Data on D disk changed from words to symbols

[The Olde Man]

This is a partitioned drive Win98SE.

I woke up this morning to find that the D drive is designated with the lettter D + some symbols and everything on it is also in symbols. And they can't be renamed nor can they be deleted.

Delete brings up File system error (1026) which mutters darkly about an overfull Recycle Bin. Well, it ain't overfull.

New data entered is not changed.

I vaguely remember reading about this on some forum, but a search got nothing.

Any good ideas out there?

[pkiff]

If this is the same ThinkPad 600 you've been trying to get up and running, then boy are you ever having bad luck. What you've described sounds to me like a corrupted drive.

Do you have enough free disk space on the drive?
http://support.microsoft.com/?kbid=208082

Have you tested the disk for errors?

If you have any data on this disk that matters to you, then ideally, you would at this point install it as a slave in a second computer and make a complete clone copy of the disk with the error. Then you could play around with the original to try to recover whatever you ccould without worrying about losing anything else. Failing that, my recommendation would be to manually copy as much important data from the disk to another one before running any automated repair tools or other quick disk fixes.

Is it possible that this problem is related to the "version conflict" error messages you describe in an earlier thread?

Phil.

[csouter]

Hi

I have also been having the same problem and I think it has to do with the I/O controller not being able to do a correct translation of the LBA CHS count on your 40GB HDD.

I also have a TP600 (2645-45A) which I recently upgraded with a 40GB HDD, and then attempted to install Win98SE on it. I have been having all kinds of troubles with it.

A search of the M$ website threw up a couple of references to problems with the Win9x driver for HDDs bigger than 8GB on the Intel chipset, (Intel 82371AB/EB PCI Bus Master IDE Controller).

At first, I had the same problem as you - instead of seeing a drive label in "My Computer," I was seeing "Greek." Also, ScanDisk refused to run, giving some cryptic error message about the disk being locked (by what, I cannot fathom). Also, the partitions giving the problem had been functioning correctly for several weeks previously, and then this error suddenly appeared out of nowhere!

A check of Device Manager showed that the last two partitions on the drive were running in "MS-DOS Compatibility Mode," whatever that is. The help referred me to the M$ support site, where I found the information about the Intel chipset referred to above.

The problem seems to be with a file called ESDI_506.PDR, which is the VXD for the I/O chipset. There is a lot of info on the M$ website, but I can't find any reference to a fix for it.

Fortunately, I don't have anything important on the HDD, so I've been trying different ways of formatting and partitioning it to see if anything works. Nothing has, so far.

If I can find any further info, I'll let you know. I'll try to find the URLs pointing to the info on the M$ support site and post them here.

HTH. Good luck!

[The Olde Man]

I have the same Intel IDE controller that you have. However I also have a "STANDARD BUS MASTERING IDE HARD DISK CONTROLLER" that seems to be fighting the Intel as to who is in charge.

None of this is conducive to a tranquil mind. I wonder if I took one out behind the barn and killed it with an axe if that might not solve some weird problems I seem to be having.

The trick question is: Which one?

[pkiff]

I have the same Intel IDE controller that you have. However I also have a "STANDARD BUS MASTERING IDE HARD DISK CONTROLLER" that seems to be fighting the Intel as to who is in charge[....]The trick question is: Which one?

This is normal in a fresh Windows 98SE install. My 98SE installs on 600/770 machines all either have TWO or THREE of these "Standard Bus Mastering IDE Hard Disk Controllers" depending on whether I am using a docking station or not. For more information on that specific item, check out: Thinkpad 600E and Win98SE conflict.

I don't know about the issue that csouter points to. However, if you update all your drivers correctly, I am quite sure that Windows 98SE can handle large hard disks without any corruption or other problems with the Intel 82371AB/EB PCI Bus Master IDE Controller. I've run 600X, 770E, 770Z machines with 32GB, 40GB, and 48GB: No problem. All those machines use virtually the same Intel 82371AB/EB PCI Bus Master IDE Controllers. But you have to make sure you update your Windows 98SE system files to the latest drivers appropriate for your machine.

Phil.

[csouter]

Sorry I took so long to get back to you, but I needed to try out a few solutions that I have found through researching both the IBM and the Microsoft websites.

In addition to Phil's IBM URL, here are a few more. Phil doesn't seem to be aware of this problem, but it's all related. The one thing I can't find now, is an article I saw somewhere which stated something to the effect that you shouldn't download chipset drivers from the Intel website if you are using a branded PC such as a ThinkPad. The chipset drivers on the Intel website are for users installing non-OEM Windows versions. That's why you're getting a conflict between the "Standard IDE Controller" and the "Intel 82371 AB/EB IDE controller." If Win98 is set up correctly on a TP600, you'll only get "Standard IDE Controller, " no mention of Intel.

BTW, the supplementary files on the IBM/Lenovo website don't solve the problem of running Windows98 on an IDE HDD with a capacity greater than 32GB. They only fix the Win98SE shutdown problem. This is actually a problem with APM. The problem with your drive is definitely due to the ESDI_506.PDR needing patching.

I guess I didn't explain very well in my previous post, but I have actually been have exactly the same problems as you: "My Computer" shows the drive (or drives) as having no labels, and the label field in the Properties notebook is grayed out. ScanDisk doesn't work and quits with a cryptic error message. The most frightening sight was the output from "DIR X:" at the MS-DOS Prompt. It was "Greek!!!" (That is, incomprehensible characters). "Control Panel" > "System" > "Performance" shows "Drive X: is using MS-DOS compatibility mode." There is a "Help and Support" link on the "Performance" page. That link takes you to Microsoft where I found the information given below. I have just downloaded and installed the driver referred to in the second URL listed. The troubles have finally all disappeared!

The first of the following references was the most useful to me, and, I suspect, will be the most useful to you, also.

ScanDisk Errors on IDE Hard Disks Larger Than 32 GB:

http://support.microsoft.com/kb/243450

The above site contains a link to the following site, where you can download an updated ESDI_506.PDR:

Windows 98 Large IDE Update:
http://www.microsoft.com/windows98/down ... efault.asp

Here are some more sites with further information:

Windows Support for Large IDE Hard Disks:
http://support.microsoft.com/kb/126855

Large IDE Hard Disk May Run In Compatibility Mode:
http://support.microsoft.com/kb/175629

Troubleshooting MS-DOS Compatibility Mode on Hard Disks:
http://support.microsoft.com/kb/130179

MS-DOS Compatibility Mode Problems with PCI IDE Controllers:
http://support.microsoft.com/kb/151911

NOTE: The last site listed above specifically mentions the Intel 82371 AB/EB controller.

Hope this helps.

[The Olde Man]

Thanks for the info. However, another thread will show that I have ginned up another problem. I am beginning to think I have a full time hobby here.

[pkiff]

In addition to Phil's IBM URL, here are a few more. Phil doesn't seem to be aware of this problem, but it's all related[....]BTW, the supplementary files on the IBM/Lenovo website don't solve the problem of running Windows98 on an IDE HDD with a capacity greater than 32GB.

Mmm...yes, you're right I didn't think about the problem of using a drive larger than 32GB in Windows 98. Thanks for catching that.

It's possible that the original poster is experiencing several unrelated problems, including the one I identified (the conflict under hard disk controllers) as well as the one you've identified (scandisk causing errors with drives larger than 32GB).

Phil.