boyd@fsucs.cs.fsu.edu (Mickey Boyd) (02/04/90)
I have had the following happen to me, and am unable to explain or correct it.
Anyone having a solution or an explination please post to this newsgroup, or
reply to me directly.
The scenario:
1. I formatted a 3.5" floppy in Double Density mode on an 386
equiped with High Density drives (I used format b: /t:80 /n:9)
2. I then put some files on it, with the PC (not an st).
3. Took it home to my trusty ST, ready to blast through some editing
with Tempus 2. Files read fine from the disk, in and out of
subdirectories.
4. Take back my now edited and improved files, and shove the disk
back into the 386.
5. 386 gives me no volume name (there was one), and no files.
After some experimentation, I have found that if I modify a disk in any way
(with the ST), the contents will be gone as far as the 386 is concerned. I
am most miffed.
--
-----------------------------------------------------------------------
---------------------------------+-------------------------------------
Mickey Boyd | "Nobody can be exactly like me.
| Even I have trouble doing it."
FSU Comp Sci | - Tallulah Bankhead
---------------------------------+-------------------------------------
-----------------------------------------------------------------------iadt3tb@prism.gatech.EDU (T. Terrell Banks) (02/05/90)
In article <9002040453.AA12498@fsucs.cs.fsu.edu> boyd@nu.cs.fsu.edu (Mickey Boyd) writes: }I have had the following happen to me, and am unable to explain or correct it. }Anyone having a solution or an explination please post to this newsgroup, or }reply to me directly. } } The scenario: } } 1. I formatted a 3.5" floppy in Double Density mode on an 386 } equiped with High Density drives (I used format b: /t:80 /n:9) } 2. I then put some files on it, with the PC (not an st). } 3. Took it home to my trusty ST, ready to blast through some editing } with Tempus 2. Files read fine from the disk, in and out of } subdirectories. } 4. Take back my now edited and improved files, and shove the disk } back into the 386. } 5. 386 gives me no volume name (there was one), and no files. } }After some experimentation, I have found that if I modify a disk in any way }(with the ST), the contents will be gone as far as the 386 is concerned. I }am most miffed. }-- Yep, I recognize this one. When it happened to me I found out that I had a virus on my Atari boot disk (damn near all the rest of my atari disks, too!). This virus was one of those guys that put something in the boot sector and then sit around infecting any disk accessed in the Atari. Run a virus fixer program on your Atari disks and get all of them cleaned up and then the IBM to Atari to IBM transfers should work OK just like you are doing them. Have fun, Terry -- T. Terrell Banks uucp: { 'insert a backbone name here' }!gatech!prism!iadt3tb Georgia Insitute of Technology - I.S.A. Internet: iadt3tb@prism.gatech.edu 190 Third Street NW Bitnet : iadt3tb@gitvm1 Atlanta, Georgia 30332-0185
drp9500@ultb.isc.rit.edu (D.R. Paradis) (02/06/90)
I have this problem with the 5 1/4" drive I have hooked up to
mine....(also with the 3 1/2")
It appears that if the ST accesses the disk at all that the boot
sector gets either rewritten or corrupted in some way that the IBM (PC
Ditto) can't read.
I correect this by using DC Format and re writing an IBM boot sector
to the disk and it reads fine. (I have to do this more on the 3 1/2"
than the 5 1/4")
Sure is a pain in the ass fix but it works for now.....
Bob