Reply to topic

Gizmo not working on Windows 2000
gerry yates


Joined: 16 Feb 2009
Posts: 3
Reply with quote
using Win2K....

get message
"Error loading Gizmo Village module(GVILLAGE.DLL)
This object is required to run Gizmo"

Any suggestions to how to fix ( or can i go back to previous version)?
View user's profileSend private message
Logan Mueller
Support

Joined: 16 Nov 2003
Posts: 565
Reply with quote
Hi Gerry,

It sounds like something may have gotten botched up during the update. Have you tried downloading the installer from this web site and installing it on top of your current installation, just to see if this makes a difference?

Gizmo should run on Win2k. If you still get the error, then you may also want to use Dependency Walker on gvillage.dll (typically located in C:\Program Files\Gizmo) to see which dependencies are missing.

_________________
Support is provided as a convenience to our users. We make no guarantees in the timeliness and accuracy in our responses. We reserve the right to refuse service to anyone.
View user's profileSend private messageVisit poster's website
gerry yates


Joined: 16 Feb 2009
Posts: 3
Reply with quote
ttried reloading over the top...
no difference.
tried dependancy walker it showed the following problems

apphelp.dll missing file

Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.
View user's profileSend private message
Logan Mueller
Support

Joined: 16 Nov 2003
Posts: 565
Reply with quote
OK, APPHELP.DLL is delay-load, which actually means it's OK for it to be missing. So it looks like you're good on dependencies.

Do you remember which version you were running before you upgraded to v2.7?

_________________
Support is provided as a convenience to our users. We make no guarantees in the timeliness and accuracy in our responses. We reserve the right to refuse service to anyone.
View user's profileSend private messageVisit poster's website
gvillage.dll problem on fresh install
David Zimmerman


Joined: 18 Feb 2009
Posts: 3
Reply with quote
Hi, I too am getting a error that stops the program from running after a new install. Using fully updated Win2K. (That dependency walker program works great.. thanks for the tip).
In windows on double-clicking the icon, it won't start, but it brings up an error message about gvillage.

In (depwalkr)
"Error opening file, the system cannot find the file specified.(2)"

Also throwing some warnings:
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.


MPR.dll is highlighted in red too.

{first time.. never installed Gizmo before)
During install, I did not select the switch for placing the software in startup
View user's profileSend private message
Logan Mueller
Support

Joined: 16 Nov 2003
Posts: 565
Reply with quote
Hi David,

Thanks for posting this info. Those last two warnings look OK, since they are from delay-load modules that Gizmo does not use, but that first error, regarding the missing file, can you see what it is referring to? Does the (2) corresponding with anything on the top pane?

We're going to try some things in the v2.7.1 release to hopefully fix things on Win2k. We think the added resources, for the new help file in v2.7, might be the culprit, as Win2k may not be used to this many resources and cannot load the DLL properly.

But strangely, Gizmo works on our Win2K machines. This is a very odd problem!

_________________
Support is provided as a convenience to our users. We make no guarantees in the timeliness and accuracy in our responses. We reserve the right to refuse service to anyone.
View user's profileSend private messageVisit poster's website
David Zimmerman


Joined: 18 Feb 2009
Posts: 3
Reply with quote
I saw an interesting posting here:
http://answers.google.com/answers/threadview?id=366517

.. but in looking in my system directory (WINNT) I do not have a APPHELP.DLL anywhere.

But then again checking the FAQ at:
http://www.dependencywalker.com/faq.html
I should not have or want this file. (I'm using IE 6.2800.1106)

Like you said, you'll have a .1 incremental release. I do thank you for looking at this so promply. You have excelent feedback and a very polished and professional website. Quality. Well done.
View user's profileSend private message
David Zimmerman


Joined: 18 Feb 2009
Posts: 3
Reply with quote
Since your Win2K version is running, here is just the last bit of the run log from a non-working instance, where GVILLAGE is called:
----------- snip (4 lines early) -------------
GetProcAddress(0x75030000 [WS2_32.DLL], "WPUCompleteOverlappedRequest") called from "WS2_32.DLL" at address 0x7503DB40 and returned 0x7503D5B8.
GetProcAddress(0x75030000 [WS2_32.DLL], "WSAProviderConfigChange") called from "WS2_32.DLL" at address 0x7503DB40 and returned 0x750376FF.
GetProcAddress(0x75030000 [WS2_32.DLL], "WSCWriteProviderOrder") called from "WS2_32.DLL" at address 0x7503DB40 and returned 0x7503D37C.
GetProcAddress(0x75030000 [WS2_32.DLL], "WSCWriteNameSpaceOrder") called from "WS2_32.DLL" at address 0x7503DB40 and returned 0x750395BA.
LoadLibraryA("gvillage") called from "MFC42.DLL" at address 0x6C400E00.
Loaded "GVILLAGE.DLL" at address 0x00BB0000. Successfully hooked module.
Loaded "GRENDER.DLL" at address 0x00F20000. Successfully hooked module.
Loaded "OLEAUT32.DLL" at address 0x779B0000. Successfully hooked module.
Loaded "OLEPRO32.DLL" at address 0x695E0000. Successfully hooked module.
Loaded "WININET.DLL" at address 0x63000000. Successfully hooked module.
Loaded "CRYPT32.DLL" at address 0x7C740000. Successfully hooked module.
Loaded "MSASN1.DLL" at address 0x77430000. Successfully hooked module.
DllMain(0x00F20000, DLL_PROCESS_ATTACH, 0x00000000) in "GRENDER.DLL" called.
DllMain(0x00F20000, DLL_PROCESS_ATTACH, 0x00000000) in "GRENDER.DLL" returned 1 (0x1).
DllMain(0x779B0000, DLL_PROCESS_ATTACH, 0x00000000) in "OLEAUT32.DLL" called.
GetProcAddress(0x7C570000 [KERNEL32.DLL], "IsTNT") called from "OLEAUT32.DLL" at address 0x77A248A2 and returned NULL. Error: The specified procedure could not be found (127).
GetProcAddress(0x7C570000 [KERNEL32.DLL], "IsProcessorFeaturePresent") called from "OLEAUT32.DLL" at address 0x77A27D4B and returned 0x7C597B45.
GetProcAddress(0x7C570000 [KERNEL32.DLL], "SetCriticalSectionSpinCount") called from "OLEAUT32.DLL" at address 0x779C844B and returned 0x77F8EFA2.
GetProcAddress(0x7C570000 [KERNEL32.DLL], "SetCriticalSectionSpinCount") called from "OLEAUT32.DLL" at address 0x779C844B and returned 0x77F8EFA2.
LoadLibraryA("C:\WINNT\system32\ole32.dll") called from "OLEAUT32.DLL" at address 0x77A10170.
LoadLibraryA("C:\WINNT\system32\ole32.dll") returned 0x7CE20000.
GetProcAddress(0x7CE20000 [OLE32.DLL], "DcomChannelSetHResult") called from "OLEAUT32.DLL" at address 0x77A10185 and returned 0x7CE6C864.
DllMain(0x779B0000, DLL_PROCESS_ATTACH, 0x00000000) in "OLEAUT32.DLL" returned 1 (0x1).
DllMain(0x695E0000, DLL_PROCESS_ATTACH, 0x00000000) in "OLEPRO32.DLL" called.
GetProcAddress(0x7C570000 [KERNEL32.DLL], "IsTNT") called from "OLEPRO32.DLL" at address 0x695F2B22 and returned NULL. Error: The specified procedure could not be found (127).
GetProcAddress(0x7C570000 [KERNEL32.DLL], "IsProcessorFeaturePresent") called from "OLEPRO32.DLL" at address 0x695F4BCB and returned 0x7C597B45.
GetProcAddress(0x779B0000 [OLEAUT32.DLL], "OleIconToCursor") called from "OLEPRO32.DLL" at address 0x695F2787 and returned 0x779FCA70.
GetProcAddress(0x779B0000 [OLEAUT32.DLL], "OleCreateFontIndirect") called from "OLEPRO32.DLL" at address 0x695F2787 and returned 0x779F2BD0.
GetProcAddress(0x779B0000 [OLEAUT32.DLL], "OleCreatePictureIndirect") called from "OLEPRO32.DLL" at address 0x695F2787 and returned 0x779FB810.
GetProcAddress(0x779B0000 [OLEAUT32.DLL], "OleLoadPicture") called from "OLEPRO32.DLL" at address 0x695F2787 and returned 0x779FB9E0.
GetProcAddress(0x779B0000 [OLEAUT32.DLL], "OleTranslateColor") called from "OLEPRO32.DLL" at address 0x695F2787 and returned 0x779F5DD0.
GetProcAddress(0x779B0000 [OLEAUT32.DLL], "OleCreatePropertyFrame") called from "OLEPRO32.DLL" at address 0x695F2787 and returned 0x779F7780.
GetProcAddress(0x779B0000 [OLEAUT32.DLL], "OleCreatePropertyFrameIndirect") called from "OLEPRO32.DLL" at address 0x695F2787 and returned 0x779F7730.
DllMain(0x695E0000, DLL_PROCESS_ATTACH, 0x00000000) in "OLEPRO32.DLL" returned 1 (0x1).
DllMain(0x77430000, DLL_PROCESS_ATTACH, 0x00000000) in "MSASN1.DLL" called.
DllMain(0x77430000, DLL_PROCESS_ATTACH, 0x00000000) in "MSASN1.DLL" returned 1 (0x1).
DllMain(0x7C740000, DLL_PROCESS_ATTACH, 0x00000000) in "CRYPT32.DLL" called.
LoadLibraryA("advapi32.dll") called from "CRYPT32.DLL" at address 0x7C74654C.
LoadLibraryA("advapi32.dll") returned 0x7C2D0000.
GetProcAddress(0x7C2D0000 [ADVAPI32.DLL], "CryptAcquireContextW") called from "CRYPT32.DLL" at address 0x7C74655F and returned 0x7C2DF311.
GetProcAddress(0x7C2D0000 [ADVAPI32.DLL], "CryptSignHashW") called from "CRYPT32.DLL" at address 0x7C746571 and returned 0x7C3051E1.
GetProcAddress(0x7C2D0000 [ADVAPI32.DLL], "CryptVerifySignatureW") called from "CRYPT32.DLL" at address 0x7C746583 and returned 0x7C3052E1.
GetProcAddress(0x7C2D0000 [ADVAPI32.DLL], "CryptSetProviderW") called from "CRYPT32.DLL" at address 0x7C746595 and returned 0x7C305439.
LoadLibraryA("kernel32.dll") called from "CRYPT32.DLL" at address 0x7C7475E1.
LoadLibraryA("kernel32.dll") returned 0x7C570000.
GetProcAddress(0x7C570000 [KERNEL32.DLL], "RegisterWaitForSingleObject") called from "CRYPT32.DLL" at address 0x7C7475FC and returned 0x7C59C7D1.
GetProcAddress(0x7C570000 [KERNEL32.DLL], "UnregisterWaitEx") called from "CRYPT32.DLL" at address 0x7C747616 and returned 0x7C59C90A.
LoadLibraryA("advapi32.dll") called from "MSASN1.DLL" at address 0x77434E4F.
LoadLibraryA("advapi32.dll") returned 0x7C2D0000.
GetProcAddress(0x7C2D0000 [ADVAPI32.DLL], "RegOpenKeyExA") called from "MSASN1.DLL" at address 0x77434E65 and returned 0x7C2EF4C0.
DllMain(0x7C740000, DLL_PROCESS_ATTACH, 0x00000000) in "CRYPT32.DLL" returned 1 (0x1).
DllMain(0x63000000, DLL_PROCESS_ATTACH, 0x00000000) in "WININET.DLL" called.
GetProcAddress(0x7C570000 [KERNEL32.DLL], "GetFileAttributesExA") called from "WININET.DLL" at address 0x6305B8A7 and returned 0x7C58751A.
DllMain(0x63000000, DLL_PROCESS_ATTACH, 0x00000000) in "WININET.DLL" returned 1 (0x1).
DllMain(0x00BB0000, DLL_PROCESS_ATTACH, 0x00000000) in "GVILLAGE.DLL" called.
DllMain(0x00BB0000, DLL_PROCESS_ATTACH, 0x00000000) in "GVILLAGE.DLL" returned 0 (0x0).
DllMain(0x00BB0000, DLL_PROCESS_DETACH, 0x00000000) in "GVILLAGE.DLL" called.
DllMain(0x63000000, DLL_PROCESS_DETACH, 0x00000000) in "WININET.DLL" called.
DllMain(0x63000000, DLL_PROCESS_DETACH, 0x00000000) in "WININET.DLL" returned 1 (0x1).
DllMain(0x7C740000, DLL_PROCESS_DETACH, 0x00000000) in "CRYPT32.DLL" called.
DllMain(0x7C740000, DLL_PROCESS_DETACH, 0x00000000) in "CRYPT32.DLL" returned 1 (0x1).
DllMain(0x77430000, DLL_PROCESS_DETACH, 0x00000000) in "MSASN1.DLL" called.
DllMain(0x77430000, DLL_PROCESS_DETACH, 0x00000000) in "MSASN1.DLL" returned 1 (0x1).
Unloaded "GVILLAGE.DLL" at address 0x00BB0000.
Unloaded "WININET.DLL" at address 0x63000000.
Unloaded "CRYPT32.DLL" at address 0x7C740000.
Unloaded "MSASN1.DLL" at address 0x77430000.
LoadLibraryA("gvillage") returned NULL. Error: A dynamic link library (DLL) initialization routine failed (1114).
LoadLibraryExW("C:\WINNT\system32\SSSensor.dll", 0x00000000, LOAD_WITH_ALTERED_SEARCH_PATH) called from "USER32.DLL" at address 0x77E1E4B4.
Loaded "SSSENSOR.DLL" at address 0x061F0000. Successfully hooked module.
DllMain(0x061F0000, DLL_PROCESS_ATTACH, 0x00000000) in "SSSENSOR.DLL" called.
DllMain(0x061F0000, DLL_PROCESS_ATTACH, 0x00000000) in "SSSENSOR.DLL" returned 1 (0x1).
LoadLibraryExW("C:\WINNT\system32\SSSensor.dll", 0x00000000, LOAD_WITH_ALTERED_SEARCH_PATH) returned 0x061F0000.
--------------------- end snip -----------------
at this point a dialog box has been popped with the error message in it.

Hope this helps abit.
View user's profileSend private message
Logan Mueller
Support

Joined: 16 Nov 2003
Posts: 565
Reply with quote
That helps a lot actually, thanks. Everything looks normal except:

DllMain(0x00BB0000, DLL_PROCESS_ATTACH, 0x00000000) in "GVILLAGE.DLL" returned 0 (0x0).

It's really strange, too, since there is nothing in our DLL_PROCESS_ATTACH implementation that would actually return 0, and this probably confirms that something is happening at the OS level. Maybe the additional resources were the source of the problem.

v2.7.1 was just released this afternoon, and we're hoping it will fix this. Otherwise, we may also have to post an earlier version for people to download, until we can really find the cause!

_________________
Support is provided as a convenience to our users. We make no guarantees in the timeliness and accuracy in our responses. We reserve the right to refuse service to anyone.
View user's profileSend private messageVisit poster's website
gerry yates


Joined: 16 Feb 2009
Posts: 3
Reply with quote
sorry for delay in actions been away on site .
just tried 2.7.3 exactly the same....
although your writeup said 2.7.4 was available it downloaded 2.7.3
will try again later.
View user's profileSend private message
Logan Mueller
Support

Joined: 16 Nov 2003
Posts: 565
Reply with quote
OK, we'll keep trying to reproduce this and hopefully find a fix soon.

_________________
Support is provided as a convenience to our users. We make no guarantees in the timeliness and accuracy in our responses. We reserve the right to refuse service to anyone.
View user's profileSend private messageVisit poster's website
Ashley Lord


Joined: 04 May 2011
Posts: 1
Reply with quote
Was this fixed? If so in what release. I am also running Win 2000 SP4 and just upgraded from 2.6.x to 2.7.7 and I now have this issue. I have tried downloading and installing over the top with no luck in stopping this error on Gizmo startup.
View user's profileSend private message
François FOURNY


Joined: 05 May 2011
Posts: 2
Reply with quote
Hi !

The problem on Win-2K resides in the fact that gvillage.dll can't be loaded because it call the following API "ShCreateShellItem" which is not implemented in Shell32.dll (version 5.0.3900.7155) of Windows 2000 Pro SP4 with all MS updates installed.

Hoping it will help to make this very good program working again on Win2K.

Regards from Belgium.
François.
View user's profileSend private message
Logan Mueller
Support

Joined: 16 Nov 2003
Posts: 565
Reply with quote
Hi François,

Thanks for catching that. You're right. Technically this API should not exist on Windows 2000.

v2.7.9 is now available and should address this. Could someone who was having the problem before confirm that it fixes the issue for them?

_________________
Support is provided as a convenience to our users. We make no guarantees in the timeliness and accuracy in our responses. We reserve the right to refuse service to anyone.
View user's profileSend private messageVisit poster's website
François FOURNY


Joined: 05 May 2011
Posts: 2
Reply with quote
Hello Logan.

I just installed version 2.7.9 (Gizmo Drive only) on my Windows 2000 with no problem. Program seems to run correctly (I mounted one ISO to test).
Apparently everything is OK now.

Do not hesitate to ask me to test your program on Windows NT4 or 2000.
I always have a PC double booting these 2 old OS for test purpose.

Thanks and regards from Waterloo (Belgium).
François.
javascript:emoticon('Cool')
View user's profileSend private message
Gizmo not working on Windows 2000
All times are GMT - 8 Hours  
Page 1 of 1  

  
  

 Reply to topic