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

[trydowave]

My entire system:

A1200
3.1 roms
ACA 1232 128mb ram
SCSI Squirrel pcmcia and CDrom

Even though I don't need to I hear my ACA 1232 can emulate 3.1 roms.

[fitzsteve]

SCSI Squirrel might be your problem because if you look at my post the Classic Workbench Startup sequence is effected if you have one installed:

;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

I assume you already tried to edit yours to match the above? (of course don't change anything below this)

[trydowave]

Ok. Ive done the above and thanks to your help I've managed to get OS3.9 running on my real A1200 It has problems though. My CD Rom Drive is no longer recognised through squirrel and every time I boot I get this message:

Cannot open "uaescsi.device" unit 2.

I occassionaly get this message: Intuition is attempting to reset the Workbench screen. Please close all windows, except drawers.
I think this goes away after awhile and now the proper screen res and 256 colours seem to be back.

Any advice?

Cheers mate
Tony

[turrican3]

Originally Posted by 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?

for this message : Message: Cache CDFS, Cannot open "uaescsi.device" unit 2.
you should edit the file devs:dosdrivers/cd2
change the "uaescsi.device by "scsi.device"
but i just read that you have just 1 cd-reader on your amiga then you should move the cd2and cd2.info from devs:dosdrivers/ to sys:storage/dosdrivers/
if you don't have a cd2 file in devs:dosdrivers/ look in every file in dosdrivers if one has the "uaesci.device".if yes change it to "scsi.device"
then reboot if after the amiga tell you Cache CDFS, Cannot open "scsi.device" with surely the unit number.
then move the files which contain the scsi.device with the good unit number from devs:dosdrivers/ to sys:storage/dosdrivers/
the problem is that the amiga is trying to mount a device "uaescsi.device"
but on amiga uaescsi.device doesn't exist, then filesytem cdfs just tell you that there is a problem.And the fact that the workbench is ugly is just because a message was prompted during the boot and the workbench can't change the resolution etc...
I hope it will help sorry for my bad english.
ps: if you continue to have an error message after this, edit the startup-sequence and the user-startup and for a line mount "uaescsi.device" unit 2 or mount cd2 and comment it or replace uaescsi.device by scsi.device but i think you will have to comment it.

Really hope it will help, but guys with better english than will surely explain this in a better way.

[trydowave]

In DEV/DOSDrivers in Workbench (my system draw) I only have 3 files: PIPE, VNC, VNR and EMERGENCY CD.
In Workbench, Storage, DOSDrivers I have:
AUX, CD0, CF0, DM0, MS0, MS1, PC, PC0m PC1, PF0, PF1, RAD, ZIC and ZIP.
Can't find CD2 anywhere. Maybe i'm looking in the wrong place?

Cheers

[FOL]

Originally Posted by trydowave

In DEV/DOSDrivers in Workbench (my system draw) I only have 3 files: PIPE, VNC, VNR and EMERGENCY CD.
In Workbench, Storage, DOSDrivers I have:
AUX, CD0, CF0, DM0, MS0, MS1, PC, PC0m PC1, PF0, PF1, RAD, ZIC and ZIP.
Can't find CD2 anywhere. Maybe i'm looking in the wrong place?

Cheers

In the Idefix package, theres a program called find device. Use that to find out what your device and unit is. the simply edit emergency CD and alter to match your device / unit.

[trydowave]

FOL. I don't know how to do that?
After I installed my CDrom squirrel drivers onto this new install I discovered the device as a Sanyo / CRD2505 / 1.20 using IDEFIX97.

I don't know where to edit the file and im not sure which part is the devices name. It doesn't say for instance, device name and then CRD2505. I can guess, which I did a minute ago. I tried to edit the part of emergency cd that said "uaescsi.device" to "scsi.device". I rebooted but I still get the message "Cannot open "uaescsi.device" unit 2"

Turrican 3: thanx for the response but I had a little bit of trouble understanding all your message. especially the bit about editing the start up sequence and also that I cant find CD2. I think I remember seeing the squirrel scsi cdrom saying its CD0.

Thanks
Tony

UPDATE: Since installing the squirrel SCSI and CD32 emu software my startup sequence has changed. It's no longer the looks like the one on Fitzsteve's last post.

Just an Idea. but after editing EMERGENCY_CD and CD0 in DEV/DOSDriver from unit 2 to unit 0 I get a boot that no longer has the error message "Cannot open "scsi.device" unit 2" (it no says uaescsi.device as ive edited that bit). But. Now I get an icon on the desktop that says EMERGENCY_CD: Uninitialized. Could it be that My Emergency CD is in fact CD0 and when I change my scsi device from unit 2 to unit 0 it interferes with it?

[fitzsteve]

@trydowave

My advice is to carefully read the readme files and documentation for the devices and software you are installing.

This will help you, blindly installing software will only cause conflicts.

[trydowave]

I've moved my EMERGENCY_CD from DEV.DOSDrivers to my misc drawer (a safe place) and I left CD0 in Storage/Dev/Dosdrivers. It is edited to unit 0. On reboot now I'm not getting an error message. I think there was a conflict with the EMERGENCY_CD? Question is. Does the Emergency CD have to be in DEV/DOSDRiver?
Thanx
P.s. my start up sequence now looks like this:

; Added by ADAPCMCFL-Installer
FailAT 11
C:CardPatch
run >NIL: C:CardReset TICKS 50


;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


;CD32 Startup added by Squirrel SCSI Installation
IF EXISTS S:CD32-Startup
C:Assign T: RAM:
Execute S:CD32-Startup
EndIF
;End CD32 Startup


;ELSE
C:SetPatch SKIPROMUPDATES "scsi.device" QUIET
;EndIF
;Unset SCSIUpdate
;End OS3.9 Checks


C:GetMouseInput LOCAL


IF $MouseInput EQ 1
Unset MouseInput
C:Assign >NIL: ENV: RAM:
C:Assign >NIL: T: RAM:
C:Execute S:Maxmem-Sequence
EndCLI >NIL:
EndIF


IF $MouseInput EQ 2
Unset MouseInput
C:Execute S:Bootmenu-Sequence
EndCLI >NIL:
EndIF


Unset MouseInput


IF EXISTS C:StackAttack
C:StackAttack
EndIF


C:Version >NIL:
FailAt 21


IF EXISTS SYS:WBstartupD
C:Rename >NIL: SYS:WBStartup SYS:WBStartupM
C:Rename >NIL: SYS:WBStartupD SYS:WBStartup
EndIF


Resident >NIL: C:IconX PURE
Resident >NIL: C:WBRun PURE
Resident >NIL: C:Assign PURE
Resident >NIL: C:Execute PURE
Resident >NIL: C:SetEnv PURE REPLACE


IF EXISTS L:env-handler
C:MakeDir RAM:T RAM:Clipboards
L:env-handler
ELSE
C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys
C:Copy >NIL: ENVARC: RAM:ENV ALL NOREQ
Assign >NIL: ENV: RAM:ENV
EndIF


IF EXISTS C:PatchRAM
C:PatchRAM
EndIF


IF EXISTS C:TagLiFE
C:TagLiFE
EndIF


Assign >NIL: T: RAM:T
Assign >NIL: CLIPS: RAM:Clipboards
Assign >NIL: REXX: S:
Assign >NIL: PRINTERS: DEVS:Printers
Assign >NIL: KEYMAPS: DEVS:Keymaps
Assign >NIL: LOCALE: SYS:Locale
Assign >NIL: LIBS: SYS:Classes ADD
Assign >NIL: HELP: LOCALE:Help DEFER


IF EXISTS C:BlazeWCP
C:BlazeWCP
EndIF


IF EXISTS SYS:System/FBlit/FBlit
SYS:System/FBlit/FBlit
SYS:System/FBlit/FText
EndIF


BindDrivers
C:Mount >NIL: DEVSOSDrivers/~(#?.info)


C:LoadMonDrvs


SetEnv Language "english"
SetEnv Workbench $Workbench
SetEnv Kickstart $Kickstart
UnSet Workbench
UnSet Kickstart


IF EXISTS C:CyberBugFix
C:CyberBugFix
EndIF


IF EXISTS C:IconBeFast
C:IconBeFast 0
EndIF


C:AddDataTypes REFRESH QUIET
IF EXISTS SYS:System/VPrefs/VisualPrefs
Run > NIL: SYS:System/VPrefs/VisualPrefs
EndIF
C:IPrefs
SYS:System/FPalette/FPPrefs
C:ConClip


Path >NIL: RAM: C: SYS:Utilities SYS:Rexxc SYS:System S: SYS:Prefs SYS:WBStartup SYS:Tools SYS:Tools/Commodities


SYS:System/REXXMast >NIL:


IF EXISTS S:User-Startup
Execute S:User-Startup
EndIF


Resident Execute REMOVE
Resident Assign REMOVE


IF EXISTS C:StackAttack
C:StackAttack AUTO
EndIF


C:LoadWB


EndCLI >NIL:

[FOL]

That looks fine apart from, why are you skipping scsi.device update?
I cant see anywhere, where it loads a newer module.

[demolition]

Originally Posted by FOL

That looks fine apart from, why are you skipping scsi.device update?
I cant see anywhere, where it loads a newer module.

Because it could be the scsi.device update which caused the guru. This was the case on my 1200. But since it still gurus, it must be something else.

Edit: Try to comment the setpatch line as well and see if it boots. Setpatch should be there but it should be able to boot without it. If this works, then it probably needs some more arguments to skip patching some other modules.

[fitzsteve]

Originally Posted by FOL

That looks fine apart from, why are you skipping scsi.device update?
I cant see anywhere, where it loads a newer module.

I've had the same issues with the BB2 scsi update and newer Sandisk cards, that's why I suggested he skip the scsi.device.

He doesn't need to load a newer one as his CF is only 4gb.

The point was to trouble shoot, we can move onto patching another scsi.device later if he wants.

The fact is the system is booting now so he's making progress (see post no. 23)

[trydowave]

Firstly. After moving emergency cd to misc and cd0 to storage/dosdrivers the Amiga wouldn't boot at all. I then moved cd0 back to dev/dosdrivers and left emergency_cd in misc. That got rid of the error message and I was able to boot as normal. I still don't know if emergency cd is needed but its in misc and not deleted.

CD rom drive is recognised now and im able to play a few CD32 games.

Fitzsteve: Do you think I will still need to skip the scsi.device? I'll considering editing stuff later, but wont if I don't have to.

Next: onto getting the indi MK2 screen modes working, getting online with an accton pcmcia card and, configuring CD emulation and making sure the MK2 doesn't overheat (it is getting noticeably hot) while the CF covers it in its little polystyrene packaging. Maybe some stick on heat sinks are in order? But, maybe that's for another thread

[fitzsteve]

Originally Posted by trydowave

Fitzsteve: Do you think I will still need to skip the scsi.device? I'll considering editing stuff later, but wont if I don't have to.

If the BB2 scsi update is indeed conflicting with your Media then yes you will need to keep skipping the update.

My workaround was to use a custom Rom with the BB2 modules inside but scsi.device updated to chris/toni's version.

I then load that via the ACATune's Maprom facility and skip the Rom update completely with:

C:SetPatch NOROMUPDATE QUIET

My Amiga boots and runs much faster this way too

[trydowave]

I have to admit it's taking a long time to boot. But I thought that was due to it being OS3.9. Here's a link to a video of it booting up and running.
Maybe it can tell you something about its speed. If its ok or if its too slow etc:

[ Show youtube player ]

[FOL]

Originally Posted by trydowave

I have to admit it's taking a long time to boot. But I thought that was due to it being OS3.9. Here's a link to a video of it booting up and running.
Maybe it can tell you something about its speed. If its ok or if its too slow etc:

[ Show youtube player ]

Nothing wrong with that, it boots. Does patches and resets to make them resident. Then boots normally.
You may get more speed out of it, if the you use SFS or PFS3 over FFS (and they are setup correctly).

[fitzsteve]

All looks fine to me, boot time is as expected. You would save the first few seconds before the reset by using Maprom and skipping the OS3.9 Rom Update.

The reason the OS is taking so long to load is because of your 256colour backdrop.

The mouse pointer ghosting is the refresh on the LCD I think, mine does that too.

Are you running ACATune?

[trydowave]

Originally Posted by FOL

You may get more speed out of it, if the you use SFS or PFS3 over FFS (and they are setup correctly).

Isn't that for hdds over 4gb?

Originally Posted by fitzsteve

All looks fine to me, boot time is as expected. You would save the first few seconds before the reset by using Maprom and skipping the OS3.9 Rom Update.

The reason the OS is taking so long to load is because of your 256colour backdrop.

The mouse pointer ghosting is the refresh on the LCD I think, mine does that too.

Are you running ACATune?

I'm not that bothered about the few seconds, but, can you please tell me how to run ACATune? Ive downloaded V17 lha. I've ran the program and then it says USE- HELP or ? for description. I then press the help key and nothing happens. I try ?, press enter and then nothing happens. Its weird as I've used it recently when I had my old 3.1 WB install.

Cheers
Tony

[fitzsteve]

Hi Tony,

Everything is explained in the ACATune Readme, if you're not using it then you will notice a big difference after you do.

As for SFS/PFS3 they will help speed loading times up, especially where there transfers of many small files, you can use SFS/PFS3 with <4gb too.

I've attached the ACATune readme for you and you should also read the PFS3 documentation if you are thinking about using it

[trydowave]

I read the doc (most of it which I could understand). Copied ACAtune to workbench (C) and opened shell and typed ACATune -status. It showed my card details. Maprom is disabled etc. Wasn't there a program of this with a GUI? I'm sure I remember one or does all this have to be changed with command lines?
Cheers