A1200 not booting ClassicWB OS39
Hi,
I've installed CWB OS39 onto a CF, and I can boot the CF perfectly in WinUAE. When I insert the CF into my A1200 (running a ACA1232/40 , AGA MK2cr , 3.1 ROM, CF ID adapter) I just get the error ''Software Failure. Error 8000 0004 Task 000C54''... I can't seem to boot into safe mode either, holding the right mouse button returns the same error. Booting anther CF with CWB ADVSP works just fine (so nothing is wrong with my hw setup). Anyone once got a similar issue? |
Missing 68040.library?
|
Quote:
|
I got it to boot by commenting out the scsi stuff :
Code:
;ClassicWB Startup-Sequence |
Yes, the scsi.device in 3.9 does not like some CF cards. I had the same problem and changed into one of the patched 3.1 versions and then it works fine.
|
As above. this is a common issue with the SCSI device of BB2. What size is your CF card and what file system do you use?
|
Quote:
|
Since you use a 4gb CF your solution is safe, but if you plan to use a larger CF you will need to patch the scsi.device with a different version. (And maybe file system depending on whether you use patched FFS)
For now, all is well :) |
Steve, mate: which is your favourite scsi.device btw (large HD)?
|
Quote:
|
Found out what the issue was... seems I have the same issue as described here :
Apparently my A1200/ACA1232/CF combination doesn't like the "Devs:Amiga Rom Update" file, so I renamed it. Next step is to load in a custom 3.9 Rom including the updated scsi.device via ACA's Maprom. |
I'm just installing ClassicWB OS 3.9 for the first time on a new 16GB CF card for use in an A1200 with ACA1232 accelerator. It GURUs on boot. Looks like I am having the same problem described here.
Is there a solution that does not require ACATune? I've never needed that before because the A1232 was being used in an ACA500 previously. It is an extra purchase if I am not mistaken. -- scratch that -- looks like a download is available. Incidentally, I only have a single 500MB partition created on the CF card for now. I went for OS 3.9 as fresh install due to the support for larger partitions and all of the other enhancements that 3.9 brings. :D |
WB3.9 requires KS3.1 and to enable the memory on the ACA with KS3.1, you need to run ACAtune. You should also use ACAtune to maprom KS3.1 for extra speed. And yes, it is a free download so there is no reason not to use it.
The reason you are getting a guru is most likely due to the scsi.device that comes with WB3.9 does not work with CF cards. Check this FAQ: http://eab.abime.net/showthread.php?t=61666 'OS 3.9 Boing Bag 2 issue' |
Thanks for clarifying.
I was able to boot by renaming the update ROM file. The system shows the built-in ROM on the About screen. Besides the unfortunate broken scsi.device, what else significant does the KS 3.9 ROM provide? I somehow recall that it did not get patched until the release of BB2 but I may be wrong. The process to patch my own ROM seems a bit complicated but I will give it a try. I see the advantage for me would be working scsi AND faster ROM via ACATune. Quote:
|
You can just maprom your original KS3.1 first, then use method 1 from my link:
1 Loading a newer version of scsi.device (43.45) with LoadModule >NIL: DEVS:scsi.device NOREBOOT and Setpatch SKIPROMUPDATES "scsi.device" QUIET Then you will get all of BB2 except from scsi.device which will be the one you chose yourself and loaded with LoadModule. |
Ahhh...I finally sorted out the scsi patch instructions. :D I was going nowhere for a while. I have my patched scsi.device 43.45 in devs: now.
I have already inserted C:ACAtune -maprom * early in my startup sequence and it still boots okay in WinUAE. I have commented out all of the other OS 3.9 scsi checks and then inserted the following: C:LoadModule >NIL: DEVS:scsi.device NOREBOOT right before C:Setpatch SKIPROMUPDATES "scsi.device" QUIET which was already there. I rebooted and I get an error saying C:loadmodule failed returncode 10 I double-checked and scsi.device is definitely sitting in DEVS: Perhaps I am not doing things in the correct sequence? |
Disregard. I solved the problem.
I started to think ahead, though. Patching scsi.device solves the problem of not seeing the entire capacity of the drive but what about FastFileSystem limitations? I want to have two partitions that are approx 7GB in size. I'm pretty sure OS 3.9 allows for >4GB partitions but thought I would ask. I discovered accidentally that I did not have to do all that patching business-- the patched scsi.device was already included inside the MyFiles folder of the ClassicWB install! Oh well. :) |
Your system partition should never exceed 4 GB (or reasonably 40 MB).
|
Not my system partition. I kept that at a more reasonable 1GB.
Quote:
|
All times are GMT +2. The time now is 01:10. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.