Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!haven.umd.edu!uflorida!SORROW@MAPLE.CIRCA.UFL.EDU
From: sorrow@oak.circa.ufl.edu
Newsgroups: comp.os.msdos.programmer
Subject: Is this a pointer problem or is my HD dying?
Message-ID: <00949BB4.B399D980@MAPLE.CIRCA.UFL.EDU>
Date: 6 Jun 91 22:28:16 GMT
Sender: news@uflorida.cis.ufl.EDU
Reply-To: sorrow@oak.circa.ufl.edu
Organization: University of Florida CIRCA VAX Cluster
Lines: 29

Okay, here's a nifty one.  First, some background:

Machine: 80386-33 w/8MB of RAM
Software: BC++ 2.00 (C mode only, DOS applications)

Anyway, when I run this program of mine's file selector, I can choose between
different drives.  This works just fine.  However, to get the files in the
current directory, I use the standard findfirst() and findnext() loop (same one
as in the examples).

SO....it works beautifully.  But after I change disks about four times, it
locks up and I get a "Not ready error reading drive C" or "drive E" or drive
"D" depending on the drive I switched to.

So...obviously this screams pointer problem.  But I don't error out when I
switch to my second hard drive (partitioned as F and G).  At all.  And the
program works fine on a PS/2 M50z.

So, do I have a pointer trashing some obscure drive table in DOS?  Or is my
drive just flaking out?

Brian
/*
Brian Hook -- MS-DOS Programmer for Contract
-----------------------------------------------------------------
"I was in the kitchen, Seamus, that's my dog, was outside....and buried
ALIVE....fritter and waste...but this one goes to 11!....anymore of that
plutonium nyborg?....SNOW TIME!....This is home...this is Mean Street..
*/