2 Aug
2005
2 Aug
'05
9 a.m.
--------------Original Message(s):
Message: 13
Date: Mon, 01 Aug 2005 10:53:39 -0500
From: John Foust <jfoust at threedee.com>
Subject: Re: classiccmp knowledgebase
To: <cctalk at classiccmp.org>
Message-ID: <6.2.1.2.2.20050801105059.050c6d98 at mail>
Content-Type: text/plain; charset="us-ascii"
At 01:54 AM 8/1/2005, you wrote:
Wouldn't it be easier to just issue two MODE
commands to redirect COM1: to CON, then feed debug a script to write out binary files?
Hey, that's why I think it would be a useful and interesting FAQ.
I thought the other guy's CTRL/Z preservation method was quite
cute, too. I'm intrigued by solutions that would require a
minimum of prep or magic tools on the sending PC.
- John
----------------Reply:
Assuming the server is also running DOS, it seems to me the
least prep or magic would be to use Interlnk/Intersvr, included
in MS-DOS since around version 5. It can use serial or
parallel ports, redirect remote drives and printers, and can do a
remote install if the receiving computer doesn't have a copy of
Interlnk. Needs a null modem serial cable of course, or a
LapLink type of Parallel cable or adapter. Same as LapLink;
not as fancy, but free. Check out the help files for Interlnk & Intersvr.
Didn't we just have a lengthy discussion about this a while ago?
mike
4 Aug
4 Aug
10:35 a.m.
If anybody remembers the old versions of laplink where they told you to
issue a mode command etc to redirect com1
Iirc you can use that to install any file onto the pc you just had to
give it the filename as an option ymmv
Regards and 73
Charles - 2E0GOM
ARICC UK Co-Ordinator - http://www.aricc.org
Kirklees RAYNET - http://www.kirkleesraynet.org.uk
-----Original Message-----
From: M H Stein [mailto:dm561 at torfree.net]
Sent: 02 August 2005 17:00
To: 'cctech at classiccmp.org'
Subject: PC<>PC File transfer (was classiccmp knowledgebase)
--------------Original Message(s):
Message: 13
Date: Mon, 01 Aug 2005 10:53:39 -0500
From: John Foust <jfoust at threedee.com>
Subject: Re: classiccmp knowledgebase
To: <cctalk at classiccmp.org>
Message-ID: <6.2.1.2.2.20050801105059.050c6d98 at mail>
Content-Type: text/plain; charset="us-ascii"
At 01:54 AM 8/1/2005, you wrote:
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.9.9/62 - Release Date: 02/08/2005
Wouldn't it be easier to just issue two MODE
commands to
redirect COM1:
to CON, then feed debug a script to write out
binary files?
Hey, that's why I think it would be a useful and interesting
FAQ. I thought the other guy's CTRL/Z preservation method was
quite cute, too. I'm intrigued by solutions that would require a
minimum of prep or magic tools on the sending PC. 
7:26 p.m.
On Thu, 4 Aug 2005 18:35:06 +0100
"Charles Blackburn" <charlesb at otcgaming.net> wrote:
If anybody remembers the old versions of laplink where
they told you
to issue a mode command etc to redirect com1
Iirc you can use that to install any file onto the pc you just had to
give it the filename as an option ymmv
My smallest laptop is an HP Omnibook 300, which includes built-in
Laplink. It only has PCMCIA slots and harkens back to the Windows 3.1
era (it has Windows 3.1 in run-in-place ROM on a special PCMCIA card) so
there's nothing fancy about it and it's designed to connect to 'classic'
peecees over serial or parallel interfaces. All you need to 'connect'
it to another DOS PC is the serial or parallel laplink cable. It has a
built-in function to 'inject' the Laplink remote access TSR with the
mode command and com1 redirection.
Pulling up the install procedure in the Windows 3.1 dialogues of the
Omnibook, it says to enter the following two commands at the remote end
you're 'injecting' llremote into:
mode com1:2400,n,8,1,p
ctty com1
Then you click 'ok' on the Windows dialogue on the Omnibook that cited
the two preceeding commands and it sends the remote client. I've never
'reverse engineered' it to see how it accomplishes it's work.
The tiny executable that it 'injects' into the remote system, called
llremote.exe, is a TSR that also works peer-to-peer on any two DOS
machines and automatically maps ALL remote drives on either end to the
two host machines connected with 'Laplink' serial or parallel cables. I
actually went out afterwards and bought commercial 'Laplink' thinking it
would be that good (llremote.exe is an 84 kb executable and
semi-transparently remaps the drives peer-peer). Commercial Laplink is
a dog by comparison (IMHO).
The only way I know to 'license' llremote.exe is to have bought an HP
Omnibook 300, which was a $2400 386sx laptop with 2 megs of RAM. (which
was enough RAM to run Windows 3.1, Excel, and Microsoft Word all
concurrently, since the machine has unique 'run-in-place' versions that
run directly out of ROM so don't use RAM- something only the technical
wizards at Hewlett-Packard's Corvalis Division (the same place that
produced the HP Calculator line, and the HP95/100/200LX systems) could
produce.
(I've gushed about the Omnibook 300 before, thanks for bearing with me
on this)
7124
days inactive
7127
days old
2 comments
3 participants
participants (3)
-
charlesb＠otcgaming.net -
chenmel＠earthlink.net -
dm561＠torfree.net