From: Ken Smith on
In article <er6s31$8ss_006(a)s994.apx1.sbo.ma.dialup.rcn.com>,
<jmfbahciv(a)aol.com> wrote:
[.....]
>When Linux can be installed and used with very little relearning
>by any computer owner, then it will cease to be a toy and become
>a general purpose tool. It hasn't reached that maturity..yet.
>It is getting there rapidly.


That is the case today. The average computer owner sends email, recieves
spam, surfs the web and plays Minesweeper. You get all that in many
installs today. All the user has to do is answer yes to installing the
software.

--
--
kensmith(a)rahul.net forging knowledge

From: Ken Smith on
In article <er6sa4$8ss_008(a)s994.apx1.sbo.ma.dialup.rcn.com>,
<jmfbahciv(a)aol.com> wrote:
>In article <t3jct2h2m7upjn9dho5vsppe4hb02ukvib(a)4ax.com>,
> MassiveProng <MassiveProng(a)thebarattheendoftheuniverse.org> wrote:
>>On Fri, 16 Feb 07 14:07:30 GMT, jmfbahciv(a)aol.com Gave us:
>>
>>>
>>>There is a huge difference between tasking and being able to
>>>interrupt any task at any time and resuming it seamlessly
>>>later and not being able to start another task until the
>>>previous one is completely finished including EOFing the
>>>files.
>>
>>
>> Batch process mentality bullshit.
>
>Quite the contrary. Your style of thinking is single-use
>concentration of gear. That has been clear since you tried
>to correct your elders.

MissingProng is a troll.

The funny thing is that the computer business has swung back and forth on
single vs multiple users. Now we seem to be at the single user end of the
swing. There is a trend back with people suggesting that everyone in the
building's files be maintained on a single server. Unfortunately, with a
Windows system done this way, there is no sure way to back up your files.
I figure at some point someone will bring out 3rd party software that
correctly backs everything for each user correctly. If that happens the
trend will continue back towards multiple users on a computer. The desk
top PC will become more like a smart terminal than a computer.

--
--
kensmith(a)rahul.net forging knowledge

From: Ken Smith on
In article <er6sft$8ss_009(a)s994.apx1.sbo.ma.dialup.rcn.com>,
<jmfbahciv(a)aol.com> wrote:
>In article <er4gcr$1ln$6(a)blue.rahul.net>,
> kensmith(a)green.rahul.net (Ken Smith) wrote:
>>In article <er45hl$pkf$1(a)jasen.is-a-geek.org>,
>>jasen <jasen(a)free.net.nz> wrote:
>>>On 2007-02-15, Ken Smith <kensmith(a)green.rahul.net> wrote:
>>>
>>>> The DOS mind set was to only do one thing at a time. Some bits of later
>>>> versions looked like multitasking was intended but abandoned. Even very
>>>> later versions save registers into code space instead of onto the stack.
>>>
>>>I read that there was a multitasking dos released by Microsoft in
>>>Europe. and then there's Deskview and I think Digital Research had
>>>a go at multitasking dos too.
>>>
>>>I played with something called multidos (I think it) was shareware or
>>>freeware and faked multitasking somehow.
>>
>>If you call two tasks "multi",
>
>I don't :-).

I could do 3 too.

It just takes a little more coding.

>
>> I wrote one that worked quite nicely. It
>>allowed the user interface task to run while disk I/O and printing etc
>>also ran. It was very special purposed so it wouldn't be something to
>>market.
>>
>>It really isn't that hard to create a multitasking system if only one task
>>is allowed to touch a given bit of hardware. Mostly you just have to
>>change the stack pointer and return from the timer interrupt into the
>>other task's context.
>
>You have a very big IF in that sentence. ;-)

Yes, but the two tasker served its purpose quite nicely. I created only
the tool I needed for the purpose not a general OS.

--
--
kensmith(a)rahul.net forging knowledge

From: Ken Smith on
In article <er6rf6$8ss_002(a)s994.apx1.sbo.ma.dialup.rcn.com>,
<jmfbahciv(a)aol.com> wrote:
>In article <d1ict2h4c5s3m3e5unsu4aagl2fpj0s49n(a)4ax.com>,
> MassiveProng <MassiveProng(a)thebarattheendoftheuniverse.org> wrote:
>>On Fri, 16 Feb 07 12:25:03 GMT, jmfbahciv(a)aol.com Gave us:
>>
>>>> Right now I also have LTSpice running on another
>>>>desktop. I'm typing this while if figures.
>>>
>>>My point is that you should not have to have another computer _system_
>>>to do any other task.
>>
>>
>> He said on another desktop. If you had any modern brains, you would
>>know that that IS the SAME computer, that has multiple "desktops". A
>>feature of Linux GUIs.
>
>IF that is true, the renaming of this term is going to cause a lot
>of problems.

It may have been better if a new term was invented. All the existing
terms had meanings:

"another screen" is bad because many Linux systems have more than one
screen

"another virtual screen" is bad because many Linux systems have a non
graphics virtual screen along with the graphics one. You can configure
for only one "desk top" and still have "another virtual screen". Also
the "virtual screen" may be larger than the physical hardware screen.

"another window" won't do because the term window is used for a part of
what is on the screen.

--
--
kensmith(a)rahul.net forging knowledge

From: Tony Lance on
Big Bertha Thing moisture
Cosmic Ray Series
Possible Real World System Constructs
http://web.onetel.com/~tonylance/moisture.html
Access page to 73K ZIP file
Astrophysics net ring access site
Newsgroup Reviews including misc.health.aids

Working Prototype of second phase Pastures software,
with 20 polyhedrons model and 200 buckminster fullerine molecules model,
complete with programs, source code in listing format and using Pastures
documentation.

Moisture Software Package.
(Based on Particle Structure Results Program, in Fortran 77.)
Sub-atomic Mesons, Baryons and Leptons Classification System.
(C) Copyright Tony Lance 1997
Distribute complete and free of charge to comply.


Big Bertha Thing virus

18th October 1999
Hi Chris,
Thanks for the Keyboard.drv, but Windows is still down.
The new messages are;
1. Clock General Protection Fault in gdi.exe (system)
2. Progman Ditto krnl386.exe (system)

Clock.exe see windows. Progman.exe see windows.
The two options seem to be, to try another four files
for windows 3.11 or save up and update PC. (130 pounds)

They have a nice 486DX66 16MB 270MB hard-drive 14" SVGA
and win 95, at the same place I bought the 386PC. It
is four times faster too. My biggest program takes 7 hours
on standard IBM PC, 90 minutes on 386 and 20 minutes on
486DX, which has a built in maths co-processor.

My DOS browser can read newsgroups, send/receive e-mail, browse
web, but not receive attachments, look up my own site or
update it.

Keyboard.drv worked, but closed down every app in windows,
so there was no way out. Clever that. The scrub round was
in the book, for bypassing emm386. Wait till boot up gets
to MSDOS loading and press F8. Step through Config.sys
line-by-line with y answer. It then goes through autoexec.bat
to last line of win. N answer drops you out to DOS prompt.

Strange to say I can still work on my science maths project
using Fortran 77 in DOS. Apps down with windows are Free Agent,
WS-ftple, Winzip, F-Prot, Anyware Virus, Chekmate Virus, FirstClass
client.

It looks like I picked up a macro virus off a wordperfect attachment
from e-mail of a guy in newsgroup. Three virus apps missed it.
It is visible in notepad view of file after saving with write.exe.
Isolate 386 and do not update site.

You might check that my site is still up, by the back door and let me
know the count. <www.bertha.ndirect.co.uk/series.htm>

It could not have happened to a nicer chap.
Thank you,
Tony Lance


Big Bertha Thing designer

Once there was Big Blue, Baby Bell and Pax IBM.
Now ther is Big Bertha, Baby Bill and Pax Microsoft.

1980 The Greater London Council, Central Computer Service installation
standards for IBM mainframe had standard date subroutines as mandatory.

1980 No standards for Prime minicomputer, so date subroutine for program
was written to be 2075 OK, by me.

All IBM customers and suppliers applied IBM standards. Enforcement of these
standards means that the following instances can only be designer
software obsolescence.(Smoking Gun features.)
1. First PC operating system DOS was written 1980 (IBM/Microsoft) No 2000
2. Next PC operating system MS-DOS (Microsoft) No 2000
3. Windows 95 enabled macro virus (Microsoft) admitted
4. Windows 95 macro virus written by Microsoft.(admitted)
5. Windows 95 macro virus released by Microsoft.(admitted)
6. Windows 98 enabled text virus (Microsoft) admitted
7. Windows 98 no product recall, fix is on Microsoft website only.
8. Windows 98 to release virus just say it exists and fix is on website.
9. 1997 MS-DOS 6.20 licensed copy sold for Microsoft with no 2000.
10. 1999 Windows 3.11 virus closes all applications leaving no exit.


Big Bertha Thing history

1st virus was boot sector virus, which was first sector of floppy disc or
start here sector.

2nd virus was program virus, which is enabled with on/off switch, by
operating system as primary function thereoff.(exe, sys, com)

3rd virus was macro virus, which is enabled with on/off switch, by
wordprocessor or other application software.(doc)

4th virus was zip virus, which is enabled with on/off switch, by
zip application software.(zip)

5th virus was text virus, which is enabled with on/off switch, by
operating system as a purely viral function, otherwise uneccessary.(txt)
Since 1980 the text virus has been impossible. 18 years to crack it, with
Windows 98 by Microsoft.

42 million Windows 3.xx users.
12 million e-mail only users.
Windows 95 not known.
Windows 98 not known.

Tony Lance
judemarie(a)bigberthathing.co.uk