FS2004 Run time error 76 Path not Found

[Nixpilot]

Hey guys,

I'm starting to Sbuilder, but everytime I enter the coordinates into the Class scenery tab, it says Run Time error 76 Path not found and closes sbuilder.

I don't know what's going on.

can anyone help?

 

[Nixpilot]

umm never mind guys.. lol I've fixed it, so if you guys can delete this post ^^'

 

[TerryW]

how did you fix it....I'm getting that message for Sb9.
I've got Win7........

 

[Lane Street]

I too, would like to know how to fix this.

Anyone?

thanks,
Lane

 

[kevintampa5]

had this problem too, I fixed it but cant rememmber what i did. let me check to see what notes I have.

 

[kevintampa5]

If I remember right, it requires SCASM.exe in the TOOLS folder of the Sbuilder folder.

Attached is the file.
IF the file already exist, check the version sizes
this version is
size on disk: 184 KB (188,416 bytes)
size: 180 KB (184,832 bytes)

created on ‎Wednesday, ‎January ‎05, ‎2005, ‏‎7:02:00 PM

This information is in the properties window of SCASM (right click scasm.exe and select properties.)

After that, start Sbuilder and see if it still has the problem

{removed - incorrect information. kevintampa5}

 

[kevintampa5]

Also when 'creating new' confirm the FOLDER options are filled in according to your preferences.

Aslo check this thread
http://www.fsdeveloper.com/forum/showthread.php?t=15077

FSUIPC may be the issue as well, but I cant really remember.

 

[kevintampa5]

you can try making sure the Visual Basic 6 runtime files are complete. sb9 uses them.
verify you followed this
http://www.scruffyduck.org.uk/files/installing_sbuilder.pdf

 

[kevintampa5]

try placin a copy of fsuipc.dll in the sbuilder directory.
I am still thinking its the msxml.dll not being registered, as typical 76 errors usually have something to do with dll, ini, or registry files/entries.

verify msxml4.dll is in C:\Windows\SysWOW64 folder for win7/vista/xp 64bit
and C:\Windows\System32 for win7/vista/xp 32bit
If its not, then you need it.
http://www.microsoft.com/en-us/download/details.aspx?id=15697

 

[kevintampa5]

verify .net framework is up to date.
http://support.microsoft.com/kb/976982/en-us#method2

we will hit it shortly. As this led me to it, one of these will fix it.

 

[Lane Street]

If I remember right, it requires SCASM.exe in the TOOLS folder of the Sbuilder folder.

SBuilder9 downloaded from this site includes scasm.exe 2.96

Also when 'creating new' confirm the FOLDER options are filled in according to your preferences.

Folder options checked, OK. Still no joy.

Also check this thread
http://www.fsdeveloper.com/forum/showthread.php?t=15077

Read that thread, nothing there to help.

FSUIPC may be the issue as well, but I cant really remember.

Nope, FSUIPC is only needed to get position info from FS9. BTW, FSUIPC is installed to the FS9\Modules folder and works fine.

you can try making sure the Visual Basic 6 runtime files are complete. sb9 uses them.

Not sure how to verify that.

I am running Win7 Ult x64 sp1 and it is up to date. I do not get the ActiveX control warnings that are known issues with SBuilder9.

verify you followed this
http://www.scruffyduck.org.uk/files/installing_sbuilder.pdf

That pdf does not apply to the pre-assembled version of SBuilder that is hosted here, which is what I am using.

try placin a copy of fsuipc.dll in the sbuilder directory.

That's not it.

...as typical 76 errors usually have something to do with dll, ini, or registry files/entries.

The error message "path not found" would support this.

I have looked at the SBuilder.ini many times and there is nothing amiss in it, as far as I can tell.

I completely deleted SBuilder9 and installed a fresh copy. Upon first run SBuilder9 successfully copied the *.bmp files from C:\Flight Sim 9\Scenery\World\texture so I am assuming SBuilder has correctly read the registry.

verify msxml4.dll is in C:\Windows\SysWOW64 folder for win7/vista/xp 64bit...[/url]

It's there and working properly, or ADE would not work, and it does.

verify .net framework is up to date.

As stated, Win7 is up to date.

I am open to more ideas.

thanks,
Lane

 

[kevintampa5]

still looking at it.

 

[kevintampa5]

http://www.fsdeveloper.com/forum/showthread.php?p=606235#post606235

Problem solved for one user. Confirm settings for your own operations.

another instance of bgl directory being the cause.
http://www.fsdeveloper.com/forum/showthread.php?t=207151&highlight=runtime

instance of SCASM being the issue
http://www.fsdeveloper.com/forum/showthread.php?t=8743&highlight=runtime

In sbuilder.ini verify
[Main]
PolyTexPath=C:\Program Files (x86)\SBUILDERFS9\Texture (your path to texture)
MacroASDPath=C:\Program Files (x86)\SBuilderFS9\Tools\ASD (your path for asd)
MacroAPIPath= (your path to api if applicable)
Rwy12Path= (your path to rwy12 if applicable)

BGL2Folder=C:\Program Files (x86)\SBuilderFS9\scenery (your path)
BGL1Folder=C:\Program Files (x86)\SBuilderFS9\scenery (your path)

I dont recommend editing the ini itself, rather rename it to sbuilder.ini.bak and reopen sbuilder9 in admin mode, verify you place all paths correctly. a new ini should be generated.

If none of these options work for you, it may be a deeper issue.