I'm running GameJackel 2.9.18.610, XP media center 2003 (fully patched 5 months ago or so), Daemon tools is installed but not active. The system is a dual dual-core AMD Opteron/w 4G ram, 4 500G sata drives in a hardware RAID 5 configuration, over 830G free space. I'm running a recent version of Sophos antivirus, and VMWare Workstation is installed.
With the previous version of GameJackel, I was able to create profiles. Now, whenever I try to do so, after the game closes and I disable the profile, I receive an error message of "Insufficient room to create profile" or something similar. Clicking cancel just makes that dialog box reappear. Moving the dialog box and canceling the creation of the profile causes GJ to crash with, I think, the message "Cannot create modal window" or some such (the machine doesn't have an Internet connection, so I'm doing this from memory.)
I might suspect VMWare Workstation (since it tends to hijack autoplay), but in the past I've been able to create profiles, with VMWare installed. Punkbuster was recently installed, but I still get the error even after stopping the service. If I had to guess, I'd suspect that the drive size is at issue. 1.5T of storage isn't too common; 830G+ free space isn't either. Maybe an overflow issue computing free space is at fault.
With the previous version of GameJackel, I was able to create profiles. Now, whenever I try to do so, after the game closes and I disable the profile, I receive an error message of "Insufficient room to create profile" or something similar. Clicking cancel just makes that dialog box reappear. Moving the dialog box and canceling the creation of the profile causes GJ to crash with, I think, the message "Cannot create modal window" or some such (the machine doesn't have an Internet connection, so I'm doing this from memory.)
I might suspect VMWare Workstation (since it tends to hijack autoplay), but in the past I've been able to create profiles, with VMWare installed. Punkbuster was recently installed, but I still get the error even after stopping the service. If I had to guess, I'd suspect that the drive size is at issue. 1.5T of storage isn't too common; 830G+ free space isn't either. Maybe an overflow issue computing free space is at fault.
