Discussion:
Inconsistent lpVolumeSerialNumber when using debugger
(too old to reply)
Paul McKneely
2019-01-14 23:18:51 UTC
Permalink
Hi,

Using Open Watcom C Version 0.9.

I am reading the lpVolumeSerialNumber using GetVolumeInformationA for
drive C: When I run the program from any method other than the debugger,
I get one value for the Volume ID. But when I run it from the debugger,
the system call gives me a different volume ID for drive C: Why is this?
It is driving me nuts.

Thanks
Paul McKneely
2019-01-14 23:23:09 UTC
Permalink
Sorry. I'm using version 1.9.
Lynn McGuire
2019-01-18 19:46:29 UTC
Permalink
Post by Paul McKneely
Hi,
Using Open Watcom C Version 0.9.
I am reading the lpVolumeSerialNumber using GetVolumeInformationA for
drive C: When I run the program from any method other than the debugger,
I get one value for the Volume ID. But when I run it from the debugger,
the system call gives me a different volume ID for drive C: Why is this?
It is driving me nuts.
Thanks
Please let us know if you figure this out. I see a very similar problem
in my DiskID32 program using Watcom C++ that I do not see using Visual
C++ 2015:
https://www.winsim.com/diskid32/diskid32.html

Lynn

Loading...