AmigaDOS asks for floppy by name, but it's "inserted" .. ?
AmigaDOS asks for floppy by name, but it's "inserted" .. ?
Say I have a demo ADF that is auto booting. It goes into AmigaDOS and then loads its files and runs. Say the name of the floppy is "Demo Floppy One" -- just after the AmigaDOS screen pops up, I get an "Insert volume Demo Floppy One" dialog. The volume is indeed named what it's asking for, as verified if I boot AmigaDOS and load that HFE image into the "drive."
Why would this happen? It's like it's loosing hold of the disk. I keep pressing Continue and it keeps asking for the disk.
This happens on a good # of demo disks I'm trying to load.
Any ideas? Tnx.
bp
Why would this happen? It's like it's loosing hold of the disk. I keep pressing Continue and it keeps asking for the disk.
This happens on a good # of demo disks I'm trying to load.
Any ideas? Tnx.
bp
Re: AmigaDOS asks for floppy by name, but it's "inserted" ..
I can check, but give a link to this demo.
Re: AmigaDOS asks for floppy by name, but it's "inserted" ..
Sometimes there is a file on the disk that's missing or something in the programs coding that's looking for a file but can't find it, so the program assumes that the correct disk isn't inserted. Check if the disk actually works in a real floppy drive, not all adf's are a good copy.
Re: AmigaDOS asks for floppy by name, but it's "inserted" ..
I know it's just a small demo sitting on an autoboot ADF (.zip includes the binary, as well, for HD running) - but it's one example from the lot:
http://www.pouet.net/prod.php?which=66507
Tnx.
bp
http://www.pouet.net/prod.php?which=66507
Tnx.
bp
Re: AmigaDOS asks for floppy by name, but it's "inserted" ..
You don't talk about your Amiga : Which amiga are you using ? Which KS/WB version ?
Many demos are only compatible with A500.
Many demos are only compatible with A500.
Re: AmigaDOS asks for floppy by name, but it's "inserted" ..
I have an Amiga 2000 with both 1.3 and 3.1 ROMs on a switcher. The same happens with both ROMs on these disks. These are recent demos, within the last year.
Another example I hit today on the Unusual Suspects (August 2014) demo.
http://www.pouet.net/prod.php?which=63917
I get same error under both ROMs and have provided a screenshot of me digging around a little - perhaps it will help diagnose. Here you see getting a dir on the image in DF0: using a WB physical floppy in DF2: in order to access dir command. See I cannot switch to DF0: as working volume but can get a dir.
It's before any of the demo code is executing here - this is early in the startup scripts. The first thing this particular disk tries to do is run the 'cpu' command from startup-sequence and then complains it can't load it when I cancel out of the Insert UnusalSuspect Disk alert on boot of the image.
See the attached please.
Another example I hit today on the Unusual Suspects (August 2014) demo.
http://www.pouet.net/prod.php?which=63917
I get same error under both ROMs and have provided a screenshot of me digging around a little - perhaps it will help diagnose. Here you see getting a dir on the image in DF0: using a WB physical floppy in DF2: in order to access dir command. See I cannot switch to DF0: as working volume but can get a dir.
It's before any of the demo code is executing here - this is early in the startup scripts. The first thing this particular disk tries to do is run the 'cpu' command from startup-sequence and then complains it can't load it when I cancel out of the Insert UnusalSuspect Disk alert on boot of the image.
See the attached please.
- Attachments
-
- image.jpeg (124.99 KiB) Viewed 8221 times
Re: AmigaDOS asks for floppy by name, but it's "inserted" ..
Disk "Unusual Suspects" have commands amigados in C:
This commands need min. kick 2.0
I preparate this same problem on kick1.3 but without "System request".
This commands need min. kick 2.0
I preparate this same problem on kick1.3 but without "System request".
Re: AmigaDOS asks for floppy by name, but it's "inserted" ..
As I said, I get the same result using Kick 3.1.norb wrote:Disk "Unusual Suspects" have commands amigados in C:
This commands need min. kick 2.0
I preparate this same problem on kick1.3 but without "System request".
But there's more oddness... See my next post please.
Re: AmigaDOS asks for floppy by name, but it's "inserted" ..
Ok, it gets odder.
If I insert an image in Disk A and boot it -- it boots and runs fine if it has a custom trackloader -- if it's not booting into AmigaDOS and running s/startup-sequence, etc. Otherwise there is the issue.
Now, check this out.
I've attached a photo of the HxC Floppy Emulator menu software showing my loading of images in Slot 02 on the HxC. Note drive A has the highlighted Lemon_Point-Natsu_no_Gomu.hfe loaded, with another disk on drive B.
Now see the screenshot of AmigaDOS. It shows DF0: as Unreadable Disk and DF1: as Natsu no Gomu! I was able to access that image, which it would seem I loaded into Drive A, via DF1: (which should be drive B) and copy the file off of the image to HD. This seems especially crazy given my first statement -- that if the disk has a track loader, then what I put on drive A DOES boot and run...
What's going on here?
I have the HxC set to emulate drive A and B (DF0: and DF1:) and I have a physical external floppy that's DF2:.
This all seems very bizarre -- does this ring a bell as far as what could be going on?
Many thanks.
If I insert an image in Disk A and boot it -- it boots and runs fine if it has a custom trackloader -- if it's not booting into AmigaDOS and running s/startup-sequence, etc. Otherwise there is the issue.
Now, check this out.
I've attached a photo of the HxC Floppy Emulator menu software showing my loading of images in Slot 02 on the HxC. Note drive A has the highlighted Lemon_Point-Natsu_no_Gomu.hfe loaded, with another disk on drive B.
Now see the screenshot of AmigaDOS. It shows DF0: as Unreadable Disk and DF1: as Natsu no Gomu! I was able to access that image, which it would seem I loaded into Drive A, via DF1: (which should be drive B) and copy the file off of the image to HD. This seems especially crazy given my first statement -- that if the disk has a track loader, then what I put on drive A DOES boot and run...
What's going on here?
I have the HxC set to emulate drive A and B (DF0: and DF1:) and I have a physical external floppy that's DF2:.
This all seems very bizarre -- does this ring a bell as far as what could be going on?
Many thanks.
- Attachments
-
- hxc_2.jpg (159.68 KiB) Viewed 8168 times
-
- hxc_1.jpg (131.69 KiB) Viewed 8168 times
Re: AmigaDOS asks for floppy by name, but it's "inserted" ..
What you should check and do:
-> The Jumper settings.
-> A general virus scanning and cleaning... (This is not the first time that someone come here with similar behavior with a images/hdd virus infection)
-> The Jumper settings.
-> A general virus scanning and cleaning... (This is not the first time that someone come here with similar behavior with a images/hdd virus infection)
Re: AmigaDOS asks for floppy by name, but it's "inserted" ..
How it works without external floppy?
Re: AmigaDOS asks for floppy by name, but it's "inserted" ..
The jumper settings are as the manual indicates for the scenario where the floppy cable has the "flipped" wires within. Pins 2 and 3, not 0 and 1 are used.
The cable has a section where 2-3 lines are twisted.
No viruses on any of the HD volumes.
bp
The cable has a section where 2-3 lines are twisted.
No viruses on any of the HD volumes.
bp
Re: AmigaDOS asks for floppy by name, but it's "inserted" ..
How can you be sure ? Have you at least tried to reproduce the issue without any HD drive connected ?blakespot wrote: No viruses on any of the HD volumes.
bp
Re: AmigaDOS asks for floppy by name, but it's "inserted" ..
This is solved.
Looking at the manual for jumper settings, I had been using the "twisted cable" settings because this is the cable I'm using:
https://www.flickr.com/photos/blakespot/28352908525/
There's twist. But, it isn't the kind of twist the HxC docs were referring to, it seems. I tried the no-twist jumper settings for DF0: and DF1: and things work fine. Glad to have this solved.
bp
Looking at the manual for jumper settings, I had been using the "twisted cable" settings because this is the cable I'm using:
https://www.flickr.com/photos/blakespot/28352908525/
There's twist. But, it isn't the kind of twist the HxC docs were referring to, it seems. I tried the no-twist jumper settings for DF0: and DF1: and things work fine. Glad to have this solved.
bp