-=> Quoting Danial Gibson to Tika Carr <=-
 DG> 386 and up are all 32-bit. DOS is only 16-bit. WinNT is 32. Win95 is
 DG> mostly 32. My point: the 486 is 32-bit. Except, you said 'true
 DG> 32-bit'. What does this mean? And told by whom? (actually I prefer who,
 DG> but I'm told that whom is correct).
Well, I stand corrected (and Jerry was right too). I mentioned this to
my friend that told me and she also admitted she forgot and said it
wrong (IOW, she admidts you both are right). 486s are 32-bit machines,
and Pentiums 64-bit. I think I got it now. 
 DG> Another word for bit-chunking/banging is bit-thunking as used by the
 DG> win32 dox. Where's ANSI when you need them? :)
Really!  I used to have a Tandy CoCo 3 (16-bit machine) and the
serial port in the back of it was... get this... 4-bit! So it was
referred to as the "bit-banger port".  And "bit-chunking" I got wrong...
you got it right with "bit-thunking". The term escaped me there for a
moment. 
 DG> This won't work anyway. I wasn't too accurate in my original message.
 DG> I meant that if I send a message, I get the message twice, not just
 DG> each character. eg:
 DG> I send 'A'     I get 'AA'
 DG> I send 'TIKA'  I get 'TIKATIKA'
Right. I was figuring (and could be wrong) that 'A' would be sent in the
first 32-bits. Then the Pentium just added that same 32-bits of info to
make 64-bits and you get it twice...
        486                 Pentium
    A(the rest 0s)          A(the rest 0s)A(the rest 0s)
    32 bits                 32 bits       32 bits
The 0s you never see though, of course. IOW, you may want to try only
reading the 1st 32 bits and disregarding the other 32 bits of the
message...
That was my theory. But, not knowing what goes in/out of a network, I
could be way off.
 DG> I was thinking that maybe it's for error detection. But then, how
 DG> would you know a) if 1 of the messages was left out and b) which was
 DG> correct?
Check the first set (32) with the second. If they are exact, the message
was ok. If not, ask the 486 to retransmit the last block?
 TC>Tika
 DG> Interesting name. How is it pronouced? Tie-ka, tee-ka
Second way. :)
 TC>             Phantom's Gate - Home of the Hacker's Haven
 TC>     http://www.frontiernet.net/~phantom7 * phantom7@frontiernet.net
 DG> What's here? I tried to get there but the connection was screwed up at
 DG> college today. (teachers _teach_, they don't _know_)
 That's for sure! Its called "Phantom's Realm" now and is under
construction. There's only one area to go into, the Computer Programming
area. There's stuff on C/C++, QuickBasic, General help, OWL and OWL
Winsock, and Web Site Development. I'm still working on things in that
area before I add another to the site.
 TC>  ! Origin: Knight Moves - Rochester,NY 716-865-2106 (1:2613/313)
 DG> Is this NY New York? Let's check...
 DG> Yep, sysop Ken Serikstad. Wow, this message reached NY
 DG> quickly. What's the weather like there?
Usually things get out fast from here (and another BBS I frequent). I've
had good luck with the echoes and systems where I live. The weather is
cool and rainy. Typical April. Sometimes a bit of snow but not much. I
am eager for warmer weather (but not TOO warm! )
 DG> So what do you anyway? Uni/work?
Uni?? Not sure what you mean. Work - I don't/can't. (long totally
off-topic story I rather not tell). I program for a hobby, when I'm able
to.
 DG> Also, if it was cause of 16/32 bit hassles, then wouldn't other
 DG> network stuff screw up too? Like the winpopup thing. Either it's a
 DG> setting in the mailslot init stuff, or it does it all the time. Another
 DG> guy I talked to says all the time. I think it's time to goto the
 DG> library and do a bit of research.
Well, I think they write the stuff to compensate for things like that.
Not sure how or you'd probably have your answer by now. 
Tika
... Programmer (n.) A device for converting coffee into computer code.
___ Blue Wave/DOS v2.30
--- QScan/PCB v1.17b / 01-0406
---------------