Problems installing Girlfriend 1.0...

Theres a workaround for version conflict. Try to install for example spanish language version of 1.0 and russian (if ur virus protection is up to date)language version 2.0. That should guarantee collision avoidance over communication channel and thus remove the I/O port bug. They should work independently rather fine. However u shouldnt try running both applications simultaneously that might introduce some unwanted noise issues.

Also try to install language version which is gibberish to u self, that somehow seems to sandbox offending process and thus prevent it from interfering other processes and protecting their running privilidges.

If nothing else work u still have option to run both platforms on different boxes, but thats economically unfeasible for most of us...

Anyway im not best giving adivices... had to dump 3.0 after experiencing a DoS (Denial of service).

hum... this is why you brought back this 1 yr old thread?

Although I admit the DoS part is pretty funny....

Quote:

---

Originally Posted by RoyN

hum... this is why you brought back this 1 yr old thread?

---

Yes i spent whole year thinking and rewriting that...

going back to invent optimal algorithm for jerk 1.0, have to work on my Big-Oh notation, until i can alphatest new brazilian language version :yum:

Old thred - but still funny :)

Terran

Quote:

---

Originally Posted by RoyN

Although I admit the DoS part is pretty funny....

---

Not if you are on the receiving end. (or not receiving end if you know what I mean)

you are completelly right, sir.

Quote:

---

Originally Posted by P3rv3rt B3ar

Anyway im not best giving adivices... had to dump 3.0 after experiencing a DoS (Denial of service).

---

Sounds to me like version 3.0 turned into a virus. A virus continues to grow and get worse until every resource is consumed. The only way it can survive is to spread to another area. The DoS will get worse while more resources are consumed to try to tackle the DoS problem. You did the only thing you could do, rid yourself of it and let it spread to another host. Better not be to me in the future, and I don't wish that on anyone here.

Quote:

---

Originally Posted by StrataG

Sounds to me like version 3.0 turned into a virus. A virus continues to grow and get worse until every resource is consumed. The only way it can survive is to spread to another area. The DoS will get worse while more resources are consumed to try to tackle the DoS problem. You did the only thing you could do, rid yourself of it and let it spread to another host. Better not be to me in the future, and I don't wish that on anyone here.

---

Allthough this malware is contained on distant population behind several hops and sturdy firewalls we better take emergency measures against pandemy caused by coordinated deployment of distributed DoS-agents. One way to increase availability is to build server farm and thus ensure redundancy through stockpiling. Also as a backup system we have to implement a grid of multiple client serving time-sharing systems with a plentiful application selection (oh and preferably big buffers).

Enforcer: yes, wasnt very funny from my point of view... Had to do several reboots and even low-level format to get back up and running.

Quote:

---

Originally Posted by P3rv3rt B3ar

Allthough this malware is contained on distant population behind several hops and sturdy firewalls we better take emergency measures against pandemy caused by coordinated deployment of distributed DoS-agents. One way to increase availability is to build server farm and thus ensure redundancy through stockpiling. Also as a backup system we have to implement a grid of multiple client serving time-sharing systems with a plentiful application selection (oh and preferably big buffers).

---

Don't forget to build a backdoor for scouse.