if anybody is interested, i wrote a VNC client for DOS in quickbasic last night... i compiled a preliminary version, and you can download it here.

just trying to help out DOS users.

download link: http://rubbermallet.org/qbvnc.zip

i'll be adding VESA support soon for better resolutions.

QuickBasic VNC? Wow! How about a DHCP client
to set WatTCP.CFG/DOS environment variables...

¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Salutations,

Michel Samson
a/s Bicéphale

you mean like ask a DHCP client for an address and make the .cfg file so that the computer uses that every time?

yeah i could handle that, and write you a lil' utility :)

gimme a day or two and i'll get back to you on here.

luckily i wrote a wattcp interface for QB a few months ago too. i used tcpdrv(as you prolly noticed) for this vnc client.

er... ask a server i meant, not client lol

Hi Mike,

This sounds like great news to me: there's been a
few instances this year where it might have helped
some users to have their WatTCP environment ready!

My favourite applications aren't DHCP-aware, i set
DOS environment variables and build the WatTCP.CFG
configuration-file from there. LSPPP/EPPPD create
a batch-file called `IP-Up.BAT', perhaps a similar
drop-file would do nicely for people like me as it
should allow control over our WatTCP.CFG contents.

8-)

If you're after a more potent challenge, something
like `Go.BAT' meant as a fool-proof feature should
spare the patience of users who just can't manage:
those guys need WatTCP.CFG to be built for them...

It may be desirable to use a flag to choose which.

;-D

Finally, one step further since this extraordinary
opportunity is too rare to be neglected: i'd push
my luck to the point of suggesting that the client
should be part DOS-WatTCP part W32-NDIS so that it
is compatible with Lawrence Rust's SwSVPkt adaptor
as well! Even when it's DHCP-ready, i don't think
Arachne, Lynx or whatever can auto-configure while
executing in a Windows DOS box and legacy software
even less; W32-NDIS/DHCP support is available for
console applications (SwSVPkt included but it does
not seem to pass this ressource), the contribution
you'd make by writing such a utility would fill an
old gap that left no room for hope until recently.

DOS Peripheral deprivation has plagued Windows for
so long we forgot why we prefer plain-DOS exactly!

8-b

I must thank you warmly for the proposal, it's not
everyday i can witness one of these!... Take your
time if you will, a few days make no difference to
former DOS/INet BBSers like me. I'll be more than
willing to try out the DHCP client you'll publish!

8-D

¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Salutations,

Michel Samson
a/s Bicéphale

What difference would this be to the ROM-DOS util that detects if a DHCP server is present and writes 'my_ip = DHCP' to wattcp.cfg

Hi Ricard,

`\Sockets\Utils\PDTest.EXE' is the only executable
i can use with a Class-1 WatTCP-compatible Packet-
Driver. The rest of the applications mention some
Sockets/RINET APIs, or even WinSock v1.1! This is
most likely useless under the given circumstances;
`SocketP.EXE' needs 82528 bytes of memory, imagine
that once the Packet-Driver itself is loaded... I
need more than a couple hours of investigation but
i didn't find it intuitive if it's supposed to fit
this discussion anyway. The only surprize i enjoy
with this thing is the Z-MoDem protocol driver and
even at that i must point out it doesn't work with
anything else than standard serial-ports, in 2006!

The least i can say about `ROM-DOS' so far is that
i wouldn't recommend it to a guy who wishes to use
Arachne and lets forget about migrating to Windows
with help from WsWVpkt because i seen some message
says "This program cannot be run under Windows NT"
at times... I hope this reply makes sense to you.

¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Salutations,

Michel Samson
a/s Bicéphale