gcasServ.exe - No Disk

[concerned citizen]

I am getting the following pop-up window all of a sudden. this started after
I plugged in a new USB device, a Dazzle SD card reader.


pop up window title is gcasServ.exe - No Disk

window displays
----------------------------------------------------------------------------
--------
(X) There is no disk in the drive. Please insert a disk into drive
\Device\Harddisk4\DR10

[Cancel] [Try Again] [Continue]
----------------------------------------------------------------------------
--------




the "DR10" part is not always the same. I saw DR8 on a previous occurence of
this bug.

 

[Bill Sanderson]

Thanks for posting a unique bug--I definitely haven't "seen" this one
before.

 

[Danny Kile]

Thanks for posting a unique bug--I definitely haven't "seen" this one
before.

I am getting the following pop-up window all of a sudden. this started
after
I plugged in a new USB device, a Dazzle SD card reader.


pop up window title is gcasServ.exe - No Disk

window displays
----------------------------------------------------------------------------
--------
(X) There is no disk in the drive. Please insert a disk into drive
\Device\Harddisk4\DR10

[Cancel] [Try Again] [Continue]
----------------------------------------------------------------------------
--------




the "DR10" part is not always the same. I saw DR8 on a previous occurence
of
this bug.

If you are doing a full scan then I would check to make sure that you
are not scanning the drive assigned to the card reader.


Danny

 

[concerned citizen]

I was not doing a full scan

I did check just now, and enabled the feature. there was no check box next
to the device's drive letter, nor did I click in the box to make a check
mark for it.

Why shouldn't I be able to scan the drive letter assigned to the card
reader? Either there's a card in there or not, just as with a floppy drive.
I ought to be able to scan these sorts of things if I want, and hopefully
the software would be smart enough to properly deal with the situation where
no media is present, too. But as I said above, no scanning was being done
for the drive letter in question, as far as I know.

Full disclosure -- in this case the drive letter is C: perhaps the software
has some hard coding for that drive letter, since it is typically the system
boot drive. I can't explain the full history of why that's no longer the
case with my box, short answer is drive upgrades and data transfers, drive
controller or motherboard swaps/upgrades, etc... somewhere along the way I
no longer had a drive C: and was booting from a different letter all of a
sudden. Now that I plugged in the SD card reader, all of a sudden there's a
drive C: again.

I would not be surprised if the "Drive C:" issue is what turns out to be the
crux of this bug.

Thanks for posting a unique bug--I definitely haven't "seen" this one
before.

-------------------------------------------------------------------------- --

--------
(X) There is no disk in the drive. Please insert a disk into drive
\Device\Harddisk4\DR10

[Cancel] [Try Again] [Continue]

-------------------------------------------------------------------------- --

If you are doing a full scan then I would check to make sure that you
are not scanning the drive assigned to the card reader.


Danny

 

[Bill Sanderson]

Full disclosure -- in this case the drive letter is C: perhaps the
software
has some hard coding for that drive letter, since it is typically the
system
boot drive. I can't explain the full history of why that's no longer the
case with my box, short answer is drive upgrades and data transfers, drive
controller or motherboard swaps/upgrades, etc... somewhere along the way I
no longer had a drive C: and was booting from a different letter all of a
sudden. Now that I plugged in the SD card reader, all of a sudden there's
a
drive C: again.

I would not be surprised if the "Drive C:" issue is what turns out to be
the
crux of this bug.

I wouldn't be surprised either! Thanks for posting that additional piece of
the puzzle. This is still a bug, but that may make it easier to track down.
FWIW, my install of Windows is on drive E, and Microsoft Antispyware lives
on drive D, and I've had no problems--but I do have an actual Drive C, as
well.