Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

LocoLink and the PcW16

29 views
Skip to first unread message

John Elliott

unread,
Mar 20, 2002, 3:00:50 PM3/20/02
to
One of the things that it says about the PcW16 in all the FAQs is that
it has at least some of LocoLink built in. So this evening I set up a
PcW16 and a PCW9512 side by side, plugged the cables in, booted
LocoLink 2.02 on the 9512, turned on the 16, created a new document, and
selected the "Import" option.

Nothing happened.

Just to check that system was working properly, I connected the 9512
to a PC running LocoScript Professional. LocoLink worked first time.
Back to the PCW16. Nothing.

So what _is_ the story with the PCW16 and LocoLink?

--
------------- http://www.seasip.demon.co.uk/index.html --------------------
John Elliott |BLOODNOK: "But why have you got such a long face?"
|SEAGOON: "Heavy dentures, Sir!" - The Goon Show
:-------------------------------------------------------------------------)

John Elliott

unread,
Mar 20, 2002, 4:25:09 PM3/20/02
to
Oh, and while we're on the LocoLink topic, PCW Plus once reviewed a
program suite called "PCWlink" by Three Inch Software (round about
October 1992, I think). It was supposed to allow you to LocoLink two PCWs,
provided that one was a 9512. Does anyone have a copy of it?

Kevin Thacker

unread,
Mar 21, 2002, 6:13:15 AM3/21/02
to
j...@seasip.demon.co.uk (John Elliott) wrote in message news:<1016654448.21051....@news.demon.co.uk>...

> One of the things that it says about the PcW16 in all the FAQs is that
> it has at least some of LocoLink built in. So this evening I set up a
> PcW16 and a PCW9512 side by side, plugged the cables in, booted
> LocoLink 2.02 on the 9512, turned on the 16, created a new document, and
> selected the "Import" option.
>
> Nothing happened.
>
> Just to check that system was working properly, I connected the 9512
> to a PC running LocoScript Professional. LocoLink worked first time.
> Back to the PCW16. Nothing.
>
> So what _is_ the story with the PCW16 and LocoLink?
I know it is in the ROM, and appears to work like any other
filesystem.

Here is a quote:
".... LOCOLINK support. This is
automatically invoked when File Selector is called for IMPORT if CP/M
discs are
permitted and the LocoLink cable is present and able to communicate
with
a remote PcW. "

Some kind of detection is required and then it seems that options will
appear on the file selector where you can choose locolink.

It seems the detection works on a disk change, a CP/M disc should be
in the PCW16 drive, and the locolink should be connected and started.
Possibly as the PcW as the master.

Kev

Howard Fisher

unread,
Mar 22, 2002, 12:22:09 PM3/22/02
to
In article <1016654448.21051....@news.demon.co.uk>, John
Elliott <j...@seasip.demon.co.uk> wrote

> One of the things that it says about the PcW16 in all the FAQs is that
>it has at least some of LocoLink built in. So this evening I set up a
>PcW16 and a PCW9512 side by side, plugged the cables in, booted
>LocoLink 2.02 on the 9512, turned on the 16, created a new document, and
>selected the "Import" option.
>
> Nothing happened.
>
> Just to check that system was working properly, I connected the 9512
>to a PC running LocoScript Professional. LocoLink worked first time.
>Back to the PCW16. Nothing.
>
> So what _is_ the story with the PCW16 and LocoLink?
>
I'm speaking from memory here, but I'm pretty sure you need the LocoLink
for Windows PCW disc, not the LocoLink for LocoScript disc.
--
Howard Fisher

John Elliott

unread,
Mar 22, 2002, 6:43:41 PM3/22/02
to
Howard Fisher <Howar...@Locomotive.com> wrote:
>I'm speaking from memory here, but I'm pretty sure you need the LocoLink
>for Windows PCW disc, not the LocoLink for LocoScript disc.

[looking up from heaps of ROM disassmblies, xanne and xjoyce packet logs,
etc]

Sounds likely. The first packet that the PCW16 sends starts 5A,46,31
where the receiver expects 0B,41,31.


--
John Elliott

0 new messages