I saw the new version and downloaded it. I then tried to upload my configuration from my ProntoPro. On V. 4, it said that the file was too big to emulate. The home screens were in black and white.

To perhaps simplify things, I uninstalled V. 4, and went to the prior version of ProntoProEdit. It had in its files the "saved" file from what I attempted to upload to the V.4, but it would not open it with the Emulator. I got the "Can't Open Configuration File" on the ProntoPro.

I then tried opening other files I had saved in the ProntoProEdit. The same. So it seems that, to this point, my attempt to download the V.4 program has resulted in an inability to access the emulator.

Anyone help out here. This really and truly sucks.

Thanks,

Nick

In V4 you have to pick the file type (TS100 TSU2000, TSU6000....). Are you sure you picked the right one?

Yes. I initially picked the wrong one, but then corrected it. I left open the possibility that my initial miss set things awry, which is why I uninstalled V.4. But the corruption has reached ProntoProEdit.

I'm going to uninstall everything and try from scratch. Any other ideas, I'm game.

Thanks,

Nick

It asks you to pick the file type every time you open it, or a new file. It does not keep it in memory. I have flipped from the different file formats with no problem.

Thanks. It's "working" now, but I'm having what must be a Windows 2000 problem. When I run the emulator, the first time it appears, it says that it can't open the configuration.

Then, thereafter, if I open panel from Home or Devices, I can then "open" the emulator. And, even then, when I open the emulator, the first panel is blank, and I have to scroll down to the second panel, and scroll all the way through . . . where the first panel then appears.

I call this a Windows 2000 problem because it was a problem with Windows 2000 at work, for a while, but it did not show up at home until downloading v.4, although I've had Windows 2000 here for some months.

Go figure.

Thanks,

Nick

I vaguely remember someone else having this problem. If I'm thinking of the same one, it might be related to turning off support for 8.3 filenames in the registry.

Right -- the emulator ONLY works with 8.3 filenames. It doesn't recognize long names.

There is a registry setting that enables/disables the storing of equivalent 8.3 filenames for each long filename. If you have that disabled, the emulator doesn't work.

Can you tell me how to make the adjustment, so I can test? This is Windows 2000 Professional.

Thanks,

Nick

Did a search on "8.3" and found the thread

[Link: remotecentral.com]\.3%60