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"?

[amigagr]

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

[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

[Thomas]

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

Bye,
Thomas

[amigagr]

i have the sence (but not absolutly sure, Piru must know about it) worpos can take care it's self by it's self! i mean, in the prefs dir, there is a worpos prefs that you can setup to disable the ppc.library, so, maybe you don't need the BPPCFix modules at all. just set the config.

[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

[Doobrey]

AMIGAZ wrote:
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

Does the new ROM still have the v40 scsi.device?
The Elbox driver doesn't like the v43 one from 3.9.

Also, the setpatch line in the S-S should be changed to 'SetPatch NOROMUPDATE'   (or just rename the AmigaOSRomUpdate file) to stop it trying to do the 3.9 stuff all over again.

[bakoulis]

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

firt of all it must disable the blizkick command from your startup-s and then test all the rest. Second the EIDE'99 (with alegroCDFS filesystem right?) must start first to the top of startup (before blizkick offcourse). and finally try to change possisions to the controller (4-way-ide have four possisions) for HD and cd-rom. test all possible master-slave possisions. I had the same problem before 4 year with a tower + EIDE99 and this was the solution!
  :-)
________
Pussy

[Framiga]

is there a way to install EIDE99 resident? (like with IdeFix-LoadIDE)

[bakoulis]

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

________
affair Webcam

[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?  :-)

[CLS2086]

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.

[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:  

[Framiga]

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)

[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