Need help getting Visual Running

[T_N_T]

Hello,

I have VP Launcher and the latest version of Visual Pinball, I set everything up properly with the Visual Install Pack, however, I can not get any of the tables to work, I have the roms in the roms folder and the tables in the tables folder, when I try to launch the table I get errors, the main error that I get is "can't open core.vbs" , another error is something about making sure something is in the same folder as the tables, can anyone help me get this thing up and running?

 

[T_N_T]

I put the scripts in the tables folder, but still nothing.

 

[m4paws]

Sounds like you need the VBS files, download here.

 

[T_N_T]

Thank You!!! That worked And now the fun begins

 

[Phoenixx]

Thats odd, because one of the VIPs features is to install the VB Scripts.

(In other words, they should have been there already.)


Wonder what the problem was in your case,...could you please tell me if one of the following applies:

● Did you use the VIPs default Tables folder or did you create (and use) your own somewhere outside the 'Pinball' directory?

● Did you at some point delete and recreate the VIPs Tables folder in the 'Pinball' directory?

● Did you at some point delete the content of the VIPs Tables folder in the 'Pinball' directory?

● Were the table files (.vpt) in subfolders or directly in the Tables folder?

● Did you use one of the VP9 executables, and if so, did you run them from within the 'NanoTech Executables' directory or did you copy the .exe into the 'Pinball' directory?

● Is there any Anti Virus software or anything running that could have prevented the installer from creating the VB Scripts?

● Were there any error- or warning-messages during the VIP installation?

● And if you are running Vista, did you install the VIP (and run VP) 'As Administrator'? This is especially important, because if you do it only with User rights then Vista wont let VP access the VB Scripts and you get exactly these errors.


Would be great if we could figure out what went wrong in your case so i can add it to 'tips and troubleshooting'. Because normally the only things that have to be added manually to a VIP installation are the ROMs and the Tables,...

 

[T_N_T]

Thats odd, because one of the VIPs features is to install the VB Scripts.

(In other words, they should have been there already.)


Wonder what the problem was in your case,...could you please tell me if one of the following applies:

● Did you use the VIPs default Tables folder or did you create (and use) your own somewhere outside the 'Pinball' directory?

● Did you at some point delete and recreate the VIPs Tables folder in the 'Pinball' directory?

● Did you at some point delete the content of the VIPs Tables folder in the 'Pinball' directory?

● Were the table files (.vpt) in subfolders or directly in the Tables folder?

● Did you use one of the VP9 executables, and if so, did you run them from within the 'NanoTech Executables' directory or did you copy the .exe into the 'Pinball' directory?

● Is there any Anti Virus software or anything running that could have prevented the installer from creating the VB Scripts?

● Were there any error- or warning-messages during the VIP installation?

● And if you are running Vista, did you install the VIP (and run VP) 'As Administrator'? This is especially important, because if you do it only with User rights then Vista wont let VP access the VB Scripts and you get exactly these errors.


Would be great if we could figure out what went wrong in your case so i can add it to 'tips and troubleshooting'. Because normally the only things that have to be added manually to a VIP installation are the ROMs and the Tables,...

I am not sure why the original .vbs files that came with the pack I have did not work, I think actually that some of them may have been missing and also I didn't realize that the tables actually need to be in the same folder as the .vbs files. BTW I am running the Windows 7 beta.

 

[m4paws]

Thats odd, because one of the VIPs features is to install the VB Scripts.

(In other words, they should have been there already.)

That's what I thought so I was a little hesitant to recommend that, but sometimes if it walks like a duck, looks like a duck and quacks like a duck - it's a duck.

Hopefully he can enlighten us as to why the VIP perhaps didn't do what it should have. Just out of curiosity, since the VIP is basically multiple install programs compiled into one installer, is it possible this could have happened by either cancelling the portion of the installation that unpacks the scripts or by the VIP installation terminating early for some reason? Not sure at what point in the process the scripts are unpacked, I would assume it's close to last.

 

[Phoenixx]

...sometimes if it walks like a duck, looks like a duck and quacks like a duck - it's a duck.

Thats true.

Anyhow, since it never happened that the VIP would not create the VBS i think the problem was most likely simple human error. He said himself that he didnt realize that Tables and VBS must be in the same folder so thats probably why he got that error at first. In any case it could not have been due to the files because the VBS that come with the VIP are identical to those in the standalone package. And since the VIP includes even more VBS than the standalone package does i can guarantee that there werent any missing either.

(Of course there is a slim chance that some Security prog or even Windows itself considered the VB Scripts potentially malicious and therefore prevented the installer from creating them but in that case the same had applied to the standalone package, so i dont think that that was it.)

Just out of curiosity, since the VIP is basically multiple install programs compiled into one installer...

Actually its only one installer, namely the VIP itself. The only exception is VPMs setup, which is being called up after the installation of the other components is completed. (That means when the VPM setup pops up, its an indicator that the rest has been successfully installed. Otherwise, (meaning in case of an error), the installation would have been halted with an error message before the call for VPMs setup could be executed because the call for VPMs setup is the last command in the setup chain.) The reason for this exception is because VPMs setup already has a GUI to configure VPMs features. Of course i could have the VIP set up VPM as well, but then i either had to make a new initial-setup GUI for VPM, (which is nonsense when i can just as well use the one that already exists), or not offer a initial VPM configuration during the installation at all, and thats just not something i would want to do.

At any rate, the entire Visual Pinball and misc-file installation is done exclusively by the VIP itself. You might call it a unified installer that fully replaces the original VP installer and takes care of the entire rest at the same time,...

 

[T_N_T]

That's what I thought so I was a little hesitant to recommend that, but sometimes if it walks like a duck, looks like a duck and quacks like a duck - it's a duck.

Hopefully he can enlighten us as to why the VIP perhaps didn't do what it should have. Just out of curiosity, since the VIP is basically multiple install programs compiled into one installer, is it possible this could have happened by either cancelling the portion of the installation that unpacks the scripts or by the VIP installation terminating early for some reason? Not sure at what point in the process the scripts are unpacked, I would assume it's close to last.

I think it was just that I didn't have the VBS files in the same folder as the tables, I never used Visual Pinball before though, thats why I came here to find out how to use it properly :)

 

[m4paws]

(Of course there is a slim chance that some Security prog or even Windows itself considered the VB Scripts potentially malicious and therefore prevented the installer from creating them but in that case the same had applied to the standalone package, so i dont think that that was it.)

That seems plausible to me... I would think unzipping a file might not trigger the same security alerts that an installer might.

At any rate, the entire Visual Pinball and misc-file installation is done exclusively by the VIP itself. You might call it a unified installer that fully replaces the original VP installer and takes care of the entire rest at the same time,...

Ah, cool, thanks for the clarification. Did the EIK work that way too? I thought I remembered one of your install kits running multiple installs, but perhaps it was just the VPM portion. (I haven't needed to use it in awhile.)

 

[Phoenixx]

Sorry for replying so late.

No, the EasyInstallKit was totally different. It pretty much just bundled what was already there under a menu but it didnt really do anything (or very little) itself.

The VIP is the exact opposite as it does everything itself, meaning it functions exactly like every other application installer.

 

[m4paws]

Ok. That must be what I'm remembering.

 

[UnitedRoadRed]

I've got a similar issue - I've come back to playing pinball after a while out and I've got the VIP exe and ran the install. I've grabbed some roms and tables and tried to start up Star Wars - it says that it cannot find DE.VBS - de.vbs exists, but in lower case. I've renamed it, but to no avail and I've even put an extra copy in the scripts folder in case it was that.

 

[UnitedRoadRed]

Solved - Windows bl**dy Vista strikes again. Followed the solution in another thread. Would suggest the chap above does the same if appropriate - right click on vpinball.exe and choose properties, set to compatilbility of XP Service Pack 2 and run as administrator and all is good with the world of VP :)

 

[Phoenixx]

CompMode isnt necessary, VP and VPM run fine under plain Vista.

Its all in the RunAsAdmin thing, (in other words the UAC), because this is what denies a user-initiated process access to stuff like scripts unless the user signals that he trusts that process.

Still the best solution: Turn off UAC. If you have your PC under control (good Firewall, reliable VirusScanner, some common sense) you wont need it.