Stability of Vegas, 98lite, 98se, 2000

Sonsong wrote on 2/24/2001, 8:31 PM
hello,

have been using 2000 with vegas audio 2b for a week or so.
Have had the system completely lock-up twice. No major
system draining files were playing. I was running maybe 6
or so trax, no more than 2 or 3 plugins on an Athlon 900.

Anyway, i have not settled on 2000. 98se has worked ok for
me in the past and i must say that 98lite sounds
intriguing.What are your experiences with these OS'. Do you
have a definitive preference.

Thanks and be blessed,
Jon

Comments

ramallo wrote on 2/25/2001, 5:58 AM
Hi,

Without a doubt, Windows 2000 pro.

Bye
karlc wrote on 2/25/2001, 8:14 AM
How did you determine that it was the operating system that
caused the lockups?

KAC ...
Rednroll wrote on 2/25/2001, 1:18 PM
I would have to agree with Karl on this one as far as the
OS goes. I installed Vegas on a win2k pro machine about a
month ago and haven't had any problems to speak
of...haven't done a lot of work on that machine either.
I'm having some personal issues with win2k yet and feel
more comfortable as of right now with win98se. But I would
suspect driver support for your hardware, befor the OS when
using win2k, and having issues. Especially when it comes
to soundcards and video cards, which tends to give vegas a
lot of problems when those drivers aren't bug free. Win2k
does seem a lot stabler than 98se and I haven't seen a blue
screen yet or a total lock up when using win2k....ie you
can always "cntrl-alt-del" and terminate a program without
it locking you out entirely like win98 tends to do.

Brian Franz
karlc wrote on 2/25/2001, 2:02 PM

I am with you, Brian ... when Win2K barf's with a DAW, the
first thing I suspect is hardware drivers.

We just got over a period of Mixtreme driver/Win2K problems
that started when we did a driver upgrade about two weeks
ago. Up until that time the machine was as stable as a
rock. (I really hesitate to muck about with a machine that
is working flawlessly, but I also do not like to get to far
behind the curve on upgrades ... and this time I got bit.)

Shortly after installing the ugrade, the machine had a
couple of days of rebooting itself on a whim, no BSOD, no
warning, just "I'm outta here" and a black screen.

Direct e-mail contact over the next 24 hours, with the guy
who actually writes the drivers for Soundscape Digital,
ended up with a driver rewrite on the spot and, voila,
stability again.

BTW, I love those guys at Mixtreme ... where else on earth
can you talk _directly_ to the driver programmer and pass
driver solutions around until the problem is solved?

KAC ...
Sonsong wrote on 2/25/2001, 9:26 PM
Hey guys, thanks for the response.

when the freeze has occurred, i have been unable to ctrl-
alt-del. It is locked solid.

Granted the machine i am using is not my main audio
machine. I have yet to try 2000 on there. i usually use the
yamaha dsp and will be using the Matrox g450 on that
machine.

currently i am using the SBlive and geforce 2 on this
machine. For what its worth, i did up grade to the latest
drivers for the sblive last nite so we shall see.

Anyway, i am not sure about the wdm yamaha dsp drivers or
the Matrox for 2000, but i will soon find out. By the way
does anyone know approx. how many processes run at boot on
a fresh 2000 install with all drivers loaded and no apps
running.

Anymore info on the Yamaha DSPf/Matrox G450/2000/Vegas
would be oh so very appreciated!!!!

Be Blessed,
Jon
studioman3 wrote on 2/27/2001, 5:08 PM
I've been using 2k for a while and it's much less buggy
than 98 (though I still have a seperate but equal machine
with 98 for non-supported apps). Fresh 2k has about 20 +-5
processes on a fresh install, but with 128meg or more,
there shouldn't be a problem. The major problem with 2k is
the fact that no one will attempt to make drivers for pro
audio soundcards. NT uses virtual drivers which apparently
will not allow any software to access any hardware directly
or any unassigned memory. Drivers can be written, but due
to the roundabout way of hardware control, it increases
delay in the input signal and lag for MIDI control. No one
has attempted to find a way around this nor has microsoft
attempted to offer any help. Too bad cause I really dig
the NT platform and I really HATE MSDOS! If someone would
just pay me a disgusting amount of money, I'd find a better
way!
karlc wrote on 2/27/2001, 11:28 PM
Mixtreme is as "pro audio" as you can get and they have
Win2K/NT drivers that work ... as well as a WDM driver for
Win2K.

KAC ...
wolfbayne wrote on 3/2/2001, 10:05 PM
What good are the WDM drivers if Vegas doesn't support the
workaround from Microsoft? My understanding is that you can
only get two channels using Vegas and WDM drivers without
the 30ms latency. Is my understanding incorrect?
jeskridg wrote on 3/8/2001, 3:38 PM
I primarily use Vegas for DV work. NO system lockups when using Vegas. Sometimes vegas crashes and it
only sucks when i haven't saved recently.

But I think maybe I have a similar system hang as you describe. I can't CtrlAltDel out of anything. Mouse pointer
won't move. System is dead and have to restart. I found this typically happens when I'm using Netscape. Maybe
once it happened with vegas but it's been so long I can't remember.

I also have no idea why this happens. But I still prefer Win2k to Win98, I would oftern get Blue Screen using
Win98. Plus for my DV work win2k is much better. I can do DV file work on a 5400rpm IDE drive and my mobo
only supports ATA66. With Win98 you couldn't do that on anything but SCSI. win2k has saved me a lot of
money since I can use cheaper hard drives.

jason