Gobbledegook

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

DMA - 16 Feb 2004 00:46 GMT

Recenyl a friend with a Win98 PC, with FAT32 file system. Recently the PC
had a "crash", and when it was brought back up somehow it has become
corrupt. When lookingat the Dos level, the file system is visible, with the
Folder (directory) names concat to 8 Characters with the ~ as you would
expect.
However, when looking through Windows Explorer, the Folders and most of the
files in them are gobbledegook. Totally unreadable. The only folders
(directories) that can be read in explorer were less than 8 Char originally.

Any ideas?

Unc.

Reply to this Message

ACTD_Randy - 16 Feb 2004 15:41 GMT

I ran into this problem myself a long time ago. What happened is somehow,
dos 'got a hold' of the file structure and when this happens anything with
more than 8 characters gets the carrot ~ (sp) and is trunctated. That
explains the ~. As for the 'gobbledegook, I can't remember what caused
that, I think some of the FAT information got corrupt at that time too.
Wait for someone else to help. Sorry:(

> Recenyl a friend with a Win98 PC, with FAT32 file system. Recently the PC
> had a "crash", and when it was brought back up somehow it has become
[quoted text clipped - 8 lines]
>
> Unc.

Reply to this Message

Pete - 01 Mar 2004 13:55 GMT

I recently ran into the same problem myself - still do not
know what caused this. "Invalid system disk on reboot and
then after copying over system files - received garbled
file and directory names. I ran scandisk to see if this
would hrlp but now think this made matters worse since now
I have a bunch of directories DIR0000 to DIR0053 which are
either empty of still contain corrupt data. I am
desperately trying to retrieve my data - so far no luck. I
suspect FAT and/or MBR are corrupt as well as root
directory and am not sure how to restore/recover them. If
anyone can help I would be extremely grateful.

>-----Original Message-----
>I ran into this problem myself a long time ago. What happened is somehow,
[quoted text clipped - 21 lines]
>
>.

Reply to this Message

ACTD_Randy - 01 Mar 2004 15:45 GMT

Maybe trying to see if the drive specifications in the Bios are correct?

> I recently ran into the same problem myself - still do not
> know what caused this. "Invalid system disk on reboot and
[quoted text clipped - 45 lines]
> >
> >.

Reply to this Message