In my case, it's usually working, but it runs out of paper in the middle of it (and there's never a replacement sheet anywhere nearby. It's usually locked up in some place whose guardian in not there at the moment) or the paper gets stuck somewhere in the machine and you can't get it out without getting your hands very dirty...
There's an urgency circuit built into most copiers. The paper will jam, the toner pretends to run out, and the options you need will be magically unavailable in proportion to the urgency of the print job. If you have a month to get the report collated and distributed, the circuit is disabled; but if you have a presentation to give in five minutes, the circuit reaches maximum and all functions halt.
The ingredient issue is more likely related to your Husband software. Since you are running two instances in the same virtual environment, you need to make sure the versions are compatible. Previous users have noted problems with upgrades to Version 1.0 from other software, and these are addressed in the beta version of Husband version 2.0. I understand the shopping and storage sub-systems have been greatly enhanced to cope with parallel processing environments.
The ingredient issue is more likely related to your Husband software. Since you are running two instances in the same virtual environment, you need to make sure the versions are compatible.
I'm fairly sure that the two copies of Husband are compatible - if not, the first copy would have crashed long since. There do however seem to be some communication glitches - witness (1) the Chicken Stock incident, and (2) the "we don't know what it is[*] but it seems to be from a four-legged mammal so we'd best deal with it while the second copy of Husband is running on a remote terminal" incident.
[*] - it's the incorrect / missing labelling data in the FAT for the lump of frozen mammal that is the communication glitch here, not the subsequent running of the Potroast 2.5 software.
Why is the photocopier always dead when I need it?
that's what you get for dropping your pants and photocopying your arse a couple of months ago. If you're gonna moon the XeroxTM, it's liable to get passive-aggressive on you.
me, I think your arse is cute, but the evidence is the XeroxTM doesn't share my opinion.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
bjarvis
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2008-02-05 02:50 pm (UTC)no subject
Date: 2008-02-05 03:13 pm (UTC)So, consider yourself lucky! :-)
no subject
Date: 2008-02-05 06:27 pm (UTC)no subject
Date: 2008-02-05 06:54 pm (UTC)no subject
Date: 2008-02-05 07:22 pm (UTC)More information on upgrades see: http://www.forwardedfunnies.com/husband_version_10_010843.html
no subject
Date: 2008-02-05 10:32 pm (UTC)I'm fairly sure that the two copies of Husband are compatible - if not, the first copy would have crashed long since. There do however seem to be some communication glitches - witness (1) the Chicken Stock incident, and (2) the "we don't know what it is[*] but it seems to be from a four-legged mammal so we'd best deal with it while the second copy of Husband is running on a remote terminal" incident.
[*] - it's the incorrect / missing labelling data in the FAT for the lump of frozen mammal that is the communication glitch here, not the subsequent running of the Potroast 2.5 software.
no subject
Date: 2008-02-05 10:36 pm (UTC)that's what you get for dropping your pants and photocopying your arse a couple of months ago. If you're gonna moon the XeroxTM, it's liable to get passive-aggressive on you.
me, I think your arse is cute, but the evidence is the XeroxTM doesn't share my opinion.