Annoying winmm.dll problem with 64-bit winxp and a feature suggestion.

Discussion in 'Other Ghost Security Software' started by Someone far away, Dec 2, 2005.

Thread Status:
Not open for further replies.
  1. The problem:
    When I open ghostwall's GUI for the first time after boot, it always gives the "Couldn't locate winmm.dll" error even though I have the winmm.dll in syswow64 and ghostwall directories. The GUI seems to run perfectly regardless of the error, but you can't actually do anything because the error window is always focused. So, I have to kill ghostwall and restart it manually. After restarting ghostwall the problem is gone, but this is really starting to bug me.

    The suggestion:
    If you are going to implement simple application allow/block control as a separate program, it would be really nice if you could also restrict applications's upload and download speeds ( because all of us don't want to give our whole band width to one app ). This could also be a separate program, so those who don't need it don't have to get it. Also separate programs could be easily managed if they had a single tray icon.
     
  2. vSx

    vSx Guest

    copy the winmm.dll from Windows/SysWow64 directory in the windows/system direc.
     
  3. Hi,

    I have a similar problem but it only appears when I bring up the GUI and Trillian is running in the backgroud. It locks the windows until I disable Trillian. Somehow I can run both trillian and Ghoswall at the same time but not the Ghostwall GUI.

    http://www.ceruleanstudios.com/ I use version 3.1 Basic Build 121
    Windows XP Pro X64

    Thanks.
     
  4. Hermescomputers

    Hermescomputers Registered Member

    Joined:
    Jan 9, 2006
    Posts:
    1,069
    Location:
    Toronto, Ontario, Canada, eh?
    :eek: I would feel a bit uncomfortable doing this because both directories include the file. However it doesnt seem to be the same file since both files are different sizes..
    C:\WINDOWS\system32 = 303 KB (310,784 bytes)
    C:\WINDOWS\SysWOW64 = 172 KB (176,640 bytes)

    What gets me is they both have the same created/modifications dates = March 25, 2005, 7:00:00 AM

    Anyone with deep insight into this?

    Guy
     
  5. donkyboy

    donkyboy Registered Member

    Joined:
    Jan 21, 2006
    Posts:
    1
    Location:
    Adelaide
    did this work for you as i have the sam problem i have out the c:\WINDOWS\SysWOW64\winmm.dll = 172 KB (176,640 bytes)
    into my install dir this did fix it for a few days now im getting the error again

    im not sure i want to copy the file to my c:\windows\system dir unless i know it works.

    also i am running trillian pro 3.1 Build 121 maybe this is the problem program incompatibility

    i have asked my friend with xp64 he is using identical setup to me except for the trillian progie and guess wot he doesnt have this problem

    hope this info helps if you require anymore about my setup post here and i will answer
     
  6. Hermescomputers

    Hermescomputers Registered Member

    Joined:
    Jan 9, 2006
    Posts:
    1,069
    Location:
    Toronto, Ontario, Canada, eh?
    I did attempt to copy the file and over write the other one but it refused stating the file was already locked by another program. I couldnt figure which program it was so I gave up.

    Besides the problem for me is only when I open the GUI of Ghostwall while Trillian is running... I can manage fine enough but it's a bit annoying.
     
  7. nick s

    nick s Registered Member

    Joined:
    Nov 20, 2002
    Posts:
    1,430
    Hi Hermescomputers,

    Copying winmm.dll from \WINDOWS\SysWOW64 to \WINDOWS\system should eliminate the error for you. Tested it here with the latest Trillian Basic on x64. The error though did appear only after installing Trillian.

    Nick
     
  8. "Copying winmm.dll from \WINDOWS\SysWOW64 to \WINDOWS\system should eliminate the error for you. Tested it here with the latest Trillian Basic on x64. The error though did appear only after installing Trillian."

    I was getting teh same error, but the above post did the trick thanks.
     
Thread Status:
Not open for further replies.