🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.msdos.programmer
Article #800

Re: NonDos

#800
From: Jim Withrow
Date: Mon, 21 Dec 1992 20:01
44 lines
2514 bytes
In article <rol-211292131758@90.222.1.80> rol@grasp1.univ-lyon1.fr (Paul Rolland) writes:
>From: rol@grasp1.univ-lyon1.fr (Paul Rolland)
>Subject: Re: NonDos
>Date: 21 Dec 92 12:19:04 GMT
>In article <18240@mindlink.bc.ca>, Robert_LaCasse@mindlink.bc.ca (Robert
>LaCasse) wrote:
>> 
>> I have discovered in my chkdsk/f.com a reply stating--PROBABLE NON DOS DISK--
>> every time I on my Hard c: drive the boot sector seems to be working just
>> fine in booting up but I think that my partition section must be snafued
>> since the command- PROBABLE NON-DOS DISK- is always displayed on chkdsk/f.
>> I realize that this is usally bad news, but nothing apparently seems to be
>> wrong with the general operation of the unit. I tried to sys c: from a floppy
>> but the boot is alright. It was suggested that I format, but who wants to do
>> that? Are there any other metods of fixing this problem;
>
>Hello,
>
>If my memory is good (and i think it is), this message appears when chkdsk 
>doesn't find a DOS signature at the beginning of the FAT. In other words,
>the
>first byte of your FAT on the C: disk isnot 0xF8.
>This is a bad news. It seems to prove that your FAT may be wrong...
>
>> incidentally I put my
>> pkunzip files in the DOS directory for faster access, could that be the
>> problem?
>
>No, i don't think pkunzip could cause such a problem, even if you are using
>beta release. May be a virus... Why don't you run your favorite virus
>checker?
>
>Paul Rolland
>
>A bug can be changed to a feature by documenting it. Developpers know !

I have seen this problem a few times before.  It usually showed up when the 
disks were larger than 32Mb and some other non dos method of 
partitioning and formatting were used.

Try using norton utilities to repair it (Norton Disk Doctor) or you may be 
using an old version of dos which you may want to upgrade.

Jim Withrow
Technical Details
Message-ID: <withrow.5.0@lims01.lerc.nasa.gov>
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!rphroy!caen!uwm.edu!linac!pacific.mps.ohio-state.edu!cis.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!eagle!lims01.lerc.nasa.gov!withrow
References: <18240@mindlink.bc.ca> <rol-211292131758@90.222.1.80>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!rphroy!caen!uwm.edu!linac!pacific.mps.ohio-state.edu!cis.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!eagle!lims01.lerc.nasa.gov!withrow
From: withrow@lims01.lerc.nasa.gov (Jim Withrow)
Newsgroups: alt.msdos.programmer
Subject: Re: NonDos
Message-ID: <withrow.5.0@lims01.lerc.nasa.gov>
Date: 21 Dec 92 20:01:08 GMT
References: <18240@mindlink.bc.ca> <rol-211292131758@90.222.1.80>
Sender: news@eagle.lerc.nasa.gov
Organization: NASA Lewis Research Center, Power Systems Facility
Lines: 44
Nntp-Posting-Host: 139.88.33.2