Hey good sleuthing! We'll try to repro this here- could someone provide the Canon scanner's model # and original driver version?

The solution given by Blues_Jam works for me also. (I have a HP and not a Canon scanner though) I renamed the TWAIN_32.DLL file to TWAIN_32.OLD (76KB July 1, 1996 Version 1.6.0.1) and copied the twain_32.dll from the C:\WINDOWS directory to C:\WINDOWS\SYSTEM32.

-Dan

The scanner I have is the CanoScan 5000F, driver version 1.04 (8.0.2.0) but now I'm wondering if this is really a Canon problem. What I'm not sure of is the origin of the 76KB TWAIN_32.DLL file in question which was in the C:\WINDOWS/System32 folder and was dated July 1996. I had assumed it was from Canon, but...

I found a newer 76KB TWAIN_32.DLL file in the
C:\CanoScan\CNQ5000\CNQSG80 folder which is dated Jan 2003.
It also appears in another folder C:\WINDOWS\twain_32. So it seems Canon provided a more up to date TWAIN_32.DLL than the 1996 version.


To reiterate, when I had the problem:

The C:\WINDOWS folder had contained the 46KB lowercase twain_32.dll file dated 8/2001.

The C:\WINDOWS\system32 folder had contained the 76KB TWAIN_32.DLL dated 7/1996.

The C:\CanoScan\CNQ5000\CNQSG80 folder contained a 76KB TWAIN_32.DLL file dated 1/2003.

The C:\WINDOWS\twain_32 also contained the 76KB TWAIN_32.DLL file dated 1/2003.


Now that I don't have the problem:

The change was replacing the 1996 dated 76KB TWAIN_32.DLL file in the C:\WINDOWS/System32 folder. I tried replacing it with both the lowercase 46 KB twain_32.dll file dated 8/2001 version (found in the C:|WINDOWS folder) and the 76KB TWAIN_32.DLL file dated 1/2003 version (found in the CanoScan folder). Either allows Vegas 5 to open without delay.

As an experiment I put back the July 1996 76KB TWAIN_32.DLL file and sure enough wowexec.exe got launched along with Vegas 5.

So where does the July 1996 76KB TWAIN_32.DLL file that was in the C:\WINDOWS/System32 folder come from? Doesn't appear to be from Canon.

I hope all of the above is clear.

The scanner I have is the CanoScan 5000F, driver version 1.04 (8.0.2.0) but now I'm wondering if this is really a Canon problem. What I'm not sure of is the origin of the 76KB TWAIN_32.DLL file in question which was in the C:\WINDOWS/System32 folder and was dated July 1996. I had assumed it was from Canon, but...

I found a newer 76KB TWAIN_32.DLL file in the
C:\CanoScan\CNQ5000\CNQSG80 folder which is dated Jan 2003.
It also appears in another folder C:\WINDOWS\twain_32. So it seems Canon provided a more up to date TWAIN_32.DLL than the 1996 version.


To reiterate, when I had the problem:

The C:\WINDOWS folder had contained the 46KB lowercase twain_32.dll file dated 8/2001.

The C:\WINDOWS\system32 folder had contained the 76KB TWAIN_32.DLL dated 7/1996.

The C:\CanoScan\CNQ5000\CNQSG80 folder contained the 76KB TWAIN_32.DLL file dated 1/2003.

The C:\WINDOWS\twain_32 also contained the 76KB TWAIN_32.DLL file dated 1/2003.


Now that I don't have the problem:

The change is replacing the 1996 dated 76KB TWAIN_32.DLL file in the C:\WINDOWS/System32 folder. I tried replacing it with both the lowercase 46 KB twain_32.dll file dated 8/2001 version (found in the C:|WINDOWS folder) and the 76KB TWAIN_32.DLL file dated 1/2003 version (found in the CanoScan folder). Either allows Vegas 5 to open without delay.

As an experiment I put back the July 1996 76KB TWAIN_32.DLL file and sure enough wowexec.exe got launched along with Vegas 5.

So where does the July 1996 76KB TWAIN_32.DLL file that was in the C:\WINDOWS/System32 folder come from? Doesn't appear to be from Canon.

I hope all of the above is clear.

P.S. Now I see above that dcrandall had this problem but owns an HP scanner.

Since I have an open trouble report with Sony Tech Support, I have sent them a copy of the offending TWAIN_32.DLL file so that they can reproduce the problem.

-Dan

In my case Device Manager reports that I have the CanoScan LiDE 30/N1240U; driver date is 4/15/2002; Version 7.0.0.0; Digital Signer is Microsoft Windows Hardware Compatibility Publisher.

Blues_Jam

and 1000 more thank yous!!!

Wow, Now I'm really happy! I can actually start using Vegas 5 seriously!

Ok Blues_Jam, Rique or anyone esle...if you're ever in Barcelona, Drinks are on me!

All the best,

Paul.

"Since I have an open trouble report with Sony Tech Support, I have sent them a copy of the offending TWAIN_32.DLL file so that they can reproduce the problem."

Did you ever get a reply?

Yes, Sony Technical Support did respond with the following:
"I'm glad to see that there is finally a solution to your problem. It seems the engineers found out about it today as well."

Sounds like Sony Engineering now has acknowledged the problem and is working on a final solution.

-Dan

I too have a Canon scanner (LiDE-80), XP Home, Vegas 5.0b, P4 3.0gHz, Intel mobo. Downloaed and installed latest Canon driver. No help.

Computer regularly crashed to startup (got "CPU has reported hardware failure" or "bad driver" error report) when scanning with Photoshop CS.

Also, the scanner could not be found by Vegas if I used "Get Photo..." It would lock up Vegas and I would have to use Task Manager to end it, then restart Vegas and not attempt to scan from inside Vegas.

I had to scan directly from Photoshop or using the Photoshop-like Canon software and even then it would occasionally stop in mid-scan and crash.

Also, Vegas would hang on the splash screen at startup. My interim fix was to open Vegas again, then open Task Manager and end the version of Vegas with the lower RAM count. It would hang at about 25 MB when it should have been using between 32 MB and 145 MB depending on the size of the file.

After copying the 46 KB lowercase twain_32.dll (mine is dated 3/31/2003) into the system32 folder from the Windows folder, all is well. I renamed the 1996 version TWAIN_32.DLL.old just in case, but it looks like I will trash it.

Rique, you're a genius. Solved scanning problems, hardware crashes and Vegas slow opening. Genius.

Why that ancient 1996 TWAIN_32 driver is in there is a mystery. How could any piece of code that old still be viable for anything???

Genius

Sidecar,

Thanks, but it was really Blues_Jam who discovered the twain file was causing this problem. It would still be nice to know where the '96 version of TWAIN_32.DLL comes from. I didn't notice any mention of this problem in the recent upgrade.

Rique,

Thank you for your acknowledgement.... You are a good man :)

Blues

WOOOOOOHOOOO!!!!!

Thanks to the genius or the geniuses who sorted this thing out. I too have a Canon Lide Scaner and I had the problem with WOW screwing up my multiple Vegas attempts etc. I did the replacement of the DLL and like magic, no problems.

I can tell you that for me it was the Canon Scanner software that introduced that nasty DLL. My bad 76k DLL was dated March 9, 2003 and when I checked to see when my canon scaner software files were modified, which means when they were installed onto my system, it was, you guessed it March 9, 2003.

Thanks Blues_Jam. Your fix made my whole night and the next day.

I suspect this kind of puzzle solving is why the bizarre world of Microsoft is so popular.

That a 46 KB piece of code could bring such satisfaction after so much frustration and Windows NonSpeak ("Windoze has recovered from a serious error. Your CPU says you have a problem. It's with a driver. Good luck finding the bad driver. Did this knowledge base article help?") is quite remarkable.

Thanks again.

Did anyone tell Canon their idiot software is screwing up perfectly stable computers? I doubt it's Sony's fault.

My bet is Vegas's "Get Photo..." feature tries to establish contact with whatever scanner is hooked up. The ancient .dll stops it.

My other version of Vegas 5.0b on a Windows2000 Pro platform that ISN'T connected to a scanner reports a much newer twain_32.dll and opens fine.

ITSS! (It's the stupid scanner!)