FLP_DRIVE on QPC2 5.02

[dilwyn]

Anyone else having problems with the FLP_DRIVE command on QPC2 when used to change a floppy disk image attached to drive 1?

FLP_DRIVE 1,"D:\example.img"

I've tried changing the .img to _img in case the separator filtering is catching it, but it's not consistent.

Sometimes that works. The weird thing is, sometimes it reports either not found or medium check failed at the first attempt. If I then issue the same command a second time, it seems to work, I can DIR the list of files and copy them all, which tends to imply the image file is not damaged.

So, issuing the FLP_DRIVE command two or more times gets it to work. Wonder what I'm doing wrong?

[pjw]

Sounds like the same problems Ive been having with SMSQmulator but not, I think, ever with QPC2. Perhaps you could try "ejecting" a disk before inserting a new one, ie FLP_DRIVE 1, "", then specify the file you want. Also, make sure youre not using the same image in flp2_. Sorry, thats the best I can do..

[Derek_Stewart]

Hi,

I use QPC2 and SMSQMulator on Linux, I do not have this problem, so maybe it is the Windows operating system you are using...

[dilwyn]

Hi,

I use QPC2 and SMSQMulator on Linux, I do not have this problem, so maybe it is the Windows operating system you are using...

Windows 10 Home. Unfortunately I don't have a PC with a different version to try.

[dilwyn]

Sounds like the same problems Ive been having with SMSQmulator but not, I think, ever with QPC2. Perhaps you could try "ejecting" a disk before inserting a new one, ie FLP_DRIVE 1, "", then specify the file you want. Also, make sure youre not using the same image in flp2_. Sorry, thats the best I can do..

Floppy drive 2 was unassigned. Using FLP_DRIVE 1,"" seems to clear it. Uusually only happens if I forget to use underscore instead of period in the image name first, e.g.

FLP_DRIVE 1,"d:\image.img"
Not Found

FLP_DRIVE 1,"d:\image_img"
Medium Check Failed (for example)

FLP_DRIVE 1,"d:\image_img"
then works fine.

Either asserting the name a second time or clearing it with a blank assignment seems to clear the problem. Thanks. First time I've noticed this happening.

[mk79]

I cannot seem to reproduce it. You could try running DebugView https://docs.microsoft.com/en-us/sysint ... /debugview and start QPC with the command line "QPC2 -dbg 1024" and post the output (noting at what time which command was executed).

[XorA]

When I see weird file opening issues like this first place I always look is virus checker.

Win10 and later do not need an external virus checker, it just breaks more than it fixes.

[mk79]

Win10 and later do not need an external virus checker, it just breaks more than it fixes.

After having spend over a week investigating weird production machine failures at work that in the end happen to have been caused by McAfee I can only concur... that software is pure evil.

[NormanDunbar]

Having suffered from McAfee in the past, it's no surprise that they give it away free with new laptops etc. It's a pain in the backside, and slows everything down -- if you have to use Windows that is.

Cheers,
Norm.

[Derek_Stewart]

Hi,

As I stated earlier,no problems with Linux/Wine with QPC2 v5.x or SMSQmulator.

SO it must be a Windows problems or feature? I thought that an exception could be made in the Windows setup and give the correct permissions to overcome this, when I used use Windows and repair the Windows based PCs, this was most of the problems, basically a operating system permissions issue.