Date: Wed, 08 Nov 2000 19:56:36 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: ad354 AT FreeNet DOT Carleton DOT CA (James Owens) Message-Id: <1659-Wed08Nov2000195636+0200-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.5h CC: djgpp AT delorie DOT com In-reply-to: <8ubi1t$j7k$1@freenet9.carleton.ca> (ad354@FreeNet.Carleton.CA) Subject: Re: InfoZIP vol label: force it, but please advise References: <8ubi1t$j7k$1 AT freenet9 DOT carleton DOT ca> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > From: ad354 AT FreeNet DOT Carleton DOT CA (James Owens) > Newsgroups: comp.os.msdos.djgpp > Date: 8 Nov 2000 12:47:57 GMT > > I'm of the printf school of debugging, but I can't remember the command to > convert an integer to a string ??? It's printf, of course ;-) Just use the %d format specifier. > If I replace the line with > > (uO.volflag == 1 && nLabelDrive > 2)) /* -$, but not A: or B: */ > > then the program labels the drive if I run from A:\ prompt, and does not > label if I run from C:\ prompt. So I'm still inclined to suspect > isfloppy(). It seems so. Try printing every value inside isfloppy, that might give a clue. Or throw together a simple test program which just calls isfloppy on a drive of your choice, and see what that does. > But it gets worse. When I run UNZIPSFX with this change and only this > change, the unzip process fails after a few filenames, complaining of a > bad offset. Perhaps some other code assumes that the labeling never works. > This tempts me to give up. Don't give up. It always gets worse before it gets better ;-)