jp.jpg (13389 bytes)

THE VIEW FROM CHAOS MANOR

View 108 July 3 - 9, 2000

read book now

HOME

VIEW

MAIL

Columns

BOOK Reviews

  For Current Mail click here.

Last Week's View                    Next Week's View

emailblimp.gif (23130 bytes)

This is a day book. It's not all that well edited. I try to keep this up daily, but sometimes I can't. I'll keep trying. See also the monthly COMPUTING AT CHAOS MANOR column, 4,000 - 7,000 words, depending.  (Older columns here.) For more on what this place is about, please go to the VIEW PAGE.

If you are not paying for this place, click here...

Day-by-day...
Monday -- Tuesday -- Wednesday -- Thursday -- Friday -- Saturday -- Sunday

For Previous Weeks of the View, SEE VIEW HOME PAGE

Search: type in string and press return.

 

For an index of previous pages of view, see VIEWDEX.
See also the New Order page, which tries to make order of chaos. These will be useful.
For the rest, see What is this place? for some details on where you have got to.

Boiler Plate:

If you want to PAY FOR THIS there are problems, but I keep the latest HERE. I'm trying. MY THANKS to all of you who sent money.  Some of you went to a lot of trouble to send money from overseas. Thank you! There are also some new payment methods. I am preparing a special (electronic) mailing to all those who paid: there will be a couple of these. I am also toying with the notion of a subscriber section of the page. LET ME KNOW your thoughts.
.

If you subscribed:

atom.gif (1053 bytes) CLICK HERE for a Special Request.

If you didn't and haven't, why not?

If this seems a lot about paying think of it as the Subscription Drive Nag. You'll see more.

For the BYTE story, click here.

 

For Current Mail click here.

Highlights this week:

 

The atomz Search returns:

Search: type in string and press return.

 The freefind search remains:

 

   Search this site or the web        powered by FreeFind
 
  Site search Web search

 

 

 

line6.gif (917 bytes)

This week:

Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday

TOP

Monday  July 3, 2000

My communication problems are intolerable. I have written a long description with a few premature speculations in last week's View. See that first

Today I went over every internal phone connection with Stabilant 22, on the theory that it is usually a cable. That has not helped. Next is some serious experimentation with the modem. First, I think I need to reinstall Outlook. It does seem that the line drops whenever Outlook is finished with its cycle, unless something else is using the line. Maybe Outlook is sending a "finished" signal although it has been told not to?

But that will be tested also if I put the modem over here where I can see the lights and hear anything, and perhaps get messages. I don't have any real way to operate other than the relentless application of logic and reductionism.

 

Ok, the experiments begin. First, I replaced the US Robotics Modem with the Creative Modem Blaster that was used until the current problems began; the first thing I did when the line was dropped every time was to change modems. I let the Netwinder connect through that, and as usual, it dropped the line after it did the assignments it was given.

Then I brought the USR over here to Princess and connected it directly to Port 2. Installation was simple. Turned on the modem. Dialup networking already had a connection to the local Earthlink number, the same one I have been connected through. Double click that. And it connected and I have not been dropped yet.

Clearly my problem is in the Netwinder or in something between here and there. I will next check all telephone cables but I don't think this is a case of the housekeeper cleaning thing up (Roberta had a printing problem while I was gone: the Ethernet connector to her NIC was pulled part way out; fixed that in a few seconds). This looks as if the Netwinder, although told to hang on to the line, is dropping it when it's not in demand, and redialing on demand. Clearly what I have now works, but of course I have no firewall at the moment. I have to fix that, possibly through a different Linux box, possibly some other way such as a different NT box. Something will be done and soon.

But my problem was not Earthlink. It is either a cable here, or the Netwinder isn't getting the instructions I think I am giving it.

At least I am not hearing the dialing process every few seconds. The problem DEFINITELY WAS NOT EARTHLINK, which has me connected at the moment at 44,000 and cleanly, and is not dropping me.

I was very pleased at the way the Netwinder worked, and I don't know what happened. I'll keep looking. It's probably a cable. Pournelle's Law says it will be 90% of the time...


And here is a frightening item:

Israel fears a Jewish civil war

By Tom Gross in Jerusalem

http://www.telegraph.co.uk/et?ac=000143789351982&;rtmo=lnPoHHHt&;atmo=rrrrrrrq&;p

g=/et/00/7/2/wisr02.html


Anyway, having solved the problem of line dropping -- at least having found a workaround -- I am going to go write. With luck Roland will know what's gone made with the Netwinder. It seems to have decided to hang up whenever there is no active demand on the modem. This is ungood.

 

TOP

 

This week:

Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday

TOP

Tuesday, INDEPENDENCE DAY 2000

Happy Birthday America

 

 

I have a chart on Head Start that may be of interest. We are off to a party shortly. There is a rant on this in mail.


The connection problem is almost certainly in the Netwinder scripts. Using the same phone line and the same modem, if I connect the modem direct to Princess (W 2000 Pro) it works and stays connected as long as I want; if I connect it to the Netwinder, it drops the line at more or less frequent intervals, randomly with intervals as long as an hour but generally as soon as there is no demand from any machine in the system; sand after a while it gives me the S10: Transmit timed out, bad line quality? message that repeats endlessly. At that point the machine WILL NOT ATTEMPT to dial, and this state endures until I hard reset the machine. (There may be a better way to reset that program, but inspection of my collection of Linux books fails to reveal it to me.)

Solutions: One is to use an NT machine in place of the Linux box and have that be the combination firewall and communications server. This is what Bob Thompson favors, and would have the advantage that I might know what I am doing: Linux like UNIX is guru friendly and requires a great deal of study and work. I had hoped the Netwinder would be an appliance-like system but it is not. On the other hand, I do intend to get to the bottom of this: what is going wrong? And surely there is a Linux command line command that will end the "S10: Transmit timed out, bad line quality?" messages that endlessly spew forth? But so far no one including Linux guru's have even hinted at what that command may be. Of course this is all frustrated by the fact that I don't know how to make this happen: just wait long enough with endless redialings and eventually it will.

With the system connected directly to Princess none of this happens. So tomorrow when I get some time I am going to set up an old junker NT4 box and use that to replace the Netwinder until we know more what is going on.

Now I am going to a party.

1800: we're back. Nice party in Malibu.

I have gone through four Linux books, and I find no reference to error message sl0 or s10, and no meaningful index entries to dialup services or modems. I presume that this guru friendly system has some means to tell the computer "Look, you had problems with the line, ignore them, reset yourself, and try dialing again" without physically resetting the system. I can do that in most flavors of Windows.  I have no way to figure out how to do that in Linux, which is what is wrong with Linux.  I have had to reset the Linux box over this problem far more times than I have had to reset Windows 2000 boxes over anything other than initial bad installations.

I am guessing that the answer to my question about resetting dialup services is difficult since in general when I pose a problem here, within hours (sometimes minutes) I get an answer or at least a hint. This is a bright readership and many use Linux. So my guess is that it's hard to find out what s10 or sl0 (it may be either; I didn't look that close and I'd have to get it to repeat the error to find out now) means, or how to cure it. 

I used to despise UNIX as being user hostile. 

 

TOP

 

This week:

Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday

TOP

Wednesday, July 5, 2000

I'll send an init string with a long s10 register number to the Netwinder and see if that does any good. However, I confess I am unhappy that I cannot find a simple command that will tell the Netwinder to ignore previous findings, stop endlessly sending the stupid s10 message, and try again. If there is such a command we can't find it. I'll get hold of Rebel today and see if they know.

Answers are beginning to come in; thanks to all.

Progress: not really. I have added S10=255 to the init string to the modem, and switched back to the Netwinder. It has dropped the line twice in the last couple of minutes, then redialed.  So the S10 register is not the problem (and indeed the message is Sugar love Zero, not S10: as I had thought. The font makes it very hard to distinguish them.

I'll have to go back to the local machine.  Roland is going to come over to see what he can do. Rebel thinks it may be the serial port on the box. Never had one of those go bad on anything as I recall, but who knows?  Sigh.

And I am going to take a hike and then write some fiction. And I have a column due shortly.


Roland is here, and the scripts on the Netwinder were not being saved properly. Ghu knows why...

The problem was not hardware. It wasn't the phone line quality. It was purely and simply a problem with the initializations for the dialup service in the Rebel box.

Rebel has used some non-standard scripting systems which give lovely visual layouts for inputting your data -- but that isn't being properly stored in the scripts that run at startup! Roland had to go in and edit the scripts in the actual files that are called in -- this is a bit like editing the Registry in Windows, something one does with a certain trepidation -- but the result is that the system stays up now. Indeed, what was needed was adding the word 'up' in a certain part of the dialup configuration script. And now it stays up and my Rebel is an appliance once again, and when we tell them what happened, they ought to be able to fix it for everyone else.

"I do all these silly things so you won't have to..."

Now I can turn to the column. I'm back where I was two weeks ago, with the Netwinder handling my internet connections; it's back to being an appliance, and thank heaven.

 

TOP

 

 

 

This week:

Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday

read book now

TOP

Thursday, July 6, 2000

Today I must do the column and supervise the Byte PCEXPO Awards process.  I won't have a lot of time.

The problem here was with the Netwinder scripts: they were not being copied properly to an essential file. Editing the configuration file for the dialup routine took care of the situation. This is more than annoying, but it was fixable.

 

 

TOP

 

 

 

This week:

Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday

TOP

Friday, July 7, 2000

Column Day

Which says it all. Too much to do. We have the BYTE.COM PCEXPO show awards done: they'll be up Monday. That took a lot of work. You'll like them.  BYTE will also have a story on my airline adventures.

Now to do the column. If you don't know about www.ahead.de have a look; their NERO ("Burning ROM") program is a marvel. See the column.

 

 

 

 

 

TOP

 

 

This week:

Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday

TOP

Saturday,

Column due.

 

 

TOP

 

 

This week:

Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday

read book now

TOP

Sunday, July 9, 2000

The column is off. Exhaustion sets in. Ah well. The NetWinder mysteries are solved and in the column. It's a mess here, but we're done for a while...

I'm going to go build a new Windows 2000 system for playing games...

I HAVE AN ODD REQUEST. I have had for years a rather silly game called "Chaos Overlords." It has few redeeming virtues but for some reason I rather liked it. I managed to misplace the CD for it, and it's no longer for sale anywhere I can find.  Does anyone have a copy?

 

 

 

  TOP

      Current View                                                         Current Mail

 

birdline.gif (1428 bytes)