Try starting up your Device Manager before starting up Vegas. Maybe you can at least see what type of hardware Windows is imagining it finds.

Thanks for the heads up. I too have W2k with 512k, so I will wait until next week to install V6.

I've tried everything I can think of so far and still nothing works. The first startup of Vegas 6 after a reboot always takes *ten minutes*. After that Vegas starts up quickly.

I've killed all non-essential processes, cleaned my registry, updated Windows 2000 with every update known to mankind, tried running as administrator and turned off plug-and-play.

I've uninstalled and reinstalled Vegas 6b. I've uninstalled and reinstalled Media Manager. Good lord that component and the database support is over 70MB, what a pig.

I've examined the running process with some tools to monitor file access and system calls, but there is just too much data for me to draw any conclusions. My best guess is that there is access to some resource that is getting blocked and only times out after a number of minutes.

No other program has ever given me this much grief.

I should say that once it does start up, it does seem to work well for the projects I have tried, allowing more tracks and effects in real-time than what I was getting with Vegas 5. I am looking forward to getting the startup problem solved.

I hope Sony is able to figure out why this is happening.

Oh well, off to file a bug report now.

Regards,

Randy

I'm running WIndows 2000 with even less memory (384K). I found that Vegas6 does take longer to start up than Vegas5 - about 3 minutes. Vegas5 takes only about 1 minute. So for me Vegas 6 is significantly slower to start up, but not 10 minutes.

I can wait 3 minutes... I hope to upgrade my machine soon.

Mark

Also V5 is 43 megs, V6 is 93 megs. One of your Win2K driver files is corrupted. The next time it calls for found new hardware check out the device manager to see what it is and re-install that driver.

JJK

>check out the device manager to see what it is and re-install that driver

I would if I could. Device Manager simply lists the entry as "Unknown".

I have cleaned my registry, reinstalled some hardware drivers, checked for hidden devices, anything I can think of.

No other app I have used in two years does this, and these "unknown devices" only appear when I run Vegas 6. Vegas 5 runs fine.

Randy

V6 also installs the SQL server for the media stuff. Might be a problem there or the ECS board. A call to Sony might help.

JJK

I've reported the problem to Sony. I'm not on a support plan, but I am hoping they will help. I would like to get this working after investing $149 for an upgrade that has degraded behavior in this respect.

In the meantime, do any Windows gurus here know how a pure software event can trigger the "Found New Hardware Wizard"? I've only ever experienced the dialog occurring right after a reboot, or plugging in a USB device. I have never seen the launch of an application bring forth this dialog!

Perhaps Vegas 6b is somehow scanning the registry in such a way as to expose a problem with my configuration. But why wouldn't this so-called "new hardware" been found during boot-up? What should I be looking for in the registry? Is there some registry debris that Windows boot-up is able to ignore but Vegas chokes on? I know I won't be able to sleep until I solve this :-(.

Randy

Still haven't got it working.

Could Vegas be assuming that a video capture device exists, and if not it chokes?
I don't have a video capture device installed in my system.

I ask this because I notice that entries in the setupapi.log file that are generated during the failure have some classids which I've found through Google to be related to video capture.

From my setupapi.log file:


Device install function: DIF_SELECTBESTCOMPATDRV.
Selecting best compatible driver caused error: Error 0xe0000228: There are no compatible drivers for this device.
Completed default installer, error: Error 0xe0000228: There are no compatible drivers for this device.
[2005/05/31 23:32:54 468.2]
Munged cmdline: rundll32.exe newdev.dll,DevInstall SW\{c68127b1-9bea-11d0-8fa5-00c04fc324c1}\{65E8773D-8F56-11D0-A3B9-00A0C9223196}
EXE name: C:\WINNT\system32\rundll32.exe
Set selected driver.
Device install function: DIF_SELECTBESTCOMPATDRV.
Selecting best compatible driver caused error: Error 0xe0000228: There are no compatible drivers for this device.
Completed default installer, error: Error 0xe0000228: There are no compatible drivers for this device.
[2005/05/31 23:35:56 224.6 Driver Install]
Device install function: DIF_SELECTBESTCOMPATDRV.
Selecting best compatible driver caused error: Error 0xe0000228: There are no compatible drivers for this device.
Completed default installer, error: Error 0xe0000228: There are no compatible drivers for this device.
[2005/05/31 23:35:56 288.2]
Munged cmdline: rundll32.exe newdev.dll,DevInstall SW\{c68127b1-9bea-11d0-8fa5-00c04fc324c1}\{65E8773E-8F56-11D0-A3B9-00A0C9223196}
EXE name: C:\WINNT\system32\rundll32.exe
Set selected driver.
Device install function: DIF_SELECTBESTCOMPATDRV.
Selecting best compatible driver caused error: Error 0xe0000228: There are no compatible drivers for this device.
Completed default installer, error: Error 0xe0000228: There are no compatible drivers for this device.

Since the delay problem is mainly Windows scanning and finding the "Unknown Device" every time it boots, don't cancel the Found New Hardware Wizard. Let it run, as it won't be able to find any compatible driver for it only the entry will be created, select the unknown device entry in Device Manager and disable it. Once it is marked disabled Windows will skip it during boot time and won't be searching for compatible drivers in its database to configure it. Not a very elegant solution but if the A DIF_SELECTBESTCOMPATDRV command is sent for some reason every time the program runs forcing Windows to perform "Scan for hardware changes" the above solution normally will take precedence over it and skip the specific disabled device. (Don't remove the device just disabled it so that its entry in the Device Manager remains with an X next to it).

Also make sure that this device is actually a "new device" and not an existing device that you had the drivers installed from a disk and that Windows seeing it as new and being unable to configure it moves it to the "Unknown Device" area.

Is it also possible that a device you once had installed and configured from a disk was removed without uninstalling it first and drivers are still present?

I am not using Win2000 and I can't provide any specific information of how the Plug n Play devices are treated under this OS but I think the problem you are having now was there before installing V6 and if at any time you were running the Scan for Hardware changes it would be exhibited.

Vassias

Hello,

Have you ever owned a WinTV card (Huappauge)? If yes, and the card is now removed, but the drivers are still dangling, Vegas could be trying to enumerate the missing device and causing this "found new hardware" wizard to search for the missing device.

Either that, or it could be related to a scanner you had connected to the PC at one time, its no longer there, but your twain drivers are still in place.

Those are the only two types of devices I can think of that Vegas would try to fire upon startup.

r56, thanks for the comments, but as I explained, the problem does not happen at boot, the "Found New Hardware" dialog only appears when Vegas starts up. Vegas is the one calling SELECTBESTCOMPATDRV.

These unknown devices that Vegas creates are placed into the registry at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\SW.

Googling on these two classids that appear in the error entries of setupapi.log for the attempted load of these drivers indicates that they are for Video Capture and Video Render respectively:

65E8773D-8F56-11D0-A3B9-00A0C9223196
65E8773E-8F56-11D0-A3B9-00A0C9223196

So my current theory is that Vegas is trying to find a compatible driver for Video Capture (SELECTBESTCOMPATDRV for 65E8773D-8F56-11D0-A3B9-00A0C9223196), not finding one, then Windows by default responds by firing up a "Found New Hardware Wizard", to have the user load the missing Video Capture driver. I believe "Found New Hardware" is totally misleading here as the condition is really "Can't Find Requested Driver".

Now if I had the Vegas source code I'm sure I could locate the problem in a few minutes :-).

ForumAdmin, I have never had any video device installed in this computer. I did have a Canon FB1200S scanner installed in the past, which has been replaced with a Canon MP 390 Printer/Scanner. I believe I have exised all references to any old devices from the registry, but I will double check this now that you mention it.

I don't have access to a video capture device at the moment, but I would be interested in seeing what happens if I installed one.

ForumAdmin, what happens if Vegas 6b is run on a virgin Windows 2000 system that has never been configured with a Video Capture device?

Thanks,

Randy

Hi Randy,

Please try doing the following:
1) Close Vegas.
2) Go here: C:\Program Files\Sony\Vegas 6.0\Video Hardware Drivers
3) Find the file titled extviddev.dll and rename it to extviddev.dll.bak.
4) Restart your computer, and restart Vegas.

Does the same problem of the "hung" splash screen occur?

ForumAdmin, thanks for that. I'll try it as soon as I get home later tonight. I'll let you know how it works.

Randy

ForumAdmin, I tried renaming the DLL as you suggested but nothing changed.

I've scoured every corner of my registry for anything that looks like it might be a problem.

I even purchased and installed a basic video capture device to see if that had anything to do with it. No luck.

The "Found New Hardware" wizards popping up seem incidental to the real problem. It doesn't matter if I close the dialogs or not, Vegas always starts up after ten minutes. After that Vegas starts in three seconds!

After the first time Vegas starts up, two "Unkown Devices" appear in my Device Manager. I removed them to see if Vegas would start up - it started in three seconds.

I am baffled. No other media software I have used in the last two years on this system has ever behaved like this.

Randy

Another thing I notice that in the Event Viewer, under Application Log,
I see these warnings right about the time Vegas finishes hanging:


Event Type: Warning
Event Source: PlugPlayManager
Event Category: None
Event ID: 256
Date: 6/2/2005
Time: 2:13:30 AM
User: N/A
Computer: FORTUNE
Description:
Timed out sending notification of device interface change to window of ""

Some more observations:

After Vegas starts the first time after a reboot, there are two unknown software devices that appear in the device manager, having something to do with video capture/render.
If I exit Vegas and uninstall these devices, Vegas will still start quickly, so it appears that the presence or absence of these unknown devices is not what is causing Vegas to hang the first time.

What is also interesting is that after I uninstall these unknown devices, and Vegas is *not* running, after a few minutes the "Found New Hardware Wizard" dialogs pop up again. So Vegas is not the process that initiates these dialogs, I suppose it is probably Windows Plug and Play manager service.

Somehow, the initial startup of Vegas tickles the system in such a way that the Windows Plug and Play manager gets confused and causes it to want to install drivers for these unknown devices.

I'm also curious to know exactly how Vegas is communicating with the Plug and Play manager at startup, because there seems to be a disconnect between the two processes that causes the hanging condition to occur.

Again, I am running Windows 2000 SP4 with all of the latest updates.

Why don't you try what I proposed in my earlier reply and disable these devices instead of removing them?
Windows normally should skip executing the command to start the wizard if the specific devices are present but disabled.
It may be a temporary workaround that will let you at least fire up Vegas without going through the cancelling of the wizard and the devices removing.
I understand you want to get to the bottom of this but isn't this worth a try until the proper solution is found?

Vassias

r56, thanks for the suggestion, but I suppose I have not made myself clear in previous posts. This problem is not happening when Windows boots. Your first post led me to believe that this is the impression you are having and that is not the case if you read carefully what I have been reporting.

The problem happens when Vegas ***starts the first time after a reboot***. Starting Vegas is what is causing these unknown devices to be generated. Frankly, I don't care if these unknown devices appear in the system or not, I just want Vegas to start up in less than ten minutes! Nothing I do with these software devices, whether I disable them or uninstall them fixes this problem. After a reboot everything is clean as expected and then the Vegas startup screws it up again. No other media application I have does or has ever done this.

The "workaround" is to live with the ten minute wait each time I start Vegas after a reboot, ignore the "Found New Hardware Wizards" that pop up during the Vegas startup, and ignore the mysterious unknown software devices that appear in Device Manager. As long as I don't reboot again, Vegas will start up fine.

I am not satisfied the "workaround", this is a very annoying problem and I would like to get to the bottom of it, which is why I am posting here.

Randy

Go into the CMOS and turn plug and play off. You don't need it in Win2K anyway. See what happens.

JJK

Thanks, I tried that the other day. No difference.

Yes I understand that this happens the first time you start Vegas after a reboot
I was just suggesting disabling the devices instead of removing because Windows normally would skip starting any service or process that probably could cause 1) Vegas to hang 2) the wizard to start and 3) the devices to get re-scanned.
You didn’t mention that it didn't make any difference whether you disable or remove the devices until the last reply, so now it's perfectly clear.

Vassias