Cd-rom gone after started using BlizKick *solved*

[Amigaz]

I just bought my first Blizzard PPC card and brought my Elbox Power Tower back to life.
Bought an Elbox 4xEDIE'99 interface from Amigakit so I can connect a 3.5 inch hd and a cd-rom, the cd-rom worked fine (mounted cd's ok) until I made a customized kickrom file with Romsplit/Remus..now it doesn't mount any cd's I put into it..no icon shows up after inserting a cd and I can hear that the drive doesn't spin up.
I'm suspecting that some of the extra BK modules I've used caused this problem but I'm not sure which.

Running OS3.9 BB2

The extra BK modules I'm using are:

NewAlert
NoClick
BPPCFix
BPPCFix040
FixMath404
HogWaitBlit
Patchmath020_All
Romfixes2

And Piru's exec 44.1

Anyone here got an idea why my cd-rom has been "disabled"?

[Amigaz]

amije wrote:
if you disable blizkick and boot without it, cdrom works?

Haven't actually done this but as I have only added the kickstart file to sys/devs and added the BlizKick commande to my startup-sequence I'm pretty sure something in the kickstart file is causing the issue.
I'm prepared to remove some modules from the kickstart file to see what's causing the problem but I started this thread to hear if someone knows the cause of the problem
Using BlizKick just for mapping the kickstart into fast ram and the BPPCFix modules so I can use WarpOS

[Amigaz]

Thomas wrote:

While editing startup-sequence you probably removed the EIDE'99 drivers.

Bye,
Thomas

Nope, they're still there..they're put first in the startup-sequence and I have put the BlizKick line first in the startup-sequence before the EIDE'99 stuff.
Have also tried putting the BlizKick line after the EIDE'99 lines.

What's happened is exactly the same thing when not having SKIPROMUPDATES "Scsi device" i startup-sequence and disabling the scsi.device parameters in the nsdpatch.cfg

[Amigaz]

bakoulis wrote:
And remember: SKIPROMUPDATES Scsi.device it MUST be present to your OS 3.9 startup-s for EIDE'99 interface. Don't remove it.

Shouldn't SETPATCH NOROMUPDATES QUIET take care of that too?  :-)

[Amigaz]

CLS2086 wrote:
Hi,
damned ! for the same price, you could get an IDEFix Express !
Have you tried AsimCDFS and IDEFIX'97 instead of Elbox drivers ? These works well with BZkick, and they could tell you if they saw your device on the adaptor.

Just tried IDEFIX'97 but when the IDEFIX operation started during the installation just before the FIND DEVICE thingie starts nothing happened.
I don't have AsimCDFS so I can't try it out
Arghh..I'm running out of ideas  :crazy:  

[Amigaz]

Framiga wrote:
i can't help so much, not having BK installed but try to post here the first lines of you S-S.

Then try to exstract again the modules using the BK utility romupdatesplit. (the very latest version on Piru page)

Will do.
I'm using Doobrey's RomSplit and Remus to create my kickrom file.
Works perfect on two of my A4000 but this is the first time I'm using BlizKick on an A1200

[Amigaz]

Ok, this is my startup-sequence:

; $VER: Startup-Sequence_HardDrive 45.2 (19.1.2001)
; Startup-Sequence for AmigaOS 3.9
C:CheckLMB
IF WARN
SYS:Prefs/4xEIDEPrefs
ENDIF
C:4xEIDE.driver QUIET
C:BlizKick System:devs/kick3.9.rom QUIET
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
    SetPatch NOROMUPDATE QUIET
Else
    SetPatch NOROMUPDATE QUIET
EndIf
Unset SCSIUpdate

C:Version >NIL:
C:AddBuffers >NIL: DF0: 15
FailAt 21

C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys
C:Copy >NIL: ENVARC: RAM:ENV ALL NOREQ

Resident >NIL: C:Assign PURE
Resident >NIL: C:Execute PURE

Assign >NIL: ENV: RAM:ENV
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

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

C:LoadMonDrvs

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

C:AddDataTypes REFRESH QUIET
C:IPrefs
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

C:LoadWB
EndCLI >NIL:

[Amigaz]

Framiga wrote:
i have not enough experience about BK but that notation and the BK line itself, seems wrong to me.

I prefer to leave to others experienced users on the matter, further suggestions.

I had a very simple S-S like the one posted here (when i've tryed BK myself)

Nothing wrong with the line since I've got all the modules inside the kickrom file already, it's a customized kickrom file.
Anyway, thanks for trying to help me  :-)

[Amigaz]

Ha! problem solved

Replaced the scsi.device 43.43 with the old one from the 3.1 rom.  :eureka:  :banana:  :banana: