overby@plains.NoDak.edu (Glen Overby) (09/30/90)
In article <30320@netnews.upenn.edu> traw@grad1.cis.upenn.edu writes: > When using dosread, I get the following message after minix >accesses fd0: >magic != 0xAA55 ... All DOS disks have the value AA55 at the end of their boot block, as an indicator. They also have a media table at the beginning of the boot block. Those aren't set correctly on your disk, which is why you get those errors. Check the DOS you're using to format the disks; I suspect that it's not placing that information in the boot block. The last time I got errors like that, I found the "Stoned" or "Marajuana" virus residing in the boot block of a couple dozen of my disks (fortunately it didn't touch my hard disk, and couldn't comprehend what a "Minix" is :-) -- Glen Overby <overby@plains.nodak.edu> uunet!plains!overby (UUCP) overby@plains (Bitnet)
lennox@minilove.diag.stratus.com (Craig Scott Lennox) (10/05/90)
In article <6082@plains.NoDak.edu> overby@plains.NoDak.edu (Glen Overby) writes: The last time I got errors like that, I found the "Stoned" or "Marajuana" virus residing in the boot block of a couple dozen of my disks (fortunately it didn't touch my hard disk, and couldn't comprehend what a "Minix" is :-) Now there's a little talked-about but nontheless important aspect of MINIX ... you don't generally have to worry about viruses! -- | flame me at: lennox@minilove.diag.stratus.com, (Craig Scott Lennox) | |"Oh boy, virtual memory! Now I'm gonna make myself a REALLY BIG ram disk!" | | Disclaimer: My opinions are covered by section 2b of the Gnu Public | | License and thus do not belong to Stratus Computer. |