Problem with classic wb

DopPie · 27 September 2004, 15:53

Hi,

Installed classic WB on my miggy. Dopus4 won't start. Keeps ginving me error 8000 000B. Anyone knows what on earth might be wrong?

Greetz
Erno

DopPie · 27 September 2004, 16:57

I can reproduce this problem using WinUAE setting jit off and compatibility mode on and 68040 as CPU.
Too real I guess

My machine is an A1200 with a 68030. Is the package 020 only?

Bloodwych · 27 September 2004, 18:22

I have absolutely no idea what's wrong. Can't reproduce this in WinUAE either, everything works fine my end.

Others have 68030 Amiga's and haven't reported this problem. Perhaps someone knows what that error stands for?

All I can suggest is re-installing Dopus. Website here Should also have a known bug list on there.

Amiga1992 · 27 September 2004, 19:24

my 030 amiga runs dopus just fine, so does my 000 A600!. How much memory do you have?

DopPie · 27 September 2004, 19:28

I have 16Meg fast Ram. The problem also occurs with UAE. AIAB does not have the problem on my real miggy. Shall I post an UAE config file with the settings that give me trouble?

Perhaps I should not have used a 3.1 disk. Since I have 3.1 Roms I thought it would be best.

Bloodwych · 27 September 2004, 19:39

It could very well be a problem exclusive to the Workbench 3.1 disk and/or ROMS.

I added support for 3.1 at the request of others, but haven't tested it 100% as I use 3.0. That's why I say in the readme files that 3.1 isn't recommended at the moment.

Again, until I have time to test, all I can suggest is try reinstalling dopus from the site linked above or running the original, unmodified one (is it 4.12?).

27 September 2004, 19:43

Quote:

Originally Posted by DopPie

Hi,

Installed classic WB on my miggy. Dopus4 won't start. Keeps ginving me error 8000 000B. Anyone knows what on earth might be wrong?

Greetz
Erno

If memory serves me correctly, DirOpus 4 will not work with Kickstart / Workbench 1.3. You must use at least Kickstart / Workbench 2.04. My advice would be for you to use an older version of DirOpus. It should work then. Personally, I think that DiskMaster 1.4 is better then DirOpus, especially on WB 1.3. You should try it. DirOpus is fancier then DiskMaster, but does not work half the time, whereas DiskMaster works all of the time and is very reliable.

27 September 2004, 19:52

Quote:

Originally Posted by DopPie

I have 16Meg fast Ram. The problem also occurs with UAE. AIAB does not have the problem on my real miggy. Shall I post an UAE config file with the settings that give me trouble?

Perhaps I should not have used a 3.1 disk. Since I have 3.1 Roms I thought it would be best.

AH, so you are running Amiga OS 3.1. Why did'nt you say so in the first place? That is the problem. DirOpus runs great on my Amiga 2000HD with WB 2.1, but will not run reliably on my Amiga 2500 with WB 3.1. I think that it is a compatibility issue. Try DiskMaster.

Here is the link: http://kazong.privat.t-online.de/archive.html

Bloodwych · 27 September 2004, 20:36

I've been playing around in WinUAE and it's a ROM problem.

Works fine with the normal 3.x A1200 ROMS - 3.0 (39.106) and 3.1 (40.068/9).

Crashes with 3.1 (40.070). But this version never came with the A1200 did it? Wasn't it A4000T only or something?

I think the 40.070's address bus is different. Some software might not like this, especially on an A1200! (guessing here).

DopPie · 27 September 2004, 21:51

The machine it goes wrong with is an Amiga Tech. 1200. It never had it's roms replaced. So this should mean all AT's will have this problem.

The A1200 has no problems that would indicate incompatible ROMS from an A4000. Hence the PCMCIA works.

EDIT

I checked the A1200. It has ROM 40.68. So no mystery rom there. It does go wrong though. I did reinstall dopus this afternoon but to no avail.

/EDIT

Bloodwych · 27 September 2004, 22:11

Strange. I have no issues with those ROMS?

I'll test further once I have time.

Looks like buggy software from dopus 416. Only way to be sure is test it on a fresh workbench install.

Everything else working ok?

Bloodwych · 27 September 2004, 23:23

After discovering my 3.1 40.068 ROM is actually a copy of 40.069, I found what I hope is an actual 40.068 like on your A1200.

On a fresh install of Workbench 3.1 with 3.1 40.068 ROM, dopus 416 does indeed still crash. The original 412 (same one that comes with AIAB) doesn't however, so all I can suggest is using that as a replacement.

Good News (for me) - it isn't specific to the ClassicWB.
Bad News - I don't think the newer dopus is still developed? Seems like a major bug; odd that it's not listed on the site.

Summing up, dopus 416 works fine with 3.0 but not certain 3.1 roms. Why it works with only the 40.069 version of 3.1 is beyond me.

DopPie · 28 September 2004, 09:19

It could be a sum of things. I have AIAB with Dopus 4.16 running fine. Maybe it is something in the background clashing with 4.16 on the classic wb install.

If I have some spare time I will play around with the emulator. It is too much work swapping AIAB and ClassicWB on my real amiga. Decompressing takes a long time.

BTW; I really like what you did with all those newIcons on the advanced version. They look much better than the ones used by AIAB.

One question; Would the install be smaller without all those 'spare' icons? There are alot of icons there which would be fine in a sperate archive. Also a wordprocessor like final copy is not really needed in my opinion. Not really system related.

Anyway great install!

Greetz
Erno

Bloodwych · 28 September 2004, 10:59

Now I'm really confused - like I mentioned above, I've installed Dopus 4.16 on a fresh workbench 3.1 install in WinUAE and using certain ROMS it still crashed.

Seems it isn't anything to do with the ClassicWB which isn't surprising - it has less patches/programs loaded up than AIAB.

More testing required.

Thanks for the comments.

As for the icon packs - I've already outlined that in the docs under the install instructions:

Quote:

Note:
One advantage of the ClassicWB being on a HDF is you can use an emulator to customize it before transferring to a real Amiga.

Every version has been made as small as possible by removing redundant files. One exception is the ClassicWB ADVSP, which has an unusually large (7MB!) number of Newicons in the icons drawer. You may want to remove some of those before transferring.

DopPie · 28 September 2004, 12:29

Oops! Thats my bad! I never read docs. I always start with the job at hand. Lesson learned.

It is confusing. AIAB is loaded with stuff in the background and it seems to work. Maybe it is just that. Something needs patching. When I have some spare time I'll help you checking this out. For now I'm busy putting tiles in my bathroom. So spare time is rare at the momen

.

Bloodwych · 28 September 2004, 12:49

Good luck with the tiles!

After further testing, yes Dopus 416 does indeed work in AIAB.

Forgetting about the ClassicWB for a moment, I’m using a brand new install of WB 3.1 which, as mentioned above, has the same issues with certain 3.1 ROMS.

Now the really confusing part – if I enable FPU support, the error message disappears with the problematic ROMS! Must be a clue there? Tracking this down is going to be annoying.

What I’ll do next is transfer the Dopus files over from AIAB and see if they work fine. If not you might be right - AIAB has a patch running that I'm missing. It should be included in the dopus 416 archive if that's the case, unless the guy never tested it on all 3.1 ROMS.

Looking at dopus in AIAB, it reminds me I should work on the dopus config for the next release.

Testing to continue....

DopPie · 28 September 2004, 16:36

That is exactly what I did yesterday. I copied all Dopus files from AIAB to Classic WB. the 8000 000B fault kept popping up. It would be good to double check.

AIAB is running MCP. Perhaps I should try installing MCP on Classic WB and copy it's settings. It could also be the scalos settings. Use Exall , hardemulation stuff like that. Since I have no idea what they are for I left those alone.

Indeed more to test. Perhaps I have some time around saturday to try some more.

Bloodwych · 28 September 2004, 17:26

Already tried installing MCP on ClassicWB and removing it from AIAB - not that.

At the moment I'm going through AIAB with a known problematic WinUAE config and eliminating patches a few at a time. Since it errors on a fresh WB install using this config, AIAB is definitely loading up something or has settings that eliminates the problem.

If I get nowhere it could be time to e-mail Jaybee!

Bloodwych · 28 September 2004, 19:56

Fixed the problem!

Well in WinUAE anyway, but it's likely to work on your A1200. Hopefully.

Managed to track the bast*** down to setpatch. AIAB has a newer non-commodore version. The one in the ClassicWB is copied from the original workbench disks during installation.

Grab it from Aminet or AIAB "C" directory and replace the old one.

No more crashes.

Also fixed some other issues I noticed while chasing this up, so it's been useful.

DopPie · 28 September 2004, 21:37

Great. Too late in the evening for me to test it. Will have to remove my AIAB install from my machine too do so. If all works I'll let you know.

Thanks.

Regards
Erno

27 September 2004, 15:53	#1
DopPie Zone Friend Join Date: Sep 2004 Location: Den Hoorn, NL Age: 45 Posts: 259	Problem with classic wb Hi, Installed classic WB on my miggy. Dopus4 won't start. Keeps ginving me error 8000 000B. Anyone knows what on earth might be wrong? Greetz Erno

27 September 2004, 20:36	#9
Bloodwych Moderator Join Date: Jun 2001 Location: I'm behind you! Posts: 3,763	I've been playing around in WinUAE and it's a ROM problem. Works fine with the normal 3.x A1200 ROMS - 3.0 (39.106) and 3.1 (40.068/9). Crashes with 3.1 (40.070). But this version never came with the A1200 did it? Wasn't it A4000T only or something? I think the 40.070's address bus is different. Some software might not like this, especially on an A1200! (guessing here). Last edited by Bloodwych; 27 September 2004 at 20:50.

27 September 2004, 23:23	#12
Bloodwych Moderator Join Date: Jun 2001 Location: I'm behind you! Posts: 3,763	After discovering my 3.1 40.068 ROM is actually a copy of 40.069, I found what I hope is an actual 40.068 like on your A1200. On a fresh install of Workbench 3.1 with 3.1 40.068 ROM, dopus 416 does indeed still crash. The original 412 (same one that comes with AIAB) doesn't however, so all I can suggest is using that as a replacement. Good News (for me) - it isn't specific to the ClassicWB. Bad News - I don't think the newer dopus is still developed? Seems like a major bug; odd that it's not listed on the site. Summing up, dopus 416 works fine with 3.0 but not certain 3.1 roms. Why it works with only the 40.069 version of 3.1 is beyond me. Last edited by Bloodwych; 28 September 2004 at 01:20.

28 September 2004, 19:56	#19
Bloodwych Moderator Join Date: Jun 2001 Location: I'm behind you! Posts: 3,763	Fixed the problem! Well in WinUAE anyway, but it's likely to work on your A1200. Hopefully. Managed to track the bast*** down to setpatch. AIAB has a newer non-commodore version. The one in the ClassicWB is copied from the original workbench disks during installation. Grab it from Aminet or AIAB "C" directory and replace the old one. No more crashes. Also fixed some other issues I noticed while chasing this up, so it's been useful. Last edited by Bloodwych; 29 September 2004 at 17:53.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Problem with Apollo 1260 and Classic WB3.9	Reido	project.ClassicWB	19	22 June 2018 20:17
Classic WB 3.9 and PPC + Bvision problem?	Articat	project.ClassicWB	14	08 February 2012 19:59
Classic WB OS3.9 VS Classic WB ADV SP	fitzsteve	project.ClassicWB	6	28 December 2009 21:27
Classic Wb install problem	Koot	project.ClassicWB	4	27 December 2007 14:37
old problem with miamidx on my amiga classic	mrodfr	support.Apps	7	24 February 2007 14:40

27 September 2004, 16:57	#2
DopPie Zone Friend Join Date: Sep 2004 Location: Den Hoorn, NL Age: 45 Posts: 259	I can reproduce this problem using WinUAE setting jit off and compatibility mode on and 68040 as CPU. Too real I guess My machine is an A1200 with a 68030. Is the package 020 only?

27 September 2004, 18:22	#3
Bloodwych Moderator Join Date: Jun 2001 Location: I'm behind you! Posts: 3,763	I have absolutely no idea what's wrong. Can't reproduce this in WinUAE either, everything works fine my end. Others have 68030 Amiga's and haven't reported this problem. Perhaps someone knows what that error stands for? All I can suggest is re-installing Dopus. Website here Should also have a known bug list on there.

27 September 2004, 19:24	#4
Amiga1992 Registered User Join Date: May 2001 Location: ? Posts: 19,646	my 030 amiga runs dopus just fine, so does my 000 A600!. How much memory do you have?

27 September 2004, 19:28	#5
DopPie Zone Friend Join Date: Sep 2004 Location: Den Hoorn, NL Age: 45 Posts: 259	I have 16Meg fast Ram. The problem also occurs with UAE. AIAB does not have the problem on my real miggy. Shall I post an UAE config file with the settings that give me trouble? Perhaps I should not have used a 3.1 disk. Since I have 3.1 Roms I thought it would be best.

27 September 2004, 19:39	#6
Bloodwych Moderator Join Date: Jun 2001 Location: I'm behind you! Posts: 3,763	It could very well be a problem exclusive to the Workbench 3.1 disk and/or ROMS. I added support for 3.1 at the request of others, but haven't tested it 100% as I use 3.0. That's why I say in the readme files that 3.1 isn't recommended at the moment. Again, until I have time to test, all I can suggest is try reinstalling dopus from the site linked above or running the original, unmodified one (is it 4.12?).

27 September 2004, 21:51	#10
DopPie Zone Friend Join Date: Sep 2004 Location: Den Hoorn, NL Age: 45 Posts: 259	The machine it goes wrong with is an Amiga Tech. 1200. It never had it's roms replaced. So this should mean all AT's will have this problem. The A1200 has no problems that would indicate incompatible ROMS from an A4000. Hence the PCMCIA works. EDIT I checked the A1200. It has ROM 40.68. So no mystery rom there. It does go wrong though. I did reinstall dopus this afternoon but to no avail. /EDIT

27 September 2004, 22:11	#11
Bloodwych Moderator Join Date: Jun 2001 Location: I'm behind you! Posts: 3,763	Strange. I have no issues with those ROMS? I'll test further once I have time. Looks like buggy software from dopus 416. Only way to be sure is test it on a fresh workbench install. Everything else working ok?

28 September 2004, 09:19	#13
DopPie Zone Friend Join Date: Sep 2004 Location: Den Hoorn, NL Age: 45 Posts: 259	It could be a sum of things. I have AIAB with Dopus 4.16 running fine. Maybe it is something in the background clashing with 4.16 on the classic wb install. If I have some spare time I will play around with the emulator. It is too much work swapping AIAB and ClassicWB on my real amiga. Decompressing takes a long time. BTW; I really like what you did with all those newIcons on the advanced version. They look much better than the ones used by AIAB. One question; Would the install be smaller without all those 'spare' icons? There are alot of icons there which would be fine in a sperate archive. Also a wordprocessor like final copy is not really needed in my opinion. Not really system related. Anyway great install! Greetz Erno

28 September 2004, 12:29	#15
DopPie Zone Friend Join Date: Sep 2004 Location: Den Hoorn, NL Age: 45 Posts: 259	Oops! Thats my bad! I never read docs. I always start with the job at hand. Lesson learned. It is confusing. AIAB is loaded with stuff in the background and it seems to work. Maybe it is just that. Something needs patching. When I have some spare time I'll help you checking this out. For now I'm busy putting tiles in my bathroom. So spare time is rare at the momen .

28 September 2004, 12:49	#16
Bloodwych Moderator Join Date: Jun 2001 Location: I'm behind you! Posts: 3,763	Good luck with the tiles! After further testing, yes Dopus 416 does indeed work in AIAB. Forgetting about the ClassicWB for a moment, I’m using a brand new install of WB 3.1 which, as mentioned above, has the same issues with certain 3.1 ROMS. Now the really confusing part – if I enable FPU support, the error message disappears with the problematic ROMS! Must be a clue there? Tracking this down is going to be annoying. What I’ll do next is transfer the Dopus files over from AIAB and see if they work fine. If not you might be right - AIAB has a patch running that I'm missing. It should be included in the dopus 416 archive if that's the case, unless the guy never tested it on all 3.1 ROMS. Looking at dopus in AIAB, it reminds me I should work on the dopus config for the next release. Testing to continue....

28 September 2004, 16:36	#17
DopPie Zone Friend Join Date: Sep 2004 Location: Den Hoorn, NL Age: 45 Posts: 259	That is exactly what I did yesterday. I copied all Dopus files from AIAB to Classic WB. the 8000 000B fault kept popping up. It would be good to double check. AIAB is running MCP. Perhaps I should try installing MCP on Classic WB and copy it's settings. It could also be the scalos settings. Use Exall , hardemulation stuff like that. Since I have no idea what they are for I left those alone. Indeed more to test. Perhaps I have some time around saturday to try some more.

28 September 2004, 17:26	#18
Bloodwych Moderator Join Date: Jun 2001 Location: I'm behind you! Posts: 3,763	Already tried installing MCP on ClassicWB and removing it from AIAB - not that. At the moment I'm going through AIAB with a known problematic WinUAE config and eliminating patches a few at a time. Since it errors on a fresh WB install using this config, AIAB is definitely loading up something or has settings that eliminates the problem. If I get nowhere it could be time to e-mail Jaybee!

28 September 2004, 21:37	#20
DopPie Zone Friend Join Date: Sep 2004 Location: Den Hoorn, NL Age: 45 Posts: 259	Great. Too late in the evening for me to test it. Will have to remove my AIAB install from my machine too do so. If all works I'll let you know. Thanks. Regards Erno

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)