DOOM ate my hard disk. Seriously.
Rob Jellinghaus
it in Windows. No problems. Then I quit, and cd'ed to my
\games directory, and played some Doom.
When I exited Doom, I was in C:\, and DOS seemed to have forgotten I
had any directories--I typed "dir" and got a long list of Windows
files, Doom files, Visual C++ files. I rebooted and found that all
kinds of crosslinking and file damaging had occurred, and I spent a
few hours untangling it as much as possible (which wasn't completely).
This is the first time I've ever had a problem like this with this PC,
and I've played a lot of Doom. So: am I off in outer space, or has
any FAT-related Doom bug ever been seen before?
--
Rob Jellinghaus ro...@netcom.com uunet!netcom!robj
Daniel Eding
> I just bought a new Diamond Speedstar Pro, and had been playing with
> it in Windows. No problems. Then I quit, and cd'ed to my
echh.
> \games directory, and played some Doom.
>
> When I exited Doom, I was in C:\, and DOS seemed to have forgotten I
> had any directories--I typed "dir" and got a long list of Windows
> files, Doom files, Visual C++ files. I rebooted and found that all
> kinds of crosslinking and file damaging had occurred, and I spent a
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
it's a problem with windows (the reason i took windows off at
one time). windows totally bungered up my hard drive, but then
i had no problems when i took it off. Now, i run windows (to
do mindless windows stuff), (VERY rare) but it hasn't happened yet.
What version of windows do you have?
> few hours untangling it as much as possible (which wasn't completely).
>
> This is the first time I've ever had a problem like this with this PC,
> and I've played a lot of Doom. So: am I off in outer space, or has
> any FAT-related Doom bug ever been seen before?
>
> --
> Rob Jellinghaus ro...@netcom.com uunet!netcom!robj
William Brocklehurst
a DOS problem rather than DOOM. Either way, I'm sorry it happened to you.
Can you still play DOOM ?!? That's all that really matters in life!
James H. Dooley
Hmm. Windows implies smartdrv impies write-back cache implies problem?
Meaning, were you running smartdrv with the write back cache? You shouldn't
have this sort of a problem, if you're using dos 6.2 with the new smartdrv
(writes back before showing C:>). That doesn't mean that it couldn't happen
though.
Misha Eriksson
Rob writes:
>This is the first time I've ever had a problem like this with this PC,
>and I've played a lot of Doom. So: am I off in outer space, or has
>any FAT-related Doom bug ever been seen before?
Heck, the incident you described is almost 100% similar to something
that happened to me a few weeks back. I had been playing DOOM like
crazy for a few weeks (OK, and a few other games as well...), and one
Saturday morning my hard disk drive was all messed up. Everything
crosslinked, both copies of the FAT totally different, lots of funny
files I had never seen before. Cleaning it up was hell - it took me
quite a few days to get back the most important stuff. I can't say if
it was DOOM that did it, but it's a strange coincidence...
--
Cheers,
Misha
-------------------------------------------------------------------------------
| mi...@snakemail.hut.fi (that's Mikael Eriksson!) |
|------------------------------------------------------------------------------
| Petersgatan 13E77 / Freewheelin Franklin sez: DOPE will take you |
| 00140 Helsingfors 14 / through time of no MONEY better than MONEY will |
| FINLAND / take you through time of no DOPE. |
-------------------------------------------------------------------------------
William Birkmaier
Were any of you guys using Doublespace.
Will
Dennis Chan
: I just bought a new Diamond Speedstar Pro, and had been playing with
: it in Windows. No problems. Then I quit, and cd'ed to my
: \games directory, and played some Doom.
: When I exited Doom, I was in C:\, and DOS seemed to have forgotten I
: had any directories--I typed "dir" and got a long list of Windows
: files, Doom files, Visual C++ files. I rebooted and found that all
: kinds of crosslinking and file damaging had occurred, and I spent a
: few hours untangling it as much as possible (which wasn't completely).
Gee Rob, I hate to bring up this subject, but sounds to me like
you have the symptoms of a virus. My suggestion would be to get yourself
a copy of PC TOOLS PRO V9 for DOS. It kicks ass and fixes any disk
related problems not to mention virus detection and eradication.
It's the best value product out there, kick the crap outta Norton V7.
Enough advertising for Central Point, now let's get back to the subject.
Hey ID, I want to run DOOM at .V32bis with error correction and data
compression. Let's see, 1750 cps vs 960 cps, I wonder which would be more
pleasing? I'm sure everyone out there with a modem without a 16550AFN
UART chip would be willing to shell out a few bucks and buy an I/O card
with a 16550 on it...
--
=============================================================================
Dennis Chan | "The best there was, the best
Internet Email adress: | there is, and the best there
dec...@cs.usask.ca | ever will be..."
X-Windows rules!!!! | - Bret "The Hitman" Hart
=============================================================================
Rob Bakos
Yeah, join the club.
It happened to me TWICE. The first time, I managed to recover the data.
The second time, being the non-backing up person that I am, I had to start
all over...:[
This sucks. Come on ID, fix this soon!
--
rba...@freenet.fsu.edu "Sprinkle with smileys where necessary..."
"If my arm moved that fast, I'd never leave the house!" -- Butthead
Peter Forth
>> that happened to me a few weeks back. I had been playing DOOM like
>> crazy for a few weeks (OK, and a few other games as well...), and one
>> Saturday morning my hard disk drive was all messed up. Everything
>> crosslinked, both copies of the FAT totally different, lots of funny
>> files I had never seen before. Cleaning it up was hell - it took me
>> quite a few days to get back the most important stuff. I can't say if
>> it was DOOM that did it, but it's a strange coincidence...
>> --
>> Cheers,
>>
>> Misha
I had the same occurance. I can't say DEFINATELY it was doom, however
Doom was the LAST thing that was run from that partition before it
was corrupted and the last time I played it it crashed in a funny manner
(the screen froze but the music kept playing). BTW I DON'T use
DoubleSpace, Stacker or ANY similiar software.
Peter Forth
Nate Carterette
we have doom on our 386dx...we use doublsespace and have no problems
whatsoever EXCEPT under some conditions you cannot quit the game
nate
--
"Are you THREATENING me, you malodorus little man?"
--Dr. Pippin Carter, cousin of famed Howard Carter, reacting to
a possible death threat by Dr. Ptahsheptut Smith.
Bryson Lee
: When I exited Doom, I was in C:\, and DOS seemed to have forgotten I
: had any directories--I typed "dir" and got a long list of Windows
: files, Doom files, Visual C++ files. I rebooted and found that all
: kinds of crosslinking and file damaging had occurred, and I spent a
: few hours untangling it as much as possible (which wasn't completely).
: any FAT-related Doom bug ever been seen before?
: --
: Rob Jellinghaus ro...@netcom.com uunet!netcom!robj
And I thought I was crazy!!! I encountered this problem with both
shareware and 1.1! Luckily, a cold boot seems to cure the directory
corruption in my case. I emailed Id with a problem report on this one
probably a month ago, but have heard nothing by mail or on the net until
today.
My workaround has been to disable write-caching on my drive which
contains Windows 3.1, and get rid of my ramdrive-\TEMP. I still notice
directory corruption in my harddrive-\TEMP directory, though.
Bryson Lee "Of all the so-called natural human rights that
bl...@tim.dfrf.nasa.gov have ever been invented, liberty is least likely
All standard disclamers to be cheap and is _never_ free of cost."
apply! -- Jean V. Dubois, Lt.-Col., M.I., rtd.
Mike Bird
Rob Jellinghaus <ro...@netcom.com> wrote:
[ stuff deleted ]
>I rebooted and found that all
>kinds of crosslinking and file damaging had occurred, and I spent a
>few hours untangling it as much as possible (which wasn't completely).
I had the same problem with a well-known but non-Microsoft purchased
real-time disk compressor. It increased the effective size of my
hard-disk from 200Mb to 300Mb (I keep a lot of files in GIF or ZIP
format, which the compressors can't do much with). It was the only way I
could free up enough space to fit Doom on my machine. Unfortunately,
bit-rot (my name for this phenomenon) set in, and every time I re-booted
(like whenever switching to or from playing Doom), more files were
cross-linked. If you're running MS-DOS 6.x with disk compression, this
could have something to do with it. I don't blame Doom, since Doom was
on an uncompressed disk (disk 'D') and so was the DOOMDATA directory
(disk 'C'). I didn't even load the compression software when playing
doom. My read-write disk cache was flushed before rebooting too. I
finally took the compression off, and I've been recovering files since
(about 4 weeks ago). So, I've been Doom-less since then B-(. However,
now I can say I've given it up for Lent! B-). We can't afford more disk
space at this moment (just bought an old 8-bit SB and a 14.4Kb modem, so
that blows the PC budget for the year), so I don't know what I can do.
Either I take of *all* the other games (making my 4 year old VERY unhappy
- you think you've seen Hell with Doom? Wait until you've lived with a 4
year-old who blames *you* for her unhappiness!), or I run Doomless.
*Sigh*. Anyone have Doom patches for Wolfenstein? B-)
I didn't really trust these real-time disk compressors anyhow, and my
experience just confirmed it. I'll use PKZIP from now on...as soon as
I can afford to register *it*.
--
Michael J. Bird e-mail: mjb...@idss.nwa.com
Northwest Airlines phone: (612) 727-6069 fax: (612) 726-0521
5101 Northwest Drive, Dept J3750 Opinions expressed are the *sole*
St. Paul, MN 55111-3034 intellectual property of ME!
William Ferrell
Well here's another case for you.
DOOM v1.1 working fine (registered). Downloaded the v1.2 patch. Ran it.
Ran DOOM v1.2, worked fine.
Ran it again, played fine, then I quit and used my computer normally. Decided
I wanted to play DOOM a third time (this is all on the first night I got
DOOM v1.2), changed to E:\DOOM and typed DOOM. "Bad command or file name".
Did a directory, and all traces of DOOM had disappeared. I ran undelete and
it indicated that yes, DOOM had deleted itself.
Undeleted the files and they didn't work, so I reinstalled DOOM and re-ran
the patch, and since then it's been working fine.
No other files on my hard drive were touched, and there are no traces of
virus or trojan activity.
Whassup, id?
=============================================================================
"Well, your dead now, so SHUT UP!" | Get bent! ferr...@lamar.colostate.edu
-- Grim Reaper, Monty Python's |
Meaning of Life | "You got the BFG9000. Oh yes!" -- DOOM
Misha Eriksson
William writes:
>Were any of you guys using Doublespace.
Nope. And a brand new hard disk drive it was...!
Barry Bloom
> William writes:
On the same line, after finishing playing doom, I went to load Windows
and no go... It seemed fishy, so I rebooted and everything was back to
normal. No file damage, nothing. Very strange....
BTW: My entire file structure was gone... nothing... reboot and it was
back...
--
ba...@noc.unt.edu I am convinced that UFOs exist
because I've seen one
-Jimmy Carter
-------------------------------------------------------------------------
Joker
Can anyone help, when i go to play the new "conference call" death battle, my
machine locks up, then a few seconds latter, I see this large drawing of a
turnip.. has anyone else had this problem?
--
*************************************************************************
***Joker********************************You put me through some**********
***Mrot...@indiana.edu***********changes Lord, But this one's really****
***********************************************WEIRed********************
Frank Racis
files, and 32 lost clusters containing the contents of DEFAULT.CFG.
In my case, I wouldn't call it a Doom bug, though. It seems to be caused
by Doom locking up when loading a level, and SmartDrive not being able to
write to disk. The FAT corruption is not directly caused by DOOM, it's
a secondary effect of Doom+cache software.
Note that even the new DOS 6.2 Smartdrive will still automatically use
write-back cache for all hard drives. It will not give you the command
prompt back until all writes are done, but write caching is still
enabled while programs are running (this information from the HELP
SMARTDRV command). If you turn off write caching, your disk corruption
problems should stop. (Even with write caches on, I haven't had this
problem with 1.2 so far. Maybe I'm just lucky)
-Frank
Michael Rittweger
>I rebooted and found that all
>kinds of crosslinking and file damaging had occurred,
A friend of me got a tremendous amount of "lost clusters" after upgrading
to Windows 3.11 (Windows for Workgroups) so it was the easiest way to FDISK
the HDD. My HDD was blanked out (on each partition there were 20 MB of
data, but no way to see, _what_ data, the rest empty). :-(
So it might be a problem caused by Windows, not Doom... We both installed
Win 3.10 and don't think of any upgrade. ;-)
BTW: We both are playing Doom a lot, of course... :-)
Michael
--
zap...@typhoon.kiel.sub.org | Michael Rittweger | Voice: 49-431-727173
2:242/257 @ fidonet | Nissenstrasse 12 | Data: 49-431-7297957
| D - 24148 Kiel |
dannyw
>When I exited Doom, I was in C:\, and DOS seemed to have forgotten I
>had any directories--I typed "dir" and got a long list of Windows
>files, Doom files, Visual C++ files. I rebooted and found that all
>kinds of crosslinking and file damaging had occurred, and I spent a
>few hours untangling it as much as possible (which wasn't completely).
>This is the first time I've ever had a problem like this with this PC,
>and I've played a lot of Doom. So: am I off in outer space, or has
>any FAT-related Doom bug ever been seen before?
When I first installed Doom 0.99, I had a lot of trouble getting
the sound effects working, and also noticed that chkdsk was reporting
logical errors on the disk.
Eventually I fixed the sound problem (much churning of IRQ numbers in my
complex system) and since then I haven't noticed logical errors.
I think it has something to do with not exiting Doom normally, ie
when you're experimenting with sound-board setups and have to
repeatedly reboot.
--
dan...@world.std.com Boston Massachusetts USA
Joe Zbiciak
>On the same line, after finishing playing doom, I went to load Windows
>and no go... It seemed fishy, so I rebooted and everything was back to
>normal. No file damage, nothing. Very strange....
>BTW: My entire file structure was gone... nothing... reboot and it was
>back...
This seems to be a recurring theme... Could be strange A20 handling
(for any of you out there who know what I am talking about.)
As DOS stores its structures in the HMA, if DOS is loaded High, and if
the HMA is either corrupted, or the A20 line state gets screwed up,
this could cause the disappearing filesystem problem...
(Well, not directly. The general case would be A20 is off when it should
be on, DOS *thinks* it is writing to its own space, but is writing to some
unused memory, user leaves DOOM, and filesystem appears to be gone.)
Anyhow, if any of these symptoms (disappearing filesystems, etc) occur,
do two things: Disable write-back cache, and check your "A20" setting
in Himem/EMM386 or Qemm or whatever upper memory manager you use.
Above and beyond that, you're on your own.... good luck!