 |
 |
|
|
Philips Pronto Classic Forum - View Post
|
|
 |
|
|
|
 |
|
The following page was printed from RemoteCentral.com:
| Topic: | 2.0 ini error This thread has 6 replies. Displaying all posts. |
|
| Post 1 made on Wednesday January 17, 2001 at 22:52 |
Any ideas why I woulod receive a "none or invalid ini file error after installing 2.0 from CD? I did make developer mod with still no success. THANK YOU RC
|
|
| OP | Post 2 made on Wednesday January 17, 2001 at 23:05 |
Peter Dewildt Historic Forum Post |
|
|
This is because you already had a pronto.ini that had a later date than the one in the install kit (presumably you edited it). There is a new line in the V2 file.
Just delete it then install again.
|
|
| OP | Post 3 made on Wednesday January 17, 2001 at 23:08 |
Daniel Tonks Historic Forum Post |
|
|
I've let Philips know that this will HAVE to work properly on the downloaded version.
|
|
| OP | Post 4 made on Thursday January 18, 2001 at 01:11 |
jack schultz Historic Forum Post |
|
|
The problem is NOT related to the date stamp on the pronto.ini file but rather that the 2.0 software merely checks for and does NOT overwrite an existing file on some machine and O/S variants. I have seen both good and not good results when upgrading to various of our in house machines, with Win98SE seeming to have more problems than Win95 machines. So, the best approach when installing 2.0 over an existing previous version is to uninstall the previous version, delete the pronto.ini file, the pronto.css file, and especially the prontoupdate.exe file, then install 2.0 and all should be fine. The deletion of the update file is just to make sure that the user does not accidentally run the (older) version update utility as the 2.0 does NOT load (offer) a new update utility currently because of the IR code library and licensing issues related to same.
|
|
| OP | Post 5 made on Thursday January 18, 2001 at 17:24 |
Peter Dewildt Historic Forum Post |
|
|
Jack, when I first installed V2 (at work) my pronto.ini was replaced, and so I had no problems. A few weeks later I installed it at home, and my pronto.ini was not replaced and I noticed the date was later than the one in the kit. Both are Windows 2000.
Your're right about the ProntoUpdate.exe. I copied my 1.05 copy into my Pronto V2 install directory, and the Update feature was no longer greyed out. However, if you run Update it at least clearly tells you what version it has when it asks you whether to proceed.
|
|
| OP | Post 6 made on Friday January 19, 2001 at 00:25 |
|
| OP | Post 7 made on Sunday January 21, 2001 at 18:53 |
Daniel Tonks Historic Forum Post |
|
|
ProntoEdit used to check what remote it was updating BEFORE sending the update -- then it changed to always allowing the update, but the remote itself rejecting the upgrade after the fact. Sounds like they should go back to the former method.
|
|
 |
Before you can reply to a message... |
You must first register for a Remote Central user account - it's fast and free! Or, if you already have an account, please login now. |
Please read the following: Unsolicited commercial advertisements are absolutely not permitted on this forum. Other private buy & sell messages should be posted to our Marketplace. For information on how to advertise your service or product click here. Remote Central reserves the right to remove or modify any post that is deemed inappropriate.
|
|
|
|
|
