|
|
Customers FamilyTrees.GenoPro.com GenoPro version: 3.1.0.1
Last Login: Wednesday, July 2, 2025
Posts: 482,
Visits: 3,296
|
I moved all my genograms to my new computer running Vista Home. I downloaded and installed the latest version of GenoPro I could find (2.0.1.4). I updated a genogram which I had not touched since September 2007 without any problems, but when I tried to generate a report (English narrative report {EN}) it generated following error I looked for the init.htm file but could not find it, so I presume it is a built-in one. There is another post in this forum that deals with this specific error (see Error 8007007E while generating report) specifying that this error can be generated when loading the VBScript engine, and means that "The specified module could not be found". Any idea which module this might be? Another post also mentions the init.htm file but with error 8002801D (see Error at line 182 (init.htm) : 8002801D). Any relation? The funny thing is that I have a full VB6 development environment installed on this Vista system, so I really don't know what module to look for.
Edited: Friday, April 18, 2008 by
GenoProSupport
|
|
|
Important Contributors FamilyTrees.GenoPro.com Customers Translator GenoPro version: 2.0.1.6
Last Login: Tuesday, December 16, 2008
Posts: 390,
Visits: 1,271
|
Init.htm line 183 is:Set oShell = CreateObject("WScript.Shell") |
Maybe due to a missing Script file? Genopro or Ron will be able to explain a bit more in detail. If you're using the '\Customized English Narrative Report\*' skin, you should have init.htm in the Dir. To do so, select the 'English Narrative Report {EN}' skin, click on 'New Skin...' and Genopro should create the Dir mentioned above, i.e. '\Customized ... JC Update: Go to this ad http://www.vistax64.com/vista-installation-setup/67281-windows-vbscript-5-6-a.html and follow the Ramesh tip. The answer may be to register/re-register the VBScript.dll file! I'm no specialist but I don't think you'll harm your system anyway.
Edited: Friday, April 18, 2008 by
GenoProSupport
|
|
|
Customers FamilyTrees.GenoPro.com GenoPro version: 3.1.0.1
Last Login: Wednesday, July 2, 2025
Posts: 482,
Visits: 3,296
|
I tried the Ramish trick but it did not help. Same error on same line.
|
|
|
Customers FamilyTrees.GenoPro.com GenoPro version: 3.1.0.1
Last Login: Wednesday, July 2, 2025
Posts: 482,
Visits: 3,296
|
I also installed Service Pack 6 for Visual Basic 6 (VB6SP6, which I had installed on the XP system). This does not help neither.
|
|
|
Administrators Customers Important Contributors FamilyTrees.GenoPro.com GenoPro version: 3.1.0.1
Last Login: 2 days ago @ 10:10 PM
Posts: 3,428,
Visits: 26,569
|
VB6 is quite a different animal to VBScript, the first is compiled whilst the second is an interpreted language. They just happen to share a similar name and some language semantics.I suggest you download and install Windows Script 5.7. This should already be on Vista but somehow your installation appears corrupt.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
Edited: Sunday, April 6, 2008 by
Ron
|
|
|
Customers FamilyTrees.GenoPro.com GenoPro version: 3.1.0.1
Last Login: Wednesday, July 2, 2025
Posts: 482,
Visits: 3,296
|
Silly me. I believed VB6 and VBS shared big parts of the run-time code. Another illusion blown away.Anyhow, Windows Script 5.7 aborted during the installation, claiming that there is "not enough storage space available". On a system with 3GB of main memory and 258 GB free on the system disk partition, this looks suspicious if you ask me. And yes, I ran the installation as administrator.
Edited: Monday, April 14, 2008 by
Nand
|
|
|
Customers FamilyTrees.GenoPro.com GenoPro version: 3.1.0.1
Last Login: Wednesday, July 2, 2025
Posts: 482,
Visits: 3,296
|
I found a remark in one of the Vista forums about Service Packs and their side-effects. They recommend to remove and re-install the SP. So I removed Vista/SP1 (which I had installed last week) but this did not change anything. I re-installed SP1, still no change. The error persists.Is there a simple way to generate this error (without the use of GenoPro)? If I could isolate the code it would be easier to debug and get support from MS.
|
|
|
Administrators Moderators Customers Gamma FamilyTrees.GenoPro.com Translator GenoPro version: 3.1.0.1
Last Login: Monday, June 2, 2025
Posts: 4,886,
Visits: 22,796
|
Nand (4/10/2008)
I found a remark in one of the Vista forums about Service Packs and their side-effects. They recommend to remove and re-install the SP. So I removed Vista/SP1 (which I had installed last week) but this did not change anything. I re-installed SP1, still no change. The error persists. Is there a simple way to generate this error (without the use of GenoPro)? If I could isolate the code it would be easier to debug and get support from MS. No wonder why so many are downgrading from Vista to XP. My sister purchased a notebook loaded with Vista and could not run the software that was necessary for her work, including printers and accounting software. In the end, we installed XP.
|
|
|
Customers FamilyTrees.GenoPro.com GenoPro version: 3.1.0.1
Last Login: Wednesday, July 2, 2025
Posts: 482,
Visits: 3,296
|
I took a high speed course in VBScripting and created a small script (a variant of the "hello world" classic). Guess what? It ran without problems.So it looks to me that the run-time stuff on Vista is OK. The problem must be located somewhere else.
|
|
|
Administrators Customers Important Contributors FamilyTrees.GenoPro.com GenoPro version: 3.1.0.1
Last Login: 2 days ago @ 10:10 PM
Posts: 3,428,
Visits: 26,569
|
You need to ensure you compare like with like. Some bits of VBSCript obviously work with GenoPro on your Vista system since all the skin files are scripts. Try pasting the following into a .vbs file and run it. Dim oShell, nResponse Set oShell = CreateObject("WScript.Shell") nResponse = oShell.Popup("Hello World?", 0,"Test VBScript Shell" , 32 + &H40000)
|
This tests the same interface that is failing (Wscript.Shell). It runs on my XP Ok. Update You could also try running regsvr32 wshom.ocx from a command prompt. Apparently wshom.ocx provides the WScript Shell feature. If you don't have wshom.ocx in your Windows\System32 folder then that is your problem.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
Edited: Tuesday, April 15, 2008 by
Ron
|