Printable View
MS unable to help, so desperate. My VB5 SP3 app works OK. The exe works OK. Uses threed32.ocx and dwspy32.dll but otherwise easy stuff. Everything registered OK. All been working for two years OK.
Re-installed VB5 SP3. Setup wiz makes a setup.exe that works on VB pc but, if I copy files to a CD and install on a new pc, install fails at first listed line: 'Invalid line in seup inf list ...
Voice Recognition, Microphones, and Text-To-Speech.
Products, Support, and International Sales.
Hi This is a big problem with Setup wiz. I also had that problem. I tried my best to get help on this but all in vain. So i decided to make my own Application which can do same work as setup wiz. I make it in VC and it worked very fine. I make a cab file of all the application files and used APIs to register my controls and dlls on other PC and believe me it worked very fine. Please try to make your own setup App.
I had the same error message yesterday and the reason was...
...different language settings!
on my development computer I had changed the date format to "MM.DD.YYYY".
When creating the setup.inf file setup wizard screwed up the file dates and wrote dates in THAT format to the setup.inf.
On the computer where I ran setup the language settings where "normal". Obivously setup had problems with the date format the setup wizard has created.
That's unbelievable: the same old brainless crap in setup wizard since the first release!
Excellent. I tried altering the Regional/Date setting and it got me past the problem. But which of the possible setting styles am I MEANT to choose - d dd M MM yy yyyy etc. And what about : or / as a date separator. Presumably my app will run on someone else's pc with different settings. I've been stuck on this for eight days so your suggestion was great. Thanks for your time and interest.
Voice Recognition, Microphones, and Text-To-Speech.
Products, Support, and International Sales.
I haven't tested this yet, but I assume that choosing "English (USA)" as language settings in Control panel could be the "best" choice for the computer where you create the setup program.
IMHO setup wizard should create a setup.lst with a "neutral" date format, one that setup can interpret.