plFEP

[Phil Aypee]

Hi,

I have loaded all my stuff on my "new" netBook and it all works fine - except....plFEP.

I forgot to put the registration in before it "expired" and now it locks the machine if enabled. Uninstalling completely and reinstalling makes no difference. I could start again from scratch (more or less) but it must be a file hidden somewhere so I wondered if anyone knew what it was?

[Jonas]

As I remember, there's some sort of registry on the Psion. It can only be deleted on hardware reset.
There was some suspicious program to display that registry...
But my memories faint more and more

[KvdS]

Hi,

I have loaded all my stuff on my "new" netBook and it all works fine - except....plFEP.

I forgot to put the registration in before it "expired" and now it locks the machine if enabled. Uninstalling completely and reinstalling makes no difference. I could start again from scratch (more or less) but it must be a file hidden somewhere so I wondered if anyone knew what it was?



AFAIK it's in C\System\Data\Commsdb.dat
Try to delete the that file or the whole folder and replace an older folder from the backup.

Success.

[Phil Aypee]

Hi,

Thanks Kees - but no cigar. plFEP still wants registering but locks the machine so it can't be registered.

I'll use FastBackup and try formatting C: next - failing that I'll have to reload the OS.

All good fun, ain't it! :rolleyes:

[Jackson Hollis]

Hi Phil,

I am not sure what happened to your netbook (or concrete to plfep). A lot of years I was using plfep without registration and curiously it was working perfectly..

Ok, some ideas now :

- please check also other disks. Plfep files could be also on disk D or elsewhere (duplication install or copy - sometimes this happens). OS after reset checks firstly last disk and lastly C.. So, it is possible that you have some plfep files on the disk D and you forget it .. (D:/System/Controls and D:/System/Fep ..)

- if this will not hep do this - try to check where problem is by this way (generaly method for many problems)

Rename your system folder from C:/system to C:/Xsystem
then make RESET
then test what problematic application doing

if problem not occurs, you know where is .. in the folder System .. :)

Then rename application folder ... from C:/System/Apps to C:/System/xApps
then make RESET
then test what it is doing ...

if problem not occurs .. bla bla bla bla .. I think you know the way how to find where is some chaos code or whatever ..

Yes, it is manual work, it will take time, but I think this is best way how to find some problematic DLL, RDL, MDL or APP ..

try it and let us know ..

jaxon hollis

[gelleal]

Try to enter some earlier date (before expiration), then register the program and change back to the current date.
Hope this helps.
Otherwise drop me a message to: gel_at_donpac_dot_ru.

Leonid (Leo)