An "a's" computer language

[vinnietoo]

Found this on the web........... I used to run Carryout 1.0 - in part as a shell and in part as my main application. Carryout is a slimmed down version of Drinkingbuddies 1.0 which allows TSR. It doesn't allow for networking, nor do you get all the other benefits of ready access to a server and server utilities such as ChatUp and EyeUp, but it is cheaper, particularly if you compile the program yourself.
At that time I was experiencing a range of system errors, which I attributed to various things including running Spouse 1.0. For instance while Carryout as TSR seemed o.k. particularly in the evening after running it for a few hours I would find that the system would first get wobbly, resolution would deteriorate progressively from SVGA down to CGA, and then the whole thing would crash.

As things went on the conflicts with Spouse 1.0 meant that generally I would have to completely unload Spouse 1.0 before running Carryout. Even starting to load Carryout could affect Wife 1.0 - as you know, Wife 1.0 the capacity to see for itself what's in the drive. Generally, however, I discovered that by partitioning off the boot sector it was possible to load Carryout there and then be able to open it up, as soon as Wife 1.0 was temporarily uninstalled.

Embarrassing faults however started to appear. Once, while simultaneously trying to handle a connection with the support service for Spouse 1.0 (If you want to call yourself you'll find it in the bestfriend directory) the contents of the No 1. cache became overwritten onto shreddys.exe. Although I was able to struggle on for a bit, I obviously had to reinstall shreddys.exe. I also regularly experienced sheets.cln being overwritten when the whole machine was supposed to be turned off, if I hadn't remembered to clear the No 2 cache before closing down for the night.

While I had a range of diagnoses at the time for the problems I was experiencing my sister explained that the real cause was running any kind of shell/organizer program containing C2H5OH source code. The only solution is to not use any such program.

As an alternative I have found that by switching to 12Steps 1.0 I have a much better program. Written in T++ it really requires you have higher power to run it properly, but the whole package includes:
* Extensive Help files (Bigbook.hlp, Share.hlp) and online help
* The very useful executable share.exe . This works wonders, bundling defragmentation, system check-up, error diagnosis etc, including a quaint application sponsor.exe (which keeps sending me the error message "RTFM").
* Dial-up access
* Networking.


There is an error diagnosis facility with the network service - Inventory - but it is invariably a bit suspect.
Good news - While it isn't the primary purpose use of the programme ChatUp.exe is also available if you don't have Spouse 1.0 and can be enabled when you know what you are doing, but it certainly isn't compatible if you have already installed Spouse 1.0. But see my note of caution below.

The upgrade 1.1, which I am using now is brilliant, it also includes email. While I understand 12Step version 6.0 is available (it includes a special intensive study tutor for the instruction manual) I haven't noted any discernable increase in performance from people who are running it, but then that could be that with the higher power I've got that I've just got a bit lazy about performance. Probably a combination of understanding the manual and having the higher power is ideal.

A word of warning. Counterfeit versions of the 12step program are available, variously marketed as TwoStep and Step13. Both are produced by John Barleycorn software. TwoStep is a slimmed down version, but as it includes no error detection ultimately leads to system failure. The attraction of 13step is that bundled with it is most advanced version of ChatUp.exe, chat_n_s.exe. But this will also cause a crash, virus alerts, and frequently results in some network disablement. I must say I am glad I made the change. I've heard that prolonged use of CarryOut 1.0 can lead to damage in the boot sector, to partitions, can result in telcos disconnecting supply, viruses, and permanent system failure.
But I know if I was not able to access the higher power I have now then I would probably be tempted to run it again......
A problem. Sometimes I wish I wasn't running Spouse 1.0. I even dreamed about this last night. Although I know the theory - that unless you've lost Spouse 1.0 for some reason, there is no particular merit in using ChatUp to obtain the upgrade Spouse 2.0 - I suppose I'm attracted by a more recent version. Any ideas how to get over this?


Hugs to all,
Vinnie