romfixes

[matthey]

There is no better scsi.device than 43.45 By Hodges, Wilen and Sauer. I tried 43.46 but soon found that version number of it, is just a number.

Info picture taken from EAB

Do you have a link to where the pic on EAB came from?

[utri007]

Do you have a link to where the pic on EAB came from?

Sorry picture is useless here http://eab.abime.net/showpost.php?p=783309&postcount=1

[slaapliedje]

I don't know? Does it have it own scsi.device? My rom works just fine with ide-fix express, wich is similar product.

I believe it does, it loads in version 100.something.

slaapliedje

[matthey]

Sorry picture is useless here http://eab.abime.net/showpost.php?p=783309&postcount=1

Thanks. Yes, the link is more useful .

[utri007]

About CD Filesystems :

I have tried without luck

CacheCDFC
AmiCDFS
ASIMCDFS
BabelCDFS
CD32/CDTV cd filesystems

Only one wich I haven't tried is that Elbox cd filesystem.

[matthey]

Rommable cd filesystem could be handy, it would allow mounting cd-rom with any boot disk which has normal 2.0-3.1 c: drawer. Could be time saving and make OS installation much easier, even if boot from cdrom wouldn't be possible.

I don't see much advantage to putting the CD file system in kickstart if it is not mounted early enough to boot off of. Most modern media has room to put the CD file system on the disk. Floppies would benefit as they have limited room but who is trying to use a CD with only floppies?

An AmigaDOS script can simulate booting off CD. Let's call the script BootCD.

Code: [Select]


SetPatch quiet
failat 31
assign T: RAM:
makedir RAM:ENV
madedir ENV:SYS
echo "WB3:S" >ENV:SYS/nv_location
mount CD0:
assign SYS: CD0:
assign DEVS: SYS: DEVS
assign ENVARC: SYS:PREFS/ENV-ARCHIVE
assign FONTS: SYS:FONTS
assign KEYMAPS: SYS:DEVS/KEYMAPS
assign L: SYS:L
assign LOCALE: SYS:LOCALE
assign LIBS: SYS:LIBS
assign PRINTERS: SYS:DEVS/PRINTERS
assign S: SYS:S
assign C: SYS:C
CD SYS:
execute S:Startup-Sequence
EndCli >NIL:


Boot off your normal bootable media and execute the script. The 68060 or 68040 support code is loaded first. For CD32 compatibility, nv_location is set to the HD for saves since most Amigas have no NV memory and the CD can't be saved to (change "WB3:S" to the desired save destination). The script may need some refinement but this should work for some CDs.

About CD Filesystems :

I have tried without luck

CacheCDFC
AmiCDFS
ASIMCDFS
BabelCDFS
CD32/CDTV cd filesystems

Only one which I haven't tried is that Elbox cd filesystem.

A file system may fit in kickstart and even work sometimes when it is not ROMable. It doesn't appear you have even been that lucky.

The CD32/CDTV CD filesystems are obviously ROMable but the drives are not IDE/ATAPI. They may lack the interface to specify a different device. The CSMK3/CSPPC has a CD file system in the flash which allows booting but it is limited in what formats it supports and may also be specific to the accelerators SCSI device.

I am not the expert on ROMTags and ROMable modules. I can disassemble the modules but I don't know what to look for. There are guys who could look at the ROMTags and hunk sections and tell you in a few minutes what is ROMable and what the module will do if placed in kickstart.

[Gulliver]

If my memory is not playing tricks on me, the OS4 Classic emergency floppy contains bootcdfilesystem which is romable and works together with the also included cdmounter command (both are 68k).

[utri007]

I don't see much advantage to putting the CD file system in kickstart if it is not mounted early enough to boot off of. Most modern media has room to put the CD file system on the disk. Floppies would benefit as they have limited room but who is trying to use a CD with only floppies?

CD boot would be ultimate goal for custom kickstart.

But think about this:

Your hard drive is broken and you need to reinstall your sytem. You are trying to found your emergency boot disk, but is missing or doesn't work. Normally you would start to installing OS3.1 from floppy, preparing hard drive with it bit a problematic hdtoolbox. After that you need to put atapi.device and cd filesystem to floppy, install and configure it, so that you could actually install OS3.5/9 wich install it own cd filesystem and uses scsi.device.

With cd filesystem / latest scsis.device on ROM you coud boot from what ever floppy you can found like deluxe paint floppy, make a cd mountlist with text editor and mount it, after that you could start to preparing hd and installing OS.