Mount adf like volumes
 

Hi all,
Anybody to remain me the name of the prog used to mount adf like virtual modules ?:confused
Thanks

Get VirtualFloppy from aminet and diskwiz from Codetapper's action site and extract .adf files to virtual floppies.

Maybe Giana means in Windows. In that case, it's ADFView:

http://home.worldonline.dk/viksoe/adfview.htm

You might also want to try FMS

Thanks !
I've downloaded all theses progs to choose the best !

If you want to mount ADF files under AmigaOS (not Windows), the best solution is ADF device.

No need to "extract" ADFs, just type "insertdisk <adf-file>" (or make a hotkey, menu-item etc.) and it gets mounted immediately.

Hey that's a good one!!! No need to reset to change ADFs like in FMS!


BTW, STUPID newbie question here... I used to be able to UNMOUNT devices but I forgot how! How was it, Korodny?

Yeah, I love it too...

Uh, I think it's ASSIGN <VOLUMENAME> DISMOUNT. Haven't used that one for ages :)

I'll try that out, thanks :D

Sorry for raising the dead but rather than duplicate effort I thought it would be best to mention here:

The command "insertdisk <adf-file>" gives the output:

InsertDisk UNIT/K/N,FILE/F
Use this with adf.device

But nothing mounted. Anyone know how to do that?

Try 'InsertDisk UNIT 0 filename'

EG InsertDisk UNIT 0 WB1.3.adf

EDIT: Have you mounted AD0: (UNIT 0)?

Doing it like your example InsertDisk UNIT 0 WB1.3.adf (with my own adf of course) yields:

Error inserting disk into unit 0

And no, I haven't explicitly mounted AD0. I'm assuming that should be done afterwards since it wouldn't exist prior to the first command returns successfully.

In the Amigaguide it says to mount AD0: first but, I still get the same error 'Error inserting disk into unit 0' as you do.

I used an A1200.

I have an A1200 too. Thanks for checking and for introducing me to AmigaGuide.

I'm contacting the author via the email address provided in the guide and I'll post back with the results!

If you are using an A1200 then you can also use DiskImage for mounting ADF's.

I've found a guide for that here: https://ftp.fau.de/aminet/docs/help/mountvirtual.pdf

Let's see how it goes :) Thank you Arnie.

So, I have left a thread without closure, something I despise seeing in other threads! I am getting more forgetful by the week and subscriptions are not helping :)

I got a response from a developer who offered to attempt to track down the code if I was willing to debug myself. I don't think I want to put him (or me) to that effort so I passed.

I don't remember if I tried the pdf above but I will give it a go soon and update the thread. My goal now is to resolve threads I have started since there are quite a few.

The best, easiest tool that I've found is ADF_Device, which can be downloaded from here http://bfugl.dk/Download.asp
Just follow the installation instructions in the AmigaGuide included in the download.
After, to add an ADF to a virtual drive just execute "Insert.script <adf file name>" - you'll then be prompted (pop-up) for the device number (maximum of 8 concurrent devices).
And to unload the file, execute "Remove.script <adf file name>" - again, you'll be prompted for the device.
I've added these commands to my DiskMaster (tool similar to Dopus) so I just click on the file and execute either the Insert or Remove scripts - piece of cake!

Thanks Smakar. I get a 'file is not executable' error for the script, even though in Information the 'executable' box is ticked.

But running adf_device verbatim according to the instructions I get success. Here's what I did:
I have reinstalled Workbench prior to this because of other issues I noticed so maybe my workbench install wasn't so good. This is going to make life much easier, thanks so much to all! :spin

Edit: I fixed the script by running

protect <filename> +e

Edit2: actually, I think the problem was that the 'script' field was not ticked under Information. The file was executable all along but the error wasn't accurate. Ignore the protect command.

Never a DOS script can be "executable". Use "protect +s" for this. It allows to run them from shell as if they are executable. In WB you need an icon with iconx as default tool (or a similar program like xicon). You don't need protection bits "s" and "e" then.