| |
xeron
Account closed
Registered: Jul 2005
Posts: 5 |
Disk/side detection
What is the best way to detect which disk/side is inserted before attempting to load a file?
If its a case of reading the disk ID, how do you do that?
I'm using this loader:
http://cadaver.homeftp.net/rants/irqload.htm
If I use Kernal routines to detect the disk/side, will i have to call "initfastload" again?
Another question just occurred to me... if I try to detect the disk/side, will I have to restore normal interrupts first? or can I detect it without disabling that loader routine? |
|
| |
cadaver
Registered: Feb 2002
Posts: 1160 |
Why not use the proper loadersystem (v2.1 or v2.2) with multidrive support? The loader in the rant is about as bad as you can get for real-life applications.
IMO easiest and most compatible (some might copy all disksides to a 1581/FD/HD/IDE64 directory) is to use short identifying files, whose existence tells which side is inserted. Or even simpler, ask the user to flip disk if the file you want to load is not found :) |
| |
xeron
Account closed
Registered: Jul 2005
Posts: 5 |
Are the sources for the 2.x loader on the plush disk? If so, does anyone have them in plain text files, since I'm cross-compiling in DASM and the sources seem to be in a custom format which I assume is for turbo assembler. |
| |
cadaver
Registered: Feb 2002
Posts: 1160 |
Didn't mean plush loader, but covertbitops loadersystem. It is exclusively built for DASM compiling:
http://covertbitops.c64.org/tools/loader.zip (V2.1)
http://covertbitops.c64.org/tools/loader22.zip (V2.2)
V2.2 is somewhat simplified, as it autodetects whether fastloading or fake-IRQloading (IDE64) can be used. |
