3 Jan
2005
3 Jan
'05
8:21 a.m.
Hi
I'm almost sure I'd done this in the past to
get something like laplink running on a remote machine.
I suspect that the code specifically had no ^Z
until the end of the file and it was just a minimum
bootstrap program to load the rest.
One could always edit the file by changing any ^Z to
something else. Once on the new machine, just change them
back.
I do remember that the name of the file couldn't be
.COM or .EXE. I think the copy from COM1: didn't
work for those files names.
Dwight
From: "Pete Turnbull"
<pete(a)dunnington.u-net.com>
On Jan 3 2005, 13:01, John Foust wrote:
At 12:41 PM 1/3/2005, you wrote:
You can't, in MS-DOS. COPY uses ASCII transfers for COM ports and
complains if you try to force binary, because it needs to see a ctrl-Z
to know where the end-of-file is.
--
Pete Peter Turnbull
Network Manager
University of York
It seems like I remember doing something
like "copy COM1: FileName" or something.
It seems like I remember there being an issue
with the file name extention.
And perhaps something else about setting the mode of the COM1:
port for bits and binary? 
3 Jan
3 Jan
5:46 p.m.
Yes, as far as I can recall Laplink had this exact facility, perhaps
using the CTTY command instead of COPY, but I may be thinking of some
other program.
Writing such a bootstrap would be an interesting exercise.
LJW
On Mon, 2005-01-03 at 22:21, Dwight K. Elvey wrote:
Hi
I'm almost sure I'd done this in the past to
get something like laplink running on a remote machine.
I suspect that the code specifically had no ^Z
until the end of the file and it was just a minimum
bootstrap program to load the rest.
One could always edit the file by changing any ^Z to
something else. Once on the new machine, just change them
back.
I do remember that the name of the file couldn't be
.COM or .EXE. I think the copy from COM1: didn't
work for those files names.
Dwight
>From: "Pete Turnbull" <pete(a)dunnington.u-net.com>
>
>On Jan 3 2005, 13:01, John Foust wrote:
>> At 12:41 PM 1/3/2005, you wrote:
>> > It seems like I remember doing something
>> >like "copy COM1: FileName" or something.
>> > It seems like I remember there being an issue
>> >with the file name extention.
>>
>> And perhaps something else about setting the mode of the COM1:
>> port for bits and binary?
>
>You can't, in MS-DOS. COPY uses ASCII transfers for COM ports and
>complains if you try to force binary, because it needs to see a ctrl-Z
>to know where the end-of-file is.
>
>--
>Pete Peter Turnbull
> Network Manager
> University of York
>
--
Lawrence Wilkinson lawrence(a)ljw.me.uk
Ph +44(0)1869-811059 http://www.ljw.me.uk
4 Jan
4 Jan
4:27 a.m.
>
> >From: "Pete Turnbull" <pete(a)dunnington.u-net.com>
> >
> >
> >You can't, in MS-DOS. COPY uses ASCII transfers for COM ports and
> >complains if you try to force binary, because it needs to see a ctrl-Z
> >to know where the end-of-file is.
Use COPY /B to force it to do a Binary copy. (FWIW /A forces it to do an
Ascii copy).
Joe
5 Jan
5 Jan
11:03 a.m.
On 04 Jan 2005 07:46:00 +0000, Lawrence Wilkinson <ljw-cctech(a)ljw.me.uk> wrote:
Yes, as far as I can recall Laplink had this exact
facility, perhaps
using the CTTY command instead of COPY, but I may be thinking of some
other program.
Writing such a bootstrap would be an interesting exercise.
LJW
This is correct - the Sharp PC-3000 palmtop (of which I have a faulty
one here - it used to work fine though) has a version of Laplink in
ROM which can do exactly this.
There's a menu option like "Upload client to remote side" or
something, which then displays "Type the following commands on the
connected machine and then press return" or similar. ISTR there are
about 3 commands it displays which you type on the remote side; at
least one of them is to do with setting the speed of the serial port,
and I think at least one of them involved COPY. You certainly didn't
need anything other than plain DOS on the machine you were uploading
to.
Ed.
On Mon, 2005-01-03 at 22:21, Dwight K. Elvey wrote:
Hi
I'm almost sure I'd done this in the past to
get something like laplink running on a remote machine.
I suspect that the code specifically had no ^Z
until the end of the file and it was just a minimum
bootstrap program to load the rest.
One could always edit the file by changing any ^Z to
something else. Once on the new machine, just change them
back.
I do remember that the name of the file couldn't be
.COM or .EXE. I think the copy from COM1: didn't
work for those files names.
Dwight
>From: "Pete Turnbull" <pete(a)dunnington.u-net.com>
>
>On Jan 3 2005, 13:01, John Foust wrote:
>> At 12:41 PM 1/3/2005, you wrote:
>> > It seems like I remember doing something
>> >like "copy COM1: FileName" or something.
>> > It seems like I remember there being an issue
>> >with the file name extention.
>>
>> And perhaps something else about setting the mode of the COM1:
>> port for bits and binary?
>
>You can't, in MS-DOS. COPY uses ASCII transfers for COM ports and
>complains if you try to force binary, because it needs to see a ctrl-Z
>to know where the end-of-file is.
>
>--
>Pete Peter Turnbull
> Network Manager
> University of York
>
--
Lawrence Wilkinson lawrence(a)ljw.me.uk
Ph +44(0)1869-811059 http://www.ljw.me.uk
7:57 p.m.
listmailgoeshere(a)gmail.com wrote:
This is correct - the Sharp PC-3000 palmtop (of which
I have a faulty
one here - it used to work fine though) has a version of Laplink in
ROM which can do exactly this.
My Toshiba T1000EX has Laplink in ROM (in fact, DOS 3.3 in ROM IIRC).
There's a menu option like "Upload client to
remote side" or
something, which then displays "Type the following commands on the
connected machine and then press return" or similar. ISTR there are
about 3 commands it displays which you type on the remote side; at
least one of them is to do with setting the speed of the serial port,
and I think at least one of them involved COPY. You certainly didn't
need anything other than plain DOS on the machine you were uploading
to.
I think the last one is "CTTY COM?:" where ? is the port number. This
lets the serial port become the console, at which point Laplink takes
over and builds up a copy on the other machine somehow.
Gordon.
7241
days inactive
7244
days old
4 comments
5 participants
participants (5)
-
dwight.elvey＠amd.com -
gordon＠gjcp.net -
listmailgoeshere＠gmail.com -
ljw-cctech＠ljw.me.uk -
rigdonj＠cfl.rr.com