Network transmission problem.

Helpful tips and guides, also new users can ask for help here.
Jack_Free
ROM Dongle
Posts: 41
Joined: Sun Aug 30, 2015 3:31 pm

Network transmission problem.

Postby Jack_Free » Sun Jan 20, 2019 3:47 pm

I have a problem, I have connected two machines to the network (NET1, NET2)
At one station, I enter NET1 on the other NET2 and then run FSERVE.
I can read the NET1 machine directory on NET2, but I can not copy files from NET1 to NET2 or vice versa.
I use WCOPY N1_WIN1_xxx_ to N2_ROM1_
After some time I get a net aborted not complete report.

Toolkick II I have on each machine.
It did not help to change cables or change the port.

DIR command works, COPY or WCOPY can not be used.
I tried nono and stereo jack, it still does not work.

For every advice he will be grateful.


I do not use an emulator, just a real QL, excuse my English, I use google translator :-)
Sinclair QL + SGC, Sinclair QL+Qubide interface, Sinclair QL+QL-SD.
User avatar
tofro
QL Wafer Drive
Posts: 1585
Joined: Sun Feb 13, 2011 10:53 pm
Location: SW Germany

Re: Network transmission problem.

Postby tofro » Sun Jan 20, 2019 3:56 pm

Is the Toolkit in ROM on both machines?

Contended RAM (the lower 128kBytes share the data bus between CPU and video controller) can change the network timing in a way that QLNET connectivity might be severly harmed)

Tobias


ʎɐqǝ ɯoɹɟ ǝq oʇ ƃuᴉoƃ ʇou sᴉ pɹɐoqʎǝʞ ʇxǝu ʎɯ 'ɹɐǝp ɥO
Jack_Free
ROM Dongle
Posts: 41
Joined: Sun Aug 30, 2015 3:31 pm

Re: Network transmission problem.

Postby Jack_Free » Sun Jan 20, 2019 4:28 pm

Thank you very much for your advice.
Yes TOOLKIT is on.
I've already figured it out, I was wrong to order.
If I copy from N1 to N2 I am using, I can not enter the address of N2 station

I used the WCOPY N1_WIN1_XXX TO N2_ROM1_ which is a bad write must be WCOPY N1_WIN1_XXX TO ROM1_ the N2 station name is not entered.

Then everything works as it should.
Beginner's error.


I do not use an emulator, just a real QL, excuse my English, I use google translator :-)
Sinclair QL + SGC, Sinclair QL+Qubide interface, Sinclair QL+QL-SD.
martyn_hill
Super Gold Card
Posts: 514
Joined: Sat Oct 25, 2014 9:53 am

Re: Network transmission problem.

Postby martyn_hill » Sun Jan 20, 2019 4:32 pm

Hi Jack!

When specifying the _local_ QL, you refer it it via its local devices - not by its Nx_ node-name, thus, to copy from N2 to N1:

On NET1, type:

COPY "N2_win1_xxx" TO "win1_yyy"

The file will be saved as win1_yyy on NET1.

FSERVE would be needed only on NET2, for this example.

Good luck - there is a lot of practical fun to be had once you can successfully network QLs (with TK2)!


User avatar
tofro
QL Wafer Drive
Posts: 1585
Joined: Sun Feb 13, 2011 10:53 pm
Location: SW Germany

Re: Network transmission problem.

Postby tofro » Sun Jan 20, 2019 4:37 pm

martyn_hill wrote:Good luck - there is a lot of practical fun to be had once you can successfully network QLs (with TK2)!


Note you cannot only open channels to a storage device on the remote machine - The fun starts when you start opening devices like CON_ or SCR_ on the remote machine or even use the MEM device driver (part of the DIY toolkit) to read or write memory on the remote QL.

Tobias


ʎɐqǝ ɯoɹɟ ǝq oʇ ƃuᴉoƃ ʇou sᴉ pɹɐoqʎǝʞ ʇxǝu ʎɯ 'ɹɐǝp ɥO
User avatar
dilwyn
Mr QL
Posts: 1487
Joined: Wed Dec 01, 2010 10:39 pm
Location: Wales
Contact:

Re: Network transmission problem.

Postby dilwyn » Sun Jan 20, 2019 5:35 pm

tofro wrote:
martyn_hill wrote:Good luck - there is a lot of practical fun to be had once you can successfully network QLs (with TK2)!


Note you cannot only open channels to a storage device on the remote machine - The fun starts when you start opening devices like CON_ or SCR_ on the remote machine or even use the MEM device driver (part of the DIY toolkit) to read or write memory on the remote QL.

Tobias

We used to have fun with this at Quanta workshops in the 1980s/1990s.

For example, the late Joe Haftke and I used to open console channels to each other's machines as a simple messaging system and chat away over that, even though we were on adjacent tables.

Once, I managed to incur the wrath of Ron Dunnett (Qubbesoft) by sneakily attaching a long network lead to his QL when he wasn't looking and simulate all kinds of errors by opening a channel to cover the channel #0 on his machine and printing continuous random error messages to it. When he found out what I was up to, he quietly got revenge by repeatedly copying files to a ramdisk on my machine, slowing it down to a crawl just as I was trying to demonstrate one of my programs to a customer.

Fun days :)


Dilwyn
All things QL: see www.dilwyn.me.uk

Who is online

Users browsing this forum: No registered users and 1 guest