Jump to content

Recommended Posts

Posted

Here's a shot of TM showing everything I have running right now. All the Fs*** stuff is F-Secure, all the Hp*** stuff is my HP printer, SMax*** is my sound card, the rest you might know already.

post-11612-1207678040_thumb.jpg

  • Replies 52
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

Posted

Viewing the closed (but not ended) ImgBurn processes in Process Explorer (from Sysinternals) might give us more of a clue as to why it's not ending.

 

If you bring up the properties on one of the tasks, you can view the status of the various threads and get stack traces on them all.

Posted

Perhaps an outdated .dll file? Don't know if Borland uses a particular Microsoft .dll file when that 'Browse for folder' process starts.

Posted (edited)

I don't have any Borland products installed.

 

I just downloaded and installed Process Explorer. It shows me properties of any process that really is there but when I try to get the properties of one of the ImgBurn processes that's a "leftover" it hangs and I have to call on TM again.

 

I haven't got a clue how to use Process Manager so if you want some info just ask.

And BTW my DLL's shouldn't be too outdated as I reformatted at Xmas and reinstalled everything by downloading the latest versions and drivers for everything I own. Some programs may have installed DLL's that may be old as some of the programs are old.

Edited by bluesnow
Posted

If double clicking on the ImgBurn process won't work, Process Explorer isn't going to be of any use to us.

 

FYI, when it does work, you should get this box:

 

pe.png

 

The next thing to try is to get windbg from microsoft.

 

http://www.microsoft.com/whdc/devtools/deb...ng/default.mspx

 

Install + open it, then click File -> Open Executable.

 

Browse to the ImgBurn exe and click Open.

 

You'll notice some stuff going into the 'Command' window. It'll soon stop and appear to be doing nothing.

 

Click the 'Debug' menu and then 'Go'.

 

ImgBurn will then load up.

 

Bring up build mode and then click the browse button just as you've done before.

 

Cancel the browse box and then back in windbg, copy + paste everything from the 'Command' window.

Posted (edited)

Here you go . . .

 

And BTW . . . using Process Explorer I got a list of threads pretty much like yours. When I closed ImgBurn all but the first line disappeared and ImgBurn was still resident.

ImgBurn.TXT

Edited by bluesnow
Posted

  1. Please download Malwarebytes' Anti-Malware and save it to a convenient location.
  2. Double click on mbam-setup.exe to install it.
  3. Before clicking the Finish button, make sure that these 2 boxes are checked (ticked):
    • Update Malwarebytes' Anti-Malware
      Launch Malwarebytes' Anti-Malware

[*]Malwarebytes' Anti-Malware will now check for updates. If your firewall prompts, please allow it. If you can't update it, select the Update tab. Under Update Mirror, select one of the websites and click on Check for Updates.

[*]Select the Scanner tab. Click on Perform full scan, then click on Scan.

[*]Leave the default options as it is and click on Start Scan.

[*]When done, you will be prompted. Click OK, then click on Show Results.

[*]Checked (ticked) all items and click on Remove Selected.

[*]After it has removed the items, Notepad will open. Please post this log in your next reply. You can also find the log in the Logs tab. The bottom most log is the latest.

Posted

just in case this scanner is about the best thing available now for the average user

 

there's some pretty nasty stuff running around and a lot of the AV programs are not catching it

Posted

I had to cancel it. It was 45 minutes and still on my smallest drive, but hadn't found anything. I'll restart it tonight and post the result tomorrow.

Posted
Perform full scan
Oppps

 

go for the quick one, it will concentrate on the registry and shell stuff

 

if you have had something bad enough then damage might have been done to your system and a repair disk is necessary

Posted

On a clean install of XP, all I get when I click 'Browse for folder' is:

 

ModLoad: 7e290000 7e401000 C:\WINDOWS\system32\shdocvw.dll

ModLoad: 754d0000 75550000 C:\WINDOWS\system32\CRYPTUI.dll

ModLoad: 5b860000 5b8b5000 C:\WINDOWS\system32\NETAPI32.dll

ModLoad: 771b0000 7727e000 C:\WINDOWS\system32\WININET.dll

ModLoad: 02460000 02469000 C:\WINDOWS\system32\Normaliz.dll

ModLoad: 5dca0000 5dce5000 C:\WINDOWS\system32\iertutil.dll

ModLoad: 76c30000 76c5e000 C:\WINDOWS\system32\WINTRUST.dll

ModLoad: 76c90000 76cb8000 C:\WINDOWS\system32\IMAGEHLP.dll

ModLoad: 76f60000 76f8c000 C:\WINDOWS\system32\WLDAP32.dll

ModLoad: 74e30000 74e9d000 C:\WINDOWS\system32\RichEd20.dll

ModLoad: 71ab0000 71ac7000 C:\WINDOWS\system32\ws2_32.dll

ModLoad: 71aa0000 71aa8000 C:\WINDOWS\system32\WS2HELP.dll

ModLoad: 77920000 77a13000 C:\WINDOWS\system32\SETUPAPI.dll

ModLoad: 77b40000 77b62000 C:\WINDOWS\system32\appHelp.dll

ModLoad: 77a20000 77a74000 C:\WINDOWS\System32\cscui.dll

ModLoad: 76600000 7661d000 C:\WINDOWS\System32\CSCDLL.dll

ModLoad: 76980000 76988000 C:\WINDOWS\system32\LINKINFO.dll

ModLoad: 76990000 769b5000 C:\WINDOWS\system32\ntshrui.dll

ModLoad: 76b20000 76b31000 C:\WINDOWS\system32\ATL.DLL

ModLoad: 769c0000 76a74000 C:\WINDOWS\system32\USERENV.dll

 

Compare that to your:

 

ModLoad: 7e290000 7e401000 C:\WINDOWS\System32\shdocvw.dll

ModLoad: 754d0000 75550000 C:\WINDOWS\system32\CRYPTUI.dll

ModLoad: 76c30000 76c5e000 C:\WINDOWS\system32\WINTRUST.dll

ModLoad: 76c90000 76cb8000 C:\WINDOWS\system32\IMAGEHLP.dll

ModLoad: 5b860000 5b8b4000 C:\WINDOWS\system32\NETAPI32.dll

ModLoad: 42c10000 42cdf000 C:\WINDOWS\system32\WININET.dll

ModLoad: 02380000 02389000 C:\WINDOWS\system32\Normaliz.dll

ModLoad: 42990000 429d5000 C:\WINDOWS\system32\iertutil.dll

ModLoad: 74e30000 74e9c000 C:\WINDOWS\system32\RichEd20.dll

ModLoad: 77fe0000 77ff1000 C:\WINDOWS\system32\Secur32.dll

ModLoad: 71ab0000 71ac7000 C:\WINDOWS\system32\ws2_32.dll

ModLoad: 71aa0000 71aa8000 C:\WINDOWS\system32\WS2HELP.dll

ModLoad: 77920000 77a13000 C:\WINDOWS\system32\SETUPAPI.dll

ModLoad: 77b40000 77b62000 C:\WINDOWS\system32\appHelp.dll

ModLoad: 77a20000 77a74000 C:\WINDOWS\System32\cscui.dll

ModLoad: 76600000 7661d000 C:\WINDOWS\System32\CSCDLL.dll

ModLoad: 10000000 10025000 c:\Program Files\Hewlett-Packard\HP Share-to-Web\HPGS2WNS.DLL

ModLoad: 02460000 02465000 c:\Program Files\Hewlett-Packard\HP Share-to-Web\S2WNSRES.DLL

ModLoad: 7d1e0000 7d49e000 C:\WINDOWS\system32\msi.dll

ModLoad: 02fb0000 03275000 C:\WINDOWS\system32\xpsp2res.dll

ModLoad: 02470000 02476000 c:\Program Files\Hewlett-Packard\HP Share-to-Web\hpgs2wnfps.dll

ModLoad: 325c0000 325d2000 C:\Program Files\Microsoft Office\OFFICE11\msohev.dll

ModLoad: 76980000 76988000 C:\WINDOWS\system32\LINKINFO.dll

ModLoad: 76990000 769b5000 C:\WINDOWS\system32\ntshrui.dll

ModLoad: 76b20000 76b31000 C:\WINDOWS\system32\ATL.DLL

ModLoad: 769c0000 76a73000 C:\WINDOWS\system32\USERENV.dll

 

So you've got a few extras there that are all being used by browse box.

 

Any one of them could be causing it to not terminate properly.

Posted
ModLoad: 10000000 10025000 c:\Program Files\Hewlett-Packard\HP Share-to-Web\HPGS2WNS.DLL
Thank you for that! I disabled HPGS2WNS.DLL using Startup Control Panel from

http://www.mlin.net/StartupCPL.shtml. Then I disabled the Share to the Web

icon on the desktop by right clicking and ticking disable. It seems to have

done the trick - fantastic.

 

I did go 1 step further and uninstalled HP's Memories Disc. Doing that

eliminated a problem with PowerDesk (file manager)/ ExplorerPlus (the one I

use now) not unloading from memory. The program was being held open with 1

hook, I noticed it in Task Manager at 1 time there were 8 copies of PD open

at once!

http://www.windowskb.com/Uwe/Forum.aspx/wi...r-Virtual-Drive

 

You could try to disable that 'HP Share-to-Web' function.

 

:)

Posted

I really thought you had it there, but . . .

 

I uninstalled HP's memories disc, removed the Share to Web thing using that control panel applet, and got rid of HPGS2WNS.DLL altogether. I'm afraid no change.

 

I'm going to continue to work with Mike Lin's applet though and see if I can eliminate some other possibilities. Since Cynthia has seen the same thing with another program it's possible we're on the right track.

 

I'll have to continue in the morning now. I'll run the Malwarebyte software overnight.

post-11612-1207703504_thumb.jpg

ImgBurn_without_HP.TXT

Posted

When you are in safe mode - are there other processes that shows up if you tick the option 'Show processes from all users' in the Task Manager?

 

At least Cynthia and I agree! lol

Don't let it be a bad habit... =))

Posted (edited)

What value is in your ISOBUILD_MRUSourceFolder and ISOBUILD_RecentFiles_Source values in HKEY_CURRENT_USER\Software\ImgBurn?

 

When the tree is opened it navigates to the value passed to it by the API call. If this location isn't there or is hard to get to it may take a while. Closing ImgBurn with a hung Windows Common Dialog will keep the thread that called it open as well.

 

There are styles that can specify no network drives, removable media, etc too, but that would limit ImgBurn functionality...might be a good option though for people that never use network drives/shares...and since the removable media is usually in a locked state during a lot of operations in ImgBurn, trying to Browse for Folder to a drive that is locked, or sometimes even showing it in the panel of Browse For Folder may hang it.

Edited by weisborg
Posted

And what about that thingy if you are on a home network? This can slow things down because "if you have a disconnected mapped drive, it can hang for a bit as Windows tries to connect it". The solution is to untick the setting General --> Maximum File Size.

 

Regards

Posted

Max file size is only to show FAT32 warning in the log. Not sure what that setting could do in this case.

Posted

It looks across all drives. Do a search in Betas for posts by LUK! on "Maximum File Size". I reported this originally, when Firey's PC took forever to report back it was NTFS. LUK! said, untick it and presto, ImgBurn fired up ASAP. However, I am not at all sure if this is related to build mode folder selection, but it's sure worth a try.

 

Regards

Posted

That last log looked different to the other ones.

 

It was easy to see the bit where you'd clicked 'Browse' on the previous ones... on that one, not so much.

 

Any chance you could do it again?

 

OT: The 'Maximum File Size' thing only happens when the program first loads up and is a one time only thing. It won't do anything to the browse box.


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.