Error message appears when PJ64 is run before the ROM browser appears. It now appears everytime (but still continues to run successfully after clicking OK) The Error message is attached as a PNG but basically reads "The proceedure entry point1_CertUpdateStore could not be located in dynamic link library CRYPT32.DLL"
I am using PJ64 1.5 SP1 although it also appears with a clean install before SP1 is applied
My computer is built by myself running Win2K with SP4
Motherboard is DFI Lanparty NFII Ultra with NForceII Chipset
CPU is Athlon 2000+ XP
Video is Nvidia GeForce FX5600 256MB
Sound is Auidgy 2 Platinium
I don't think any of the other hardware is relavant but there is HDD space to spare.
It happens with defauly plugins loaded or my Custom plugin selection (which is the defualt sound and video with N=Rage's Direct-Input8 V2 1.82a)
Before I last rebooted it did not do this and my previous windows session was 37 days long with PJ64 executed sucessfully over many times throughout that session, so plenty of other software settings could have been changed in that session, plus with new Windows updates released since then.
Although this is my own computer I repair computers for a living for a small OEM and am in charge of the repairs, so I repair a few every day so don't be afraid to say things like regedit and file rename, copy, paste, notepad edit etc.
j64:
I am using PJ64 1.5 SP1 although it also appears with a clean install before SP1 is applied
My computer is built by myself running Win2K with SP4
Motherboard is DFI Lanparty NFII Ultra with NForceII Chipset
CPU is Athlon 2000+ XP
Video is Nvidia GeForce FX5600 256MB
Sound is Auidgy 2 Platinium
I don't think any of the other hardware is relavant but there is HDD space to spare.
It happens with defauly plugins loaded or my Custom plugin selection (which is the defualt sound and video with N=Rage's Direct-Input8 V2 1.82a)
Before I last rebooted it did not do this and my previous windows session was 37 days long with PJ64 executed sucessfully over many times throughout that session, so plenty of other software settings could have been changed in that session, plus with new Windows updates released since then.
Although this is my own computer I repair computers for a living for a small OEM and am in charge of the repairs, so I repair a few every day so don't be afraid to say things like regedit and file rename, copy, paste, notepad edit etc.