Re: ntvdm encountered a hard error
- From: "Chris Saunders" <spamtrap@xxxxxxxxxx>
- Date: Mon, 30 Oct 2006 02:06:21 -0500
On Windows I believe you can use CreateFile and DeviceIoControl for this.
Regards
Chris Saunders
"Frank Kotler" <spamtrap@xxxxxxxxxx> wrote in message
news:1rqdnaA-Pff86djYnZ2dnUVZ_oydnZ2d@xxxxxxxxxxxxxx
Galbu wrote:
Frank Kotler wrote:
Shouldn't cause a "hard error", but sector numbering usually starts at 1
(weird, I know). I'm surprised it worked on a floppy.
well, I've actually written cl=1.
anyway, is there any other way to read a drive sector under winXp
without using a locking drive? e.g. another interrupt?
You might try int 13h/45h. In general, if you want to use bios interrupts,
boot to dos. Windows gives you a "fake dos"... and not a very good fake.
(protected mode is protecting your system from *you*, y'know!)
I think there's a Windows API that will read a sector, but I don't know
what it is. Must exist, 'cause there's an "ERROR_SECTOR_NOT_FOUND"...
Best,
Frank
..
.
- Follow-Ups:
- Re: ntvdm encountered a hard error
- From: Cranky
- Re: ntvdm encountered a hard error
- References:
- ntvdm encountered a hard error
- From: Galbu
- Re: ntvdm encountered a hard error
- From: Frank Kotler
- Re: ntvdm encountered a hard error
- From: Galbu
- Re: ntvdm encountered a hard error
- From: Frank Kotler
- ntvdm encountered a hard error
- Prev by Date: Re: ntvdm encountered a hard error
- Next by Date: Get the FAQs
- Previous by thread: Re: ntvdm encountered a hard error
- Next by thread: Re: ntvdm encountered a hard error
- Index(es):
Relevant Pages
|