I've tried un-installing vegas4b, going back to vegas4,
and the problem remains. I've tried getting rid of V4,
and installing 4b only, still there.

The problem may have come with vegas4, but I can't be sure
of that. Also I thought this all was unique to just V4, but
when I went back and uesed vv3, the same thing happend.

I deleted all files assosiated with vegas, and did a clean
install with just 4b, didn't help. None of my problems were
present before installing vegas 4, vv3 ran perfect.

This is very frustating to say the least. Finaly I did an upgrade
to Windows xp pro, just to see what would happen, everything went
bonkers. My printer didn't work properly, my scanner didn't work,
even my cd rom drive was reacting wierd. I had a bunch of updates
on a cd but couldn't get them loaded.

Got pissed and un-installed xp, and went back to my original problem.

Thanks,

kpitrl

When XP was running, did you download Service Pack 1?

OUCH!!!

You could try something like sisoft sandra to check memory and other components. Something could have broken coincidentally to installing VV4b.

If the problem started with Vegas, then it could have updated something, one or more of the files that windows uses, possibly related to direct x. Uninstalling vegas or deleting the program files would not have an effect on a newer file or files in your windows folders, and a newer file might not be compatible with something else running on your system. I don't know of a way to counter this other then going to a backup or comparing with another machine etc. It might help to make sure all windows updates are installed, and/or the latest direct x. It's a longshot, but might try installing the .net stuff from the MS update site.

If you go to device manager in windows, it should show you if there are any hardware problems -> all devices should be listed, and there should be no yellow exclamation points or red *x*s or anything. Wouldn't hurt to go through and reinstall all the drivers for each device with the latest ones available, including anything for your motherboard, ide channels etc. [for the ide channels, usually change/update them to windows generic and then back]

Could try eliminating hardware devices in windows to narrow it down, make sure there's no other software starting with windows, try running in safe mode, that sort of thing. Might have to physically remove one or more cards from the PC, like the sound card, firewire card, anything not absolutely necessary for your PC and windows to run in order to try and make sure it wasn't a hardware problem.

If you think all the hardware is OK, easiest way, depending on how much software you have installed, might be to make a disk image if possible of your hard drive (using something like Norton Ghost) just in case, clear the disk and start fresh, probably with win XP *IF* your hardware was compatible. Upgrading to winxp can be iffy, so often best to do it fresh. Might try a reinstall of windows without wiping the disk, though again I'd do a full backup or image first.

"When XP was running, did you download Service Pack 1?"

No, that particular computer is not connected to the internet.
Can you get service pack updates from a different computer?

in the device manager, all devices are said to be funtioning properly.
I have updated the display drivers, which I thought was the problem at
the start of this all.

I also checked under system info, and saw no conflicts listed there.
I think a refomat and a clean install might be my best bet, though as
a last resort hopfully.

This is so strange, I can be editing away, nothing fancy, and everything
just stops, the curser stops, everything. And I can't even do a ctrl/alt/
delete.

Thanks,

kpitrl

Updating to XP you will certainly have to deal with updating drivers (that's just the nature of the beast).

But you mention that you removed all the files associated with VV - but did you take a run through the registry? Unless you actually got rid of ALL the associated and/or shared files...reinstalling another copy (version) isn't going to do anything.

It certainly sounds like a software issue. Outside of the fact that you are using WinME.

I'm not sure what got updated with VVb....but I would look at video driver, DirectX, or speak with SoFo Techsupport for removal process of ALL files and what can be done to restore other files back to their original configs.

Wiping the HD and doing fresh installs would certainly "get rid" of the problems...but that's such a pain in the arse to do. I just finished one over the week end, but they are still no fun!!

One quick question for ya though - can you recreate the times the system crashes? As in - it always goes down when you are working with multiple small files or a few big files.....it goes down 10 minutes after starting, etc, etc.

One thing people over look a lot is getting rid of temp files (that are just siting there sucking resources) - or perphaps any prerendered files that may be sitting out there sucking resources.

Last question - where is your virtual memory sitting? As in - does it reside on your C Drive - or on another drive you have for your system?

I have two HDs and the OS always wants to put it on the C-Drive - but since my D-drive is the largest and fastest of the two...I put the virtual memory there.

Welp, that's all I got. Hope ta hear bak from ya regarding this. I'm sure between me and the other great folks here on the board we can get you some kind of a solution.

Kameron J.

"you mention that you removed all the files associated with VV - but did you take a run through the registry?"

No, the registry is a place where I dodn't have a whole lot of knowledge. I've dabbled there, but I'm not sure what not to delete in some cases.


"It certainly sounds like a software issue. Outside of the fact that you are using WinME."

Are you saying that I may have software that might be conflicting with other software? if so how do I find out? direct X is somthing that I had thought about.

"can you recreate the times the system crashes?"

It seems random, but I'll pay a bit more attention to what I'm doing when it freezes. It doesn't seem to matter if i'm working with video, stills, large, or small files, but I'll pay more attention to that.

I do regularly delete temp, and pre-renders after every project, so we can rule that out.

"where is your virtual memory sitting?"

I'm sure that it's on my (C) drive, I do have two drive, but both are 7200rpm, and both are the same size. Should I move virtual memory off my system drive?

I'll check back in the morn, thanks all for your help, and knowledge. I don't know
where I'd be without this forum, I,m confident that a sollution is just around the corner.

kpitrl

also, (and please don't be insulted) have you defragmented your drives?
and are you running Vegas on a separate drive from the media?
and is the media drive 7200rpm?

all above could contribute to temporary freezes, as CPU tries to catch up with video.

and lastly, how much RAM do you have. if it's under 512, that's the first thing I'd try to fix.
this isn't official (and may be wrong), but I think VV4 is a bit hungrier than VV3 - please correct me if I'm wrong about that assumption.

"have you defragmented your drives? and are you running Vegas on a separate drive from the media? and is the media drive 7200rpm?"

Yes, I defrag after every project. Vegas resides on my (C) drive, and media on (D)Both are 7200 rpm, as for ram I'm maxed out at 512mg.

"(and please don't be insulted)"
All suggestion are welcome, even those that seem insulting ;o)

My system:
Gateway select 1100, 1.1ghz athlon
512mg 133mhz sdram
2-40g 7200rpm hard drives
Nvidia geforce2 mx 32mg video card
motherboard- not sure
windows me (yuk)

I know, it's getting a bit old, but uptill now it worked great.

Thanks, kpitrl

"Are you saying that I may have software that might be conflicting with other software? if so how do I find out? direct X is somthing that I had thought about."

After the fact - it can get a little tricky to determine if there is another application that is causing problems. Personally, I learned never to install more than one piece of software and work with it before moving on to the next one. (including uninstalling). You could do an update of directX (if for no other reasons than S&G). And then see what happens.

As for the register....as long as you make a copy of it before stepping through it - you should be fine. I would look for all the keys with Vegas in it. Perhaps one of the techs would know other keys to look for.

"I'm sure that it's on my (C) drive, I do have two drive, but both are 7200rpm, and both are the same size. Should I move virtual memory off my system drive?"

I always suggest moving the virtual mem to the faster drive that has more available space. If they are both relatively the same...then you may just want to pump up the size a bit. Windows does alright - but I like just a bit more control. Here is a tip....make your "initial size" at least the same as the "maximum".

If all else fails - as a total last last last final final final resort - you could possibly maybe want to think about considering playing around with the thought of thinking about wiping your system and starting over. But I would highly not suggest this unless it is absolutely positively needed.

Hope this helps.

I decided to go fourth with what I concidered a last resort.
I DELETED (Windows Me) and did a clean install with (Win XPpro)
So far so good, I spent most of yesterday gathering drivers, and patches.

Today I bit the bullet, (since time permitted) and hopefully I won't look back.
I had a little trouble with registering, but before I could get Sofo on the phone,
it went through.

One thing I did notice was, most of my favorite fonts were missing in the text
generator. I remember reading that Vegas uses the fonts that are available
on your system, and re-installing pulisher 2000 seem to have done the trick.

I wont know the extent of my success right away, but as I said, so far, so good.
I'd like to take a moment to thank everyone who showed interest in my problem,
especially, Kameron J., and Mikkie.

Thanks to this great forum, nobody has to feel that he's out there, all alone.


kpitrl

Sounds like it's too late, but. I found this the other day.
http://www.belarc.com/free_download.html
They have a program called the "Belarc advisor". It's cool cuz it tells you EVERYTHING which is on/in your machine. Hardware, software, mem the works. I found a couple of things I did not know about and I keep a very tight ship.

It's possible to use this info to see something you were not aware was there and causes conflicts. Good luck