Denyonet | MSX Resource Center (Página 6/7)

Paragon (1214)

12-04-2011, 21:29

WWWOOOOOOWWW !!!!
It works!
Thankyou edoz for convincing me!

I've tried FTP and TFTP, and they work! Retrieved a file from ftp.komon.org , all good!
Transferred a file from WinXP to MSX with TFTP launched as a listening server.

Some other experiments:
- I have also a VPN with a different IP family and pings don't work; tried also to make Briges, etc. but no story;
- TCPCON seems to work but I'd like most to use TELNET.COM; telnet asks me for INL installed, but it's already installed by INET.BAT, so what ... ?
- and finally TOO BAD I've read this statement on OBSOSMB help:

"typing "\\<MSX IP address>\<drive>" in the location bar of a window to see a list of the shared drives will not always work. In particular, it seems to never work on Windows XP."

Anyway, VERY GOOD WORK!!!
Can't wait any longer for a real Ethernet cartridge!

Por konamiman

Paragon (1198)

13-04-2011, 08:57

Dont forget to use the sharename .. for example \\ip\a (Windows is default getting ipc$)
Windows ALWAYS opens IPC$ and asks for the lists of shares, even when you use the "\\<IP>\<drive>" syntax. ObsoSMB recognizes that and delivers the list of shares by emulating RPC. But for some reason it does not always work except when using the NET VIEW command.

TCPCON seems to work but I'd like most to use TELNET.COM; telnet asks me for INL installed, but it's already installed by INET.BAT, so what ... ?
TELNET.COM is a INL 1 program. The version in the disk image file is INL 2 (all the other programs don't work with INL 1 anyway). I should remove Telnet program from the disk image.

and finally TOO BAD I've read this statement on OBSOSMB help:
"typing "\\<MSX IP address>\<drive>" in the location bar of a window to see a list of the shared drives will not always work. In particular, it seems to never work on Windows XP."
Huh? That's a typo. "\\<MSX IP address>\<drive>" will work (and will show you the contents of the shared drive). What does not always work is "\\<MSX IP address>" (which should show the list of the shared drives).

I'm happy to see that there is finally some movement around these networking applications.

Por enribar

Paragon (1214)

13-04-2011, 09:55

Hi 2 all, so this morning I've been experimenting ObsoNET emulation again.
This time in a network based on Windows Server 2003 (on VMWare) and with IBM AS400.
Emulation works only if I set static addresses, maybe DHCP doesn't work good with Winpcap + Antivirus + proxy + other "misterious net agents"

Btw, my interest is to interact with AS400 by a Telnet application. So in 2011 someone could buy a MSX and use it as a terminal!
But I'd need a working Telnet version for INL 2. Konamiman, could you help me?
Thankyou.

Por konamiman

Paragon (1198)

14-04-2011, 19:05

Sorry, but now I need to take a break. Maybe in the future.

Anyway, with all the documentation and the source code of networking applications available at my web site, I'm sure that someone could develop a neat Telnet client for the TCP/IP UNAPI. Anyone brave enough around here?

Por edoz

Prophet (2482)

14-04-2011, 19:43

i would like to do it but the problem is my MSX programming skills ..

Por edoz

Prophet (2482)

24-06-2011, 16:04

You can order now at sunrise .. very cool device .. … I’m now just waiting for delivery

Por Hydlide

Master (171)

30-06-2011, 13:24

They're available! Just got an email from Rob @Sunrise..
Now.. where's that MSX twitter client again..

Por mais1976

Master (172)

30-06-2011, 13:38

This is so cool, can't wait to have my denyonet.

And tweet it width the MSX twitter client

http://www.konamiman.com/msx/msx-e.html

Por Latok

msx guru (3938)

30-06-2011, 14:17

This is so cool, can't wait to have my denyonet.

And tweet it width the MSX twitter client

http://www.konamiman.com/msx/msx-e.html

That width typo is the best way to show you're an MSX-er. Cheers for that ^_^

Por konamiman

Paragon (1198)

30-06-2011, 14:50

That width typo is the best way to show you're an MSX-er. Cheers for that ^_^
I have the same problem. Whenever I have to write something containing "ms" (such as the name of the Windows configuration tool msconfig) I always write "msx" the first time.