SCSI cd rom with AsimCDFS

[Oldsmobile_Mike]

Haha, just messing with ya.  You could probably do it either way, but for the sake of consistency here, let's stick with the actual file, eh?  Trust me, I run 3.9 all day long, and I'm looking at a file as I type this.  

[gertsy]

Well I can tell you mine is in the tooltypes section of the CD0: Icon information.  Considering its not working the conventional way perhaps tony can try it and see.

[Oldsmobile_Mike]

Well I can tell you mine is in the tooltypes section of the CD0: Icon information.  Considering its not working the conventional way perhaps tony can try it and see.

So you're saying you have no mount file in your Devs: Dosdrivers at all?  Just the .info files?  I don't believe it could possibly work that way.  But if it does for you...  :laughing:

[tonyvdb]

Im using OS3.1

[mechy]

Im using OS3.1

Remember asim uses the cd0: icon in storage not in devs/dos drivers.
check storage/dosdrivers/cd0(or whatever its named) for the right device number.. if you picked CD0 in the asim install, it sets unit number to 0.. if you select cd2 its 2,etc. remove any cd0 or anything from devs:dosdrivers.
is the scsi cd drive known to be a working drive?
some old scsi cdroms had very buggy firmwares but i suspect its not that.
when testing use a pressed cd,not a copy you made,again some buggy firmwares in drives dont like some burned cd's

[tonyvdb]

Remember asim uses the cd0: icon in storage not in devs/dos drivers.
check storage/dosdrivers/cd0(or whatever its named) for the right device number.. if you picked CD0 in the asim install, it sets unit number to 0.. if you select cd2 its 2,etc. remove any cd0 or anything from devs:dosdrivers.

Really? On the 4000 you have to put the CD0 into the dosdrivers drawer. Im confused.

is the scsi cd drive known to be a working drive?

It was working last time it was used.

[scuzzb494]

This is at the top of the list:

Device =SCSI.device
Unit =0
Mount =1
Should the mount not also be 0? It shows file system is AsimCDFS so that part is good.

I have no CD0 in my Devs. AsimCDFS is run from your user-startup. Open the user-startup from S with a text editor and see if you have a line starting ;BEGIN AsimCDFS

There are two folders in Workbench one called AsimCDFS and the other AsimCDFS Buffer

In the main folder you will be able set the prefs

Like...

CD0
asim.atapi.device
Unit#: 001
Autostart DC: 2+partitions
Change Path AsimCDFS:Dis
Autoboot Never
rest empty

Get DOpus on your machine so you can interogate folders, files, icons etc without having to keep opening folders. Icons are not always visible. You can also use the Configure function to see what drives are mounted.

When you mount the CD you should get the diskchanger window for ISO9660 or Juliet.

My guess is that you have a conflict at the moment between two mounting procedures and one is cancelling the other.

Mine works fine with AsimCDFS.

[Oldsmobile_Mike]

Remember asim uses the cd0: icon in storage not in devs/dos drivers

Wow, that's crazy.  :angry:

Also what ROM version on your 2091?  Not sure the exact nature of the fixes but if you read the BBOAH link it says at the bottom that 7.0 "fixed removable media recognition".

[mechy]

Wow, that's crazy.  :angry:

Also what ROM version on your 2091?  Not sure the exact nature of the fixes but if you read the BBOAH link it says at the bottom that 7.0 "fixed removable media recognition".

good point, the wd33c93 -04 also sometimes had problems with more than 1 drive.

[delshay]

I have no CD0 in my Devs. AsimCDFS is run from your user-startup. Open the user-startup from S with a text editor and see if you have a line starting ;BEGIN AsimCDFS

There are two folders in Workbench one called AsimCDFS and the other AsimCDFS Buffer

In the main folder you will be able set the prefs

Like...

CD0
asim.atapi.device
Unit#: 001
Autostart DC: 2+partitions
Change Path AsimCDFS:Dis
Autoboot Never
rest empty

Get DOpus on your machine so you can interogate folders, files, icons etc without having to keep opening folders. Icons are not always visible. You can also use the Configure function to see what drives are mounted.

When you mount the CD you should get the diskchanger window for ISO9660 or Juliet.

My guess is that you have a conflict at the moment between two mounting procedures and one is cancelling the other.

Mine works fine with AsimCDFS.

AsimCDFS: during installation it is best to let the program detect your device. You should see it during installation, then the program saves it in the user-startup.

you must find your device during installation otherwise it will not work, unless you know how to EDIT the user-startup.

MasterISO which also works with AsimCDFS also saves its configuration in the user-startup.

[tonyvdb]

Ok, so I got it working. I changed my hard drive to be device 0 and the CD-ROM drive to be device 1 re ran AsimCDFS And all is good.
The a2091 is revision 6.6 rom

[giZmo350]

Ok, so I got it working. I changed my hard drive to be device 0 and the CD-ROM drive to be device 1 re ran AsimCDFS And all is good.
The a2091 is revision 6.6 rom

You're welcome!

[gertsy]

So you're saying you have no mount file in your Devs: Dosdrivers at all?  Just the .info files?  I don't believe it could possibly work that way.  But if it does for you...  :laughing:

No, now you're being silly. Just the parameters "device=device.type" and "unit=n", IIRC, Maybe something about active too.  But I could be thinking of IDEFIX.
Never knew about Asim using the device under storage. Perhaps they thought storage meant actual storage devices. LOL.

[scuzzb494]

Really? On the 4000 you have to put the CD0 into the dosdrivers drawer. Im confused.

It was working last time it was used.

Quick tip. Write down everything that happened in a way you can fully understand. Write all files to an adf format and store off the computer. Also save any pages and sites you may have visited to discuss the issue.

You really never want to be scratching your head regarding a similar problem. Also it helps when someone else has an issue.

Well done. Half the fun is solving the problems.

[tonyvdb]

Thank you to all who participated in this thread, it was very helpful

[delshay]

If I remember correctly if at first the device is not detected, you can run the software as many times you want, it should edit/overwrite the user start-up for you.

the only problem I had with this software is it does not show list of audio files when using a SCSI DVD rom drive, but works fine with a normal drive.

Software needs an update as MasterISO needs it to work correctly. As far as I know only SCSI DVD drive is affected.

It can still play audio files, but list of tracks is not listed and this is where MasterISO fails, as tracks are not listed and audio files can't be edited from MasterISO.