You have an extensions conflict. Wait until Girlfriend 1.0 is finished with Monthly Software Update (MSU) before asking system for ANY other resources. Quit all other applications if Girlfiend 1.0 prompts you to do so during MSU. You may have to restart after MSU, although some users have reported working on Girlfriend 1.0 while MSU is running. Your mileage may vary, as Monthly Software Updates change based on a variety of circumstances.
Girlfriend x.x schedules MSU using proprietary tools, and this behavior cannot be changed without significant re-compiling. There are no GUI tools to admin Girlfriend 1.0 as of yet. There is also no man page or online docs, as Girlfriend 1.0 keeps changing behavior based on user input.
BTW, good luck running Girlfriend 1.0 as a multi-user binary -- I haven't been able to get it to work without serious system instabilities and frequent crashes, even with latest software updates from Apple! I tried twice and had to re-install Girlfriend 1.0, with weeks of downtime.
In case you're interested, Girlfriend 0.95 and earlier ran only on System 7.1 (or earlier), ran only as a foreground app, and ran without the user having any ability to the ability to save or modify without upgrading to a costly full-release of software. Girlfriend 0.96.1 and later have all been nagware, except for Girlfriend 0.98.2 which was shareware and the horrible Girlfriend 0.99.5 which was a bizarre experiment in freeware (extremely unstable binaries!!).
Girlfriend 0.98.2 had a Network Users interface, but it had some serious security issues. My system was wracked with two viruses -- because Girlfriend 0.98.2 was shareware and Parents 2.2 would not work with Girlfriend 0.98.2 at all. Girlfriend 0.97.1, 0.97.3, and 0.97.7 were all beta releases, but all were feature poor. I ran Girlfriend 0.96.3 for awhile. I liked most of the features of 0.96.3, but the interface was ugly and I had a problem with preferences changing before I upgraded to 0.97.x.
To tell you the truth, you may want to bite the bullet and upgrade to Wife 1.0 instead of Girlfriend 2.0, because user training issues will significantly affect your TCO based on previous experiences with Girlfriend 1.0. You cannot run Girlfriend 1.0 and Girlfriend 2.0 on the same machine without serious and tedious re-compiling from source (and various library conflicts) -- and, BEWARE, there may be very serious security issues if your systems are networked and both Girlfriend 1.0 and Girlfriend 2.0 are on the same network interface or, worse yet, the same subnet.
Something else to think about, will you ever neet any data from Girlfriend 1.0? If so, know that Girlfriend 2.0 may overwrite all of Girlfriend 1.0's data without user input. Backups are extemely difficult to maintain, as reinstalling Girlfriend 1.0 data with Girlfriend 2.0 binary will cause 2.0 to become unstable, and may lead to complete loss of functionality. Girlfriend 2.0 will try to overwrite all system preferences -- so check Trash often.
One last thing, make sure you have plenty of system resources available with you intend to run Lad's Night Out (any version) in the foreground. Girlfriend 1.0 writes syslog entries in several places throughout the system, and log files may become very large in a very short time. Unless you want to spend all of your time cleaning up logs, I'd schedule Lad's Night Out with Girlfriend 1.0, or run it as a background app.
Slashdot Mirror
You have an extensions conflict. Wait until Girlfriend 1.0 is finished with Monthly Software Update (MSU) before asking system for ANY other resources. Quit all other applications if Girlfiend 1.0 prompts you to do so during MSU. You may have to restart after MSU, although some users have reported working on Girlfriend 1.0 while MSU is running. Your mileage may vary, as Monthly Software Updates change based on a variety of circumstances.
Girlfriend x.x schedules MSU using proprietary tools, and this behavior cannot be changed without significant re-compiling. There are no GUI tools to admin Girlfriend 1.0 as of yet. There is also no man page or online docs, as Girlfriend 1.0 keeps changing behavior based on user input.
BTW, good luck running Girlfriend 1.0 as a multi-user binary -- I haven't been able to get it to work without serious system instabilities and frequent crashes, even with latest software updates from Apple! I tried twice and had to re-install Girlfriend 1.0, with weeks of downtime.
In case you're interested, Girlfriend 0.95 and earlier ran only on System 7.1 (or earlier), ran only as a foreground app, and ran without the user having any ability to the ability to save or modify without upgrading to a costly full-release of software. Girlfriend 0.96.1 and later have all been nagware, except for Girlfriend 0.98.2 which was shareware and the horrible Girlfriend 0.99.5 which was a bizarre experiment in freeware (extremely unstable binaries!!).
Girlfriend 0.98.2 had a Network Users interface, but it had some serious security issues. My system was wracked with two viruses -- because Girlfriend 0.98.2 was shareware and Parents 2.2 would not work with Girlfriend 0.98.2 at all. Girlfriend 0.97.1, 0.97.3, and 0.97.7 were all beta releases, but all were feature poor. I ran Girlfriend 0.96.3 for awhile. I liked most of the features of 0.96.3, but the interface was ugly and I had a problem with preferences changing before I upgraded to 0.97.x.
To tell you the truth, you may want to bite the bullet and upgrade to Wife 1.0 instead of Girlfriend 2.0, because user training issues will significantly affect your TCO based on previous experiences with Girlfriend 1.0. You cannot run Girlfriend 1.0 and Girlfriend 2.0 on the same machine without serious and tedious re-compiling from source (and various library conflicts) -- and, BEWARE, there may be very serious security issues if your systems are networked and both Girlfriend 1.0 and Girlfriend 2.0 are on the same network interface or, worse yet, the same subnet.
Something else to think about, will you ever neet any data from Girlfriend 1.0? If so, know that Girlfriend 2.0 may overwrite all of Girlfriend 1.0's data without user input. Backups are extemely difficult to maintain, as reinstalling Girlfriend 1.0 data with Girlfriend 2.0 binary will cause 2.0 to become unstable, and may lead to complete loss of functionality. Girlfriend 2.0 will try to overwrite all system preferences -- so check Trash often.
One last thing, make sure you have plenty of system resources available with you intend to run Lad's Night Out (any version) in the foreground. Girlfriend 1.0 writes syslog entries in several places throughout the system, and log files may become very large in a very short time. Unless you want to spend all of your time cleaning up logs, I'd schedule Lad's Night Out with Girlfriend 1.0, or run it as a background app.
Good luck!
You have an