coucou Posted February 2, 2009 Share Posted February 2, 2009 Hi,I'm using WinXP Pro and WPI 6.2 since while, and everything worked like a charm.Today, I undertaked to update my installed progs and the wpi config.js file obviously. Time to time I lauched WPI to verify that everything works.Suddenly by launching wpi.hta, I got a Runtime error (see here/image bellow) A Runtime error has occurredDo you wish to debug?Line: 39Error: 'bit64' is undefinedBy clicking [No], Igot JavaScript Error (see here/image bellow)JavaScript Error ReportMessage 'configs[...].0' is nul or not an objectURL:file:///F:/XPCD_SP2/Software/WPI/WPI.htaFile: check.jsFunction: check0Line: 215By clicking [OK], WPI start but config.js NOT loaded.As i have a copies/backup of that WPI, on other drives in the same computer I tested them... same problem... can't get ride from those errors.Then I made a copy of that WPI (with errors) to a second computer and run it... it works like a charm.Anyone can help how to get ride from those errors?Regardscoucou Link to comment Share on other sites More sharing options...
lordsepid Posted February 2, 2009 Share Posted February 2, 2009 i don't know the error but i had almost same problems once and i decided to reinstall my windows.after that the problem solved. also upgrading to new version would definitely help you. Link to comment Share on other sites More sharing options...
coucou Posted February 3, 2009 Author Share Posted February 3, 2009 i don't know the error but i had almost same problems once and i decided to reinstall my windows.after that the problem solved. also upgrading to new version would definitely help you. TNX for this radical solving problem In the meantime, that a clever person find a solution, i'm testing my WPI update on a Vmawre machine it seems worgin fine. Hope NOT waiting much.Regardscoucou Link to comment Share on other sites More sharing options...
mritter Posted February 4, 2009 Share Posted February 4, 2009 The only way to get that error about bit64 is if you overwrote your old WPI folder with the new one and globals.js didn't get updated for some reason. Or you have some old reg keys hanging around.1) Delete the entire WPI folder in registry: HKCU\Software\WPI2) Download WPI again and copy in your old options.js and config.js3) Run WPI and update your config file.4) Quit and run again to see if works properly. Link to comment Share on other sites More sharing options...
coucou Posted February 4, 2009 Author Share Posted February 4, 2009 TNX mritter,right now i'm out for a week.I'll test it laterRegardscoucou Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now