Dilwyn,
Is this with a QDOS or PC format floppy, or does it also happen if the drive is empty? One problem I know with the MS Office suite is that on loading it seems to check all files that are in the recently accessed list. Therefore if you have saved a file to a floppy it will try and access the floppy drive. I tend to notice it even at work where it tries to access a network share that is no longer available - and can take a long time before it gives up. Unfortunately I do not have a Win9x system where I can check out your scenario so can only offer some thoughts. I can check out the scenario on NT4/W2K/XP if you want - but you seem to think that you do not have problems on those OS. Dave ----- Original Message ----- From: "Dilwyn Jones" <[EMAIL PROTECTED]> To: "QL Users List" <[EMAIL PROTECTED]> Sent: Saturday, September 28, 2002 11:47 AM Subject: [ql-users] QPC2v303 versus Office 97 > > Can anyone else reproduce this problem I'm having with QPC2 v3.03? > > Start QPC2. Check that floppy disk access works with DIR FLP1_ > > Go to Windows 95 or 98 (I was using Win95 until start of this week > until it did a PC an I was forced to reinstall but this time used > WIn98SE). Start a M$ program like Word or Excel (Office 97 Pro on my > PC). > > ALT TAB back to QPC2, check you can still read a floppy disk. > > ALT TAB back to M$ prog. Open a file, make sure you wade through a few > directories - whichever directory (probably My Documents) it opens > first, make sure you load from another folder. > > ALT TAB back to QPC2. On my system floppy disk access will have > stopped working. If you DIR FLP1_ with a disk in the drive, it will > take a long time to realise it can no longer read the disk. But if you > DIR FLP1_ with no disk in the drive it realises straight away and > gives the usual error. > > This does not happen when I use the same version of QPC2 on a Windows > 2000 system at work, so may be specific to my PC or to Windows 95/98. > > Please can someone with Win9x, M$ Word or Excel and QPC2v3 try this > and let me know if the same problem occurs so I can offer a better > description of the problem to Marcel or Jochen to see if they can come > up with something to help me. Conversely, if someone with a similar > setup can verify that this doesn't happen I'll know it's something in > the software on this machine. > > Very strange, it only seems to happen with M$ programs! (OK, I know > that'll teach me...) > > -- > Dilwyn Jones >
