New OS3.9 Classic wb install (CF) not booting on real amiga.

[trydowave]

Coming off this thread:
http://eab.abime.net/showthread.php?t=70946
thought id move to the hardware section but its an ongoing problem.

Conntect my fresh install of 0S3.9 with Classic wb to my real A1200 but its not booting and im getting the red error (click left mouse btn) on restart.
More details soon (when im back form work).

In the meantime anyone know what might be happening?

Cheers

[Toni Wilen]

You didn't change max transfer in hdtoolbox.

[fitzsteve]

Probably scsi device in BB2 not compatible with your CF card, what size CF are you using?

If 4gb or < you can skip the scsi.device update and it should then load. You'll have to google for the change you need to make to the startup sequence, I don't remember it off hand

*(unless someone else comes along and knows it!)

[demolition]

I had a similar problem when I moved the CF card to the real 1200. Turns out that scsi.device caused the problem. Replaced it by the ChrisToni version (think it is called 43.45?) and it worked fine again. Could be a CF compatibility problem like fitzsteve is writing.

[Toni Wilen]

BB installed or not is probably the next question instead of jumping to conclusions

[fitzsteve]

Originally Posted by Toni Wilen

BB installed or not is probably the next question instead of jumping to conclusions

BB2 is part of the requirements for installing Classic Workbench 3.9

[trydowave]

Does anything in the thread suggest what I should do?
http://eab.abime.net/showthread.php?t=68514

[thomas]

A guru before it even starts to boot usually means that the boot partition is not accessible.

If it starts to boot, resets and then gurus, then the boot partition is accessible but most likely the ROM update is not compatible.

[trydowave]

Ok. Back from work and I've had a proper look...
When I start the Amiga it begins to boot from the hdd and then all the lights flash. It then resets and a second later the guru pops up.
It says:
Error 8000 0004 Task: 0800C548.

[Toni Wilen]

Did you use _exact_ same config on UAE? (Same cpu, same RAM, including type, IDE HD emulation etc..)

I still can't find your winuaelog.txt

[fitzsteve]

It shouldn't be a big deal to try skipping the scsi.device but you need to give more info like the size of the CF card you are using and confirm that you indeed installed BB2 (I'm guessing you did as it's required for Classic Workbench 3.9)

Please read and respond to the advice given, we can't help you if you don't give us the info we need

Now I've done some googling for you, you need to make the following changes to your startup sequence to skip the loading of the scsi.device contained in the BB2 update, which I believe is the cause if your Guru's.

The easiest way is to comment out the lines that I have below:

;ClassicWB Startup-Sequence
;--------------------------
;OS39

;Start OS3.9 Checks
;IF EXISTS C:SquirrelSCSI
; C:SquirrelSCSI
;EndIF
;Set SCSIUpdate 1
;IF EXISTS C:IDEFix
; C:IDEFix
; Set SCSIUpdate 0
;EndIF
;IF EXISTS SYS:Expansion/XSurfIDE
; Set SCSIUpdate 0
;EndIF
;IF EXISTS SYS:Prefs/Env-Archive/NOSCSIUPDATE
; Set SCSIUpdate 0
;EndIf
;IF $SCSIUpdate EQ 1
; C:SetPatch QUIET
;ELSE
C:SetPatch SKIPROMUPDATES "scsi.device" QUIET
;EndIF
;Unset SCSIUpdate
;End OS3.9 Checks

Leaving only the line in BOLD un-commented.

This will stop the scsi.device from being updated and should solve your issue if it is a guru caused by incompatible CF card, if you have a card larger than 4gb you might run into further problems with 'large disk support' depending on the size of CF and file system used, this is why I asked before.

I hope that helps

[trydowave]

Sorry. Been on a short holiday so I couldn't respond. I will get on this right away. For now I can say that I have a sandisk 4gb card. (has been working fine for all my other workbench installs).

Originally Posted by Toni Wilen

Did you use _exact_ same config on UAE? (Same cpu, same RAM, including type, IDE HD emulation etc..)
I still can't find your winuaelog.txt

All my settings we're correct. set the ram to 128 and the cpu to 68030 to match my ACA 1232. Not sure about IDEHD emu. I will include a winuaelog.

Originally Posted by fitzsteve

It shouldn't be a big deal to try skipping the scsi.device but you need to give more info like the size of the CF card you are using and confirm that you indeed installed BB2 (I'm guessing you did as it's required for Classic Workbench 3.9)
Please read and respond to the advice given, we can't help you if you don't give us the info we need
Now I've done some googling for you, you need to make the following changes to your startup sequence to skip the loading of the scsi.device contained in the BB2 update, which I believe is the cause if your Guru's.
The easiest way is to comment out the lines that I have below:
Leaving only the line in BOLD un-commented.
This will stop the scsi.device from being updated and should solve your issue if it is a guru caused by incompatible CF card, if you have a card larger than 4gb you might run into further problems with 'large disk support' depending on the size of CF and file system used, this is why I asked before.
I hope that helps

Hi Fitzsteve. Even though I've been an Amiga user since 1990 I'm still quite inexperienced on the Workbench side of things. Could you please tell me how I (i think) edit the start up sequence with simple steps. As for BB2. I installed both (I think OS3.9 needs both for installation and I imagine if anything went wrong with the BB updates then 0s3.9 would fail to install. I'm guessing here of course. All I know is I did install both updates and they are still in my PC harddrive folder called "stuff" which winuae can see. (might be included in log)
Thanx alot mate
Tony
P.s. Hope you got that A1200 floppy drive working in something

[fitzsteve]

Hi mate, open CLI and type:

ed s:startup-sequence

Or use the Classic Workbench menu's to (right click) Workbench>Startup>startup-sequence

If you can't boot into workbench hold both mouse buttons on boot and choose 'boot without startup sequence' then at the command prompt type:

ed s:startup-sequence

To save Right Click & choose File>Save

[trydowave]

Ok. Before this post I had to research what un-commenting was and found an article saying that to "un-comment" you simply put // in front of the code.
looking like this:

//C:SetPatch SKIPROMUPDATES "scsi.device" QUIET

I did this in start up and saved it. rebooted. And it was the same so it saved ok. After that I plugged the card back into the A1200 and it gave me a guru again (with the same error I think)

Did I do this correctly?

Btw. Since then I've installed 3.1 with Classic Workbench ADVSP onto the same card and it booted fine. Don't know if that gives you any more information on the card.

Cheers
Tony

[demolition]

Commenting in Amiga DOS scripts are done by adding a ; in front of the line. Uncommenting, you remove it again.

;C:SetPatch SKIPROMUPDATES "scsi.device" QUIET

[trydowave]

Cheers Demolition. Ill try it now.

[trydowave]

After doing this im still getting this error: Error 8000 0004 Task: 0800C548.
Does it have anything to do with the scsi cdrom drive that I have?

update: when I take out the squirrel pcmcia card the reset takes much longer. I get a black screen for ages then it resets and I get the same error message.

[Toni Wilen]

Originally Posted by trydowave

All my settings we're correct. set the ram to 128 and the cpu to 68030 to match my ACA 1232. Not sure about IDEHD emu. I will include a winuaelog.

Not really. You have UAE extensions enabled like bsdsocket, directory harddrives, 8M fast ram + 128M Z3 (Your A1200 surely does not have both) and so on

But first, configure the hdf as IDE0, not UAE. (and make sure "chipset extra" = A1200)

[trydowave]

done everything but I cant find bsdsocket.
Does any of this mean I have to reinstall OS3.9 to the CF in Winnuae?

Cheers
Tony

UPDATE: I found bsdsocket and its unticked.
Now when workbench loads I get an error message and workbench looses colour etc.

Message: Cache CDFS, Cannot open "uaescsi.device" unit 2.

Message System request: Intuition is attempting to reset the Workbench screen. Please close all windows, except drawers.

Added the no comments ";" to start up and removed it. Same error messages?

Screen is low res showing just a few shades of green and blue but in screenmode preferences it says it is in 640 x 512 interlaced and that it has 256 colours?

UPDATE: UPDATE: It seems that taking away the fast ram from 8mb to 0mb )leaving the 128mb fast ram) makes the workbench screen degrade? Anyone know why?

What roms do you've ?
Rememebr you need 3.1 kikcstart roms to use OS 3.9.

bye bye