Does anyone else have any issues with the editor crashing? When loading some of the saved PCF files then opening up some of the panels, they don't display, showing only a blank box, and the menus and icons look corrupted. The simulator also seems to have some graphics glitches. This only happens intermittently, however.

It all seems to point to an outdated video driver, but I updated that to the most recent and I'm still having trouble. Has anyone else seen this?

(Do Philips people read this? Just in case for Tech Support folks: Windows 98SE, NVidia Geforce 256)

Sounds like your computer is running low on resources. How much memory to you have? Right click the My Computer icon on your desktop and select system. This will tell the amount of memory and your resources. If resources get belwo 80% you will have slow downs and crashes. Rebooting the computer will help for awhile.

Archer

Yes. Read my post "Farewell TSU3000". That was also a reason I returned it. Unfortunately my corrupted Simulator graphics showed up on the remote too.
David

I agree with Archer's statement about your resource level. I don't have a 3000 yet but I have been playing around with PENG. I found that when I opened ONE of the pcf's that I downloaded that my resources would get down to 15%. That's not enough to do anything useful.
I was wondering how much memory I need. I currently have 640MB out of a max of 768 and have been thinking about replacing my 128MB chip with a last 256. Do I need to?

Hey, memory is cheap. It is one of the best upgrades you can do for the amount of money spent. You will see the benefits on most of the programs you run.

Archer

ndor, what operating system are you using? If you are using Windows 95 or 98, adding more memory *won't* do anything to increase resources - it's a fixed area, regardless of how much memory you have.

I have had problems as well. I was hoping that the NG would be faster and more reliable but I do have some problems captureing some IR codes. My program has crashed as well but I am running XP home. I do have plenty of memory but I believe it is still flakey. Hopefully the IR capturing will be improved in later versions. To program one button you still have to click in 3 places just to enter the IR capture screen, then 3 more times to exit that button. If you use the IR Library, you have to select the make, model then find the button that is to be controled. This takes a lot of time and I believe it is faster to learn the codes than to use the library. I think that if there is a screen that displays the buttons of the page in a list in a colum on the left then the IR remote functions in a list on the right, by highlighting the button you wish to program then selecting the appropriate IR from a list on the right, you program at least 600% faster. This will eliminate the process of unnessary opening and closing of windows.

Well I checked it out and I am running low on resources. Regardless, I wouldn't think low resources would crap out a program like that. Especially lower than 80% as Archer said.

I know memory is cheap, but I'd rather not sink any more money into a three year old machine.

And I have to agree about the UI, it needs a lot of work.

I'm running win2k with only 256 ram. Have opened 3 or 4 pcfs simultaneously with the emulator, along with several other apps. No problems, crashes, or corruption. But that's why I switched to win2k years ago - it's robust, unlike win98. don't know about xp, but I haven't heard anyone rave about it either. - mike

I have exactly the same problem on my Win98SE system (when I use larger PCF files). I moved my work to a Win2K system and those problems are gone.

There is one down-side to using Win2K for PENG: The font sizes shown in PENG don't come close to what is shown in the simulator (or used on the 3000). For instance, 10 & 12 simulate as the same size but look very different in PENG. 14 looks like it's much bigger in PENG than it is on 3000. 8 looks much larger in PENG than it is on 3000.

These things are not true with Win98: The PENG fonts are very realistic there.
Barry