Jeff Somers
jso...@marcam.com
In article <Cvp8u...@bfsec.bt.co.uk>, ddo...@bfsec.bt.co.uk (Damian Dougan) writes:
|> Hello All,
|>
|> Doom 1.666 patch is out on
|>
|> infant2.sphs.indiana.edu /pub/doom/incoming
|>
|> ftp.uwp.edu /pub/incoming/id
|>
|>
|> The files are:
|>
|> dm1666.txt
|> dm1666rp.zip Registered Patch
|> dm1666sp.zip ShareWare Patch
|> dm1666sw.zip Share Ware Doom 1.666
|>
|> Happy Dooming!
|>
|> Damien.
: >Hello All,
: >Doom 1.666 patch is out on
: >Happy Dooming!
Now, don't get me wrong. I'm very happy about the patch being
out, but I gotta warn ya...the process of patching is LOOONNNGGG!!!! I
timed it, and it took well over an hour of non-stop disk spinning. *yawn*
BUT, great work gang! Everything looks much better, and I'm
dying to try the 14.4 modem setup. And I can now use the keyboard
without wondering when the spinning top imitaion will start up!
A grateful user.
: >Damien.
What exactly does version 1.666 offer over 1.2?
Paul.
>Hello All,
>Doom 1.666 patch is out on
>infant2.sphs.indiana.edu /pub/doom/incoming
actually, that's: /pub/doom/id
Are you running a 10 MHz 80286 without a WRITE DISK CACHE? On my 486 DX 40,
with SMARTDRV 5.01 configured for Write Cacheing, it took less than 10 small
minutes...
Don't you just love it when things finaly come out?
Thanks, id!
Cheers,
Gilles.
--
*---------------<([ Gilles Gravier -- cor...@ensta.fr ])>---------------*
I know you believe you think you understand what you thought you heard me
say, but I am not sure you realize that what you thought you heard is not
what I meant.
What, were you running the patch on your Commodore 64? It took
about five to seven minutes on my 486dx2/66.
Suggest you buy a faster disk? It took less than 5 minutes on my machine
so don't be put off. Get the patch and install it!
: What exactly does version 1.666 offer over 1.2?
Well, as far as I can tell, it runs much faster, has a phone book
option for modem play, has strings for many popular modems, now supports
up to 28.8 kps, includes an option for a time limit on levels in
deathmatch, and also the Deathmatch 2.0 rules.
: Paul.
10 minutes was long enought for me to think the thing had crashed and was
happily writing in some queer loop. I aborted when it was nearly done,
as evidenced by 8 megs of lost clusters. So I waited a little longer the
next time and it worked. Obviously they are writing a second 10 meg
doom.wad and then deleted the first. I think I would have liked a notice
that it would take a long time.
Jason
: Paul Clarke (pa...@prl.philips.co.uk) wrote:
Having one of these high spee modems I was ofcourse impressed,
until I tried to use it. The setup strings atomatically default
to 9600 (slowwwwww) and upon connection (since mnp is on) promptly
lose connection but don't bother to let you know ...
Moral - check out the modem stuff your self before
trusting the default strings.
-Terry
Faster? On my AMD-DX40 with plenty of ram and a VL5428-based card I
get a drop in FPS from 19 to 13. Back to 1.2.
/Mikael
--
Mikael Nordqvist, student | d9...@efd.lth.se | I'm not paraniod, it's just
Lund Institute of Technology | me...@df.lth.se | that everyone is out to get me
>Gilles Gravier (cor...@cedre1.ensta.fr) wrote:
>: In article <CvqxF...@sunfish.usd.edu>,
>: Cymbrogi <cpu...@camelot.uk.old> wrote:
>: (... SNIP ...)
>: >
>: > Now, don't get me wrong. I'm very happy about the patch being
>: >out, but I gotta warn ya...the process of patching is LOOONNNGGG!!!! I
>: >timed it, and it took well over an hour of non-stop disk spinning. *yawn*
>: Are you running a 10 MHz 80286 without a WRITE DISK CACHE? On my 486 DX 40,
>: with SMARTDRV 5.01 configured for Write Cacheing, it took less than 10 small
>: minutes...
> Well, I am running a 486sx-33mhz, with a write AND read disk
>cache and yes, it took well over an hour as I stated before.
>Hmmm...about the only thing that I can think of is that I have it on a
>SCSI drive and not an IDE drive. (I added the SCSI when I switched from
>Apple to IBM-Clone). That's probably it. (and the drive is crammed full too)
SCSI drive... that won't slow it down.
crammed full... THAT'LL slow it down.
I took my system 5m30sec to patch... P-66
My neighbor's took 8min... 486DX-33
Generally I would advise all gamers to get a REAL 486, not an SX.
[Cymbrogi needs 1 hour to patch DOOM on 486sx-33 with almost-full
SCSI Hard drive ]
>
>SCSI drive... that won't slow it down.
>crammed full... THAT'LL slow it down.
Yep. The patch program makes a new WAD file and deletes the old one.
Trying to stuff a 10 Meg file into all the little nooks and crannies
will take a while. DOOM will probably take longer to load until
you defrag the disk.
>I took my system 5m30sec to patch... P-66
>My neighbor's took 8min... 486DX-33
>
>Generally I would advise all gamers to get a REAL 486, not an SX.
NO! The 486SX is a "real 486" except without a math coprocessor.
Most games do not use the coprocessor, so this is really not an
issue. This is not the same as the 386/386SX where one had a
narrower bus. For integer operations, the 486SX and 486DX will
have the exact same performance.
------------------ Frank Racis - FWR...@psuvm.psu.edu -----------------
It's only ones and zeros.
-------- Actually, I'm a lab mouse out to take over the world. --------
: Are you running a 10 MHz 80286 without a WRITE DISK CACHE? On my 486 DX 40,
: with SMARTDRV 5.01 configured for Write Cacheing, it took less than 10 small
: minutes...
Well, I am running a 486sx-33mhz, with a write AND read disk
cache and yes, it took well over an hour as I stated before.
Hmmm...about the only thing that I can think of is that I have it on a
SCSI drive and not an IDE drive. (I added the SCSI when I switched from
Apple to IBM-Clone). That's probably it. (and the drive is crammed full too)
: Don't you just love it when things finaly come out?
>Ralf Southard (rp...@psu.edu) wrote:
>: SCSI drive... that won't slow it down.
>: crammed full... THAT'LL slow it down.
>: I took my system 5m30sec to patch... P-66
>: My neighbor's took 8min... 486DX-33
>: Generally I would advise all gamers to get a REAL 486, not an SX.
> Well la-tee-fuckin'-da!!! Some of us can't afford to buy a new
>computer every generation. I had to scrape to buy the 486 sx-33 2 years
>ago when it was about the most you could get on a student budget. And
>I've ran tests on systems with the math-co and without (dx vs. sx) to
>reveal that the difference in performance wasn't worth the difference in
>price (I didn't want to spend an additional 300-500 bucks that I didn't
>have for a few extra seconds here and there.)
Whoa! Forgive me for expressing my opinion, without vulgarity no less. If you
bought a 486 SX-33 two years ago, you had quite a budget. I couldn't afford a
486 of any kind until 1993. I only mentioned the SX/DX because there is very
little difference in price these days. 486-33's are now becoming entry level
machines, partly because they're below the $1200 mark.
As for student budgets, I could afford more as a student than I can in real
life now.
> Oh, btw, *my* neighbor's 486sx-25 with an empty hd took almost as
>long to patch as mine. So I have different experiences.
Oh, btw, I repeat, my neighbor's took 8 minutes... period.
> The patch is worth it...I never said otherwise. I just felt that
>people should know of my experience with it, that's all. Sorry for not
>having a REAL 486, but it runs just fine for me.
Don't be sorry, sharing your experience is great, and that's what I did.
EVERYBODY... GET THIS PATCH... YOU won't be sorry.
Hmm. How much exactly is "plenty"? Anyway, it sure seems faster to me.
Besides, v1.666 has lots of other "new" stuff:
DeathMatch 2.0
better serial/modem connections
new stuff (sounds, secrets, etc.)
I'm sticking with it.
--
===============================================================================
| "So I open my door to my enemies |
| And I ask could we wipe the slate clean Mike Newton |
| But they tell me to please go fuck myself <m...@netcom.com> |
| You know you just can't win" |
| -Pink Floyd |
===============================================================================
: SCSI drive... that won't slow it down.
: crammed full... THAT'LL slow it down.
: I took my system 5m30sec to patch... P-66
: My neighbor's took 8min... 486DX-33
: Generally I would advise all gamers to get a REAL 486, not an SX.
Well la-tee-fuckin'-da!!! Some of us can't afford to buy a new
computer every generation. I had to scrape to buy the 486 sx-33 2 years
ago when it was about the most you could get on a student budget. And
I've ran tests on systems with the math-co and without (dx vs. sx) to
reveal that the difference in performance wasn't worth the difference in
price (I didn't want to spend an additional 300-500 bucks that I didn't
have for a few extra seconds here and there.)
Oh, btw, *my* neighbor's 486sx-25 with an empty hd took almost as
long to patch as mine. So I have different experiences.
The patch is worth it...I never said otherwise. I just felt that
people should know of my experience with it, that's all. Sorry for not
having a REAL 486, but it runs just fine for me.
/>
\ /< "I took his head, and raped his woman
{\\\\\\(0):::<======================================-
/ \< before his blood was even cold!"
\> -- Kurgan
GIMME THE PRIZE!!
I did a test last night. On my wife's computer, a 386 dx 25 with 8 megs of
ram and a slow hard drive (.29 access), the Doom patch took about 15 mintues.
On my 486 with much better hard ware, it took close to 1/2 hour. The
difference being, my wife has an unfragmented drive with lots of space
to spare, my 486 has a fragmented drive and only about 10 megs free.
So, my best suggestion is to clear off some space and defragment your hard
drive before applying the doom 1.666 patch.
Robert Merritt (who has nothing better to do at night than to test out the
speed of the doom patch until my 2x cd rom mm kit shows up in the mail)
-* Disclaimer: Opinions posted here are mine and not of my employer
-*"There is always death and taxes. However death doesn't get worse every year"
>Ralf Southard (rp...@psu.edu) wrote:
>: In article <Cvp8u...@bfsec.bt.co.uk> ddo...@bfsec.bt.co.uk (Damian Dougan) writes:
>: >From: ddo...@bfsec.bt.co.uk (Damian Dougan)
>: >Subject: Doom 1.666 Out !!!
>: >Date: Tue, 6 Sep 1994 08:27:39 GMT
>
>: >Hello All,
>
>: >Doom 1.666 patch is out on
>: >Happy Dooming!
>
> Now, don't get me wrong. I'm very happy about the patch being
>out, but I gotta warn ya...the process of patching is LOOONNNGGG!!!! I
>timed it, and it took well over an hour of non-stop disk spinning. *yawn*
Which kind of system are you using? Although I have a pentium 60MHz (not
>What exactly does version 1.666 offer over 1.2?
I don't know, but I hope they added one thing:
I want to be able to calibrate the joystick while
in the game. It is REALLY frustrating to start a
game and find out I messed up the calibration. I
then have to exit Doom and restart. THIS SUCKS!!!
Mario
***********************************************************
* ___ ____ ____ *
* /o o\ //oo\\ ( oo ) Mario D'Alessio __/\__ *
* \_O_/ \__/ \__/ dale...@rtsg.mot.com \RUSH/ *
* WooWoo Work: (708) 632-2323 |/\| *
* Woo 9am to 6pm Central Time *
* *
***********************************************************
It only took me about 60 seconds and I have a dx2/66! How slow is
your hard drive if it took 5-7 minutes on a 66 machine?
Craig
unfortunately I didn't see anything like that in it... (I just got
the patch yesterday.) It would have been nice though... and I'm
glad to see someone else has that problem...
-ed
: Suggest you buy a faster disk? It took less than 5 minutes on my machine
: so don't be put off. Get the patch and install it!
I have DOOM v1.4. Do I have to get the patch to 1.5 to upgrade to 1.6? if so,
could someone please post the locations of both of those patches?
Thanks in advance..
--Steve Tiilikainen
: Well, I am running a 486sx-33mhz, with a write AND read disk
: cache and yes, it took well over an hour as I stated before.
: Hmmm...about the only thing that I can think of is that I have it on a
: SCSI drive and not an IDE drive. (I added the SCSI when I switched from
: Apple to IBM-Clone). That's probably it. (and the drive is crammed full too)
My first guess is that your drive is very badly fragmented. If you have
DOS 6, try DEFRAG and see if that makes a difference. If you don't have
DOS 6 or something like Norton, look on Simtel for a program called DOG.
Always worked great for me. I only have a 386-33 and it probably only
took 15-20 minutes for me (course I was expecting it to take a while and
was watching TV at the time.)
Mark Harrison
harr...@sun.lclark.edu
: I did a test last night. On my wife's computer, a 386 dx 25 with 8 megs of
: ram and a slow hard drive (.29 access), the Doom patch took about 15 mintues.
: On my 486 with much better hard ware, it took close to 1/2 hour. The
: difference being, my wife has an unfragmented drive with lots of space
: to spare, my 486 has a fragmented drive and only about 10 megs free.
: So, my best suggestion is to clear off some space and defragment your hard
: drive before applying the doom 1.666 patch.
Also, if the patch terminates with a disk full error, it doesn't clean
things up properly (you have to run chkdsk or scandisk), so making
sure you have enough space before you start is a good thing...
Dave
: I have DOOM v1.4. Do I have to get the patch to 1.5 to upgrade to 1.6? if so,
: could someone please post the locations of both of those patches?
If you have DOOM1.4, you have the shareware version. Just download the
shareware version of 1.666.
Howard
--
st...@okcforum.osrhe.edu | "Remember, the truth that once was spoken:
I speak for no one but myself, | to love another person is to see the face
and no one else speaks for me. | of God." - Les Miserables fnord
Commence strategic maneuvers at audio command signal. 5, 4, 3, 2, 1, begin.
heh. I have a 386/25 DX (*gag*, *puke!*) and it took me 5 minutes. I have
the patched v1.666 doom on my 424 meg IDE HD
:)
--Steve Tiilikainen
I'm not sure I saw anybody answer this yet. Well, the sound works a bit
better now, I know that in v.1.2 my Thunder Board sometimes had trouble
when too many things were happening at once; that's fixed. Also, the new
deathmatch rules are an option. And, the shareware version won't read WAD
files. But even more noticeable to me: the armor rating only goes up to
%200 now, and you can record deathmatch demos that you can watch from
various player's perspectives! It may actually run faster now, I'm not
sure.
> > Well, I am running a 486sx-33mhz, with a write AND read disk
> >cache and yes, it took well over an hour as I stated before.
> >Hmmm...about the only thing that I can think of is that I have it on a
> >SCSI drive and not an IDE drive. (I added the SCSI when I switched from
> >Apple to IBM-Clone). That's probably it. (and the drive is crammed full too)
>
> SCSI drive... that won't slow it down.
> crammed full... THAT'LL slow it down.
I believe if the SCSI drive is used to boot up as IDE drive, it will
slow it *WAY* down.
--
Email : hkc...@hkchan.pc.my