Date: Fri, 07 Jan 2005 22:52:39 +0100 From: Philip Nienhuis <[EMAIL PROTECTED]> Subject: Re: [LIB] When EZ-Drive is a >must< for W98 * W2K installations
Matt Hanson wrote: > > Date: Thu, 6 Jan 2005 16:56:24 -0800 (PST) > From: Matt Hanson <[EMAIL PROTECTED]> > Subject: Re: [LIB] When EZ-Drive is a >must< for W98 * W2K installations > > --- Philip Nienhuis <[EMAIL PROTECTED]> wrote: > > > I think what happened on you Lib is that initially scandisk got confused > > because of the 0b setting (it doesn't use LBA disk translation then) and > > screwed up the file system, including your Daemon Tools subdir. > > Now that you converted it to 0c, scandisk can at last do a proper job > > and obviously finds the file system and in particular, that subdir has > > been screwed up..... > > I didn't allow scandisk to make that change on the Daemon Tools subdir when > I ran it the other day. It popped up that message, and gave me the option > to repair or quit. Having seen the damage fixing the error did once last > week, I've been quitting, and either running chkdsk from W2K to check for > problems on that drive, or installing EZD and running scandisk again from > W98. And with EZB, scandisk finds no problems. > > But I did allow scandisk to repair a couple of these errors last week > before switching C: from 0b to 0c. Do you think that when I allowed > scandisk to convert those folders and files to recovered data files, it > also wrote changes to FATs that are confusing it now that the C: partition > has been changed from 0b to 0c? This is all pretty confusing to >me<. ;-P Yes I think that is possible. > Data partitions aren't really affected by the change from type 0b to 0c, > right? The change only affects booting from a partition, in that the > partition is seen as "Windows FAT32 LBA" as type 0c, and just "Windows > FAT32" as type 0b. Yes they are affected. And it has not much to do with booting. The thing is, the 0B/0C type seems to determine which way Windows will access a FAT32 partition. In case of logical partitions 0B type, no LBA or int13 extensions will be invoked => possible data loss on > 8 GB FAT32 partitions. So you need 0C type to tell Windows to use int13 extensions every time it accesses such partitions. On other FAT32 partitions, invoking int13 extensions may be "overkill" but it surely doesn't hurt. > So I guess I could just leave things as they are with EZD installed. But I > am still having problems with Winamp not being able to find MP3s on G: that > are listed in its ACSII M3U playlist files. And that's running Winamp from > W2K. Tho' I really have no idea if the two file/folder issues are related. Winamp problem may be related to something totally different. I don't know, I can't check it from here :-) > How about I delete the C: partition, create a new one as 0c, restore a > 'vanilla' image of W98. And delete the G: partition, create a new one, 0b > or 0c probably doesn't matter for a data partition, and restore the data > from backup on the desktop. Or do you think W2K may still be playing a > part here? If I created a new C: and restored a W98 image, I'd have to run > W2K setup again so it can boot from C:. C: does not need to be type 0C, as long as it is entirely below 8 GB. Be sure to set the type of logical FAT32 partitions beyond 8 GB to 0C. That DOES make a difference. P.
