Hmm, I'm still getting the messed up working dir. Here's what I did:
1. Extract JPCSP Launcher to my Jpcsp emulator folder.
2. Run JPCSP Launcher and click ADV to open up the advanced settings page, and then click Custom Path.
3. Checked the Override box, set the Jar File to point to the correct jar file and also the Lib Path to the correct lib\windows-x86\ then click Save.
4. Click on Run to launch Jpcsp. The Jpcsp window shows so it runs successfully.
5. However, I notice that in my dist folder where my jar file is located, the emulator creates the ms0 folder, tmp folder, and Settings.properties file since it's not using the correct working folder. The Load UMD window doesn't show since it can't find my umdimages folder.
6. If I restart JPCSP Launcher, it will use the correct working folder until I change the Custom Path which causes the working folder to change to the jar folder again.
EDIT: I tried it on my notebook which uses Windows 7 64-bit and it's working just fine the first time without needing a restart of the launcher. The bug occurs on my desktop PC which is still using XP 64-bit. This is very strange. Also no problems at all with v1.3.0.8 on my desktop PC as long as I name the file jpcsp.jar.
1. Extract JPCSP Launcher to my Jpcsp emulator folder.
2. Run JPCSP Launcher and click ADV to open up the advanced settings page, and then click Custom Path.
3. Checked the Override box, set the Jar File to point to the correct jar file and also the Lib Path to the correct lib\windows-x86\ then click Save.
4. Click on Run to launch Jpcsp. The Jpcsp window shows so it runs successfully.
5. However, I notice that in my dist folder where my jar file is located, the emulator creates the ms0 folder, tmp folder, and Settings.properties file since it's not using the correct working folder. The Load UMD window doesn't show since it can't find my umdimages folder.
6. If I restart JPCSP Launcher, it will use the correct working folder until I change the Custom Path which causes the working folder to change to the jar folder again.
EDIT: I tried it on my notebook which uses Windows 7 64-bit and it's working just fine the first time without needing a restart of the launcher. The bug occurs on my desktop PC which is still using XP 64-bit. This is very strange. Also no problems at all with v1.3.0.8 on my desktop PC as long as I name the file jpcsp.jar.