For the benefit of any users about to enjoy the displeasures of Windows XP, I am happy to report that I now have a large, script-intensive application running under WinXP.
There were 3 very difficult areas encountered.
1. The load time of Alpha Five was around 5 minutes! I have a small ethernet peer network at my home and my new XP system was sharing printers from the network. Turns out this caused an excessive wait at load time and I'll never understand why.
My solution was to create a printer (Epson LQ-570, specifically) and define it as a local printer, even though it didn't exist. I had made it my default but I'm not totally sure that was necessary. Alpha Five now loads in a couple seconds.
2. I run many post and append functions that are defined in the Control Panel for the specific database or set. I used an application menu and the card_run function. Certain appends and updates and all posts took an excessive amount of time. One post of only 10,000 records took 7.5 minutes on a 1.8GHz Dell with XP, and only 1-2 minutes on my 400MHz Dell with WIN98.
The solution was to stop using card-run, and instead, coded the entire append and post operations in the application card script. The difficult post dropped from 7+ minutes to 17 seconds. My guess is that record locking came into play and XP handled this MUCH less graciously than WIN98, although the time did improve on WIN98 as well.
3. Certain reports (but not all) had colors specified for header and footer fields and labels. Some of this information did not print, or partially printed. There was no consistency that I could see.
The solution was to re-code those colors to "wintext" which WINXP handles fine. I was printing to a monochrome printer anyway, but I consider this a very small loss. Probably this had something to do with the XP print drivers which are not the best I have worked with.
So, after a shaky start, my 7 year old application continues to live, which fact pleases me immensely. I hope this experience helps someone out there. It can be very lonely sometimes when dealing with these issues.
Regards ... Sam
There were 3 very difficult areas encountered.
1. The load time of Alpha Five was around 5 minutes! I have a small ethernet peer network at my home and my new XP system was sharing printers from the network. Turns out this caused an excessive wait at load time and I'll never understand why.
My solution was to create a printer (Epson LQ-570, specifically) and define it as a local printer, even though it didn't exist. I had made it my default but I'm not totally sure that was necessary. Alpha Five now loads in a couple seconds.
2. I run many post and append functions that are defined in the Control Panel for the specific database or set. I used an application menu and the card_run function. Certain appends and updates and all posts took an excessive amount of time. One post of only 10,000 records took 7.5 minutes on a 1.8GHz Dell with XP, and only 1-2 minutes on my 400MHz Dell with WIN98.
The solution was to stop using card-run, and instead, coded the entire append and post operations in the application card script. The difficult post dropped from 7+ minutes to 17 seconds. My guess is that record locking came into play and XP handled this MUCH less graciously than WIN98, although the time did improve on WIN98 as well.
3. Certain reports (but not all) had colors specified for header and footer fields and labels. Some of this information did not print, or partially printed. There was no consistency that I could see.
The solution was to re-code those colors to "wintext" which WINXP handles fine. I was printing to a monochrome printer anyway, but I consider this a very small loss. Probably this had something to do with the XP print drivers which are not the best I have worked with.
So, after a shaky start, my 7 year old application continues to live, which fact pleases me immensely. I hope this experience helps someone out there. It can be very lonely sometimes when dealing with these issues.
Regards ... Sam
Comment