Quote:
Originally Posted by alexh
I think he means if you burn your own KS3.9 EPROM with scsi.device 43.6b or 44.2?
|
Kickstart 3.1 contains version 40, OS 3.9 is version 44, IDEfix contains version 119. Should be obvious which one is used.
Quote:
Originally Posted by thomas
What did you do/change to make this work?
|
Sorry, this was my fault. I made a mistake editing startup-sequence so that IDEfix was not active. With IDEfix active, SFS works the same way as PFS3: you just need to access the big partitions to make them active. So if you have any assign which points to the big partition, you won't even notice that it is not active from the start.
Quote:
Originally Posted by Boo Boo
Id also be intrested - I dont like the Reboot and also after the updated SCSI update reboot seems to takes longer.
I thouight IDEFix worked much the same? and allowed large HDs or are there restrictions?
|
Just what is discussed in this thread from the beginning: run IDEfix in startup-sequence, then access the partitions which won't show up, for example with DiskChange dh1: or with Asssign something: work:somepath