ne2000wc.zip 11.09 KiB 1996-05-01 Warp Connect NE2000-compatible network adapter (20-Jun-95)
Networking discussion
Re: Networking discussion
I can confirm that this driver, ne2000wc works in OS/2 Warp 3.0 Connect.
- ppgrainbow
- Posts: 479
- Joined: Thu 04 Sep, 2014 7:03 am
- Contact:
Re: Networking discussion
That network compatible driver should do the trick!neozeed wrote:I can confirm that this driver, ne2000wc works in OS/2 Warp 3.0 Connect.
ne2000wc.zip 11.09 KiB 1996-05-01 Warp Connect NE2000-compatible network adapter (20-Jun-95)
Re: Networking discussion
Although the latest update is only a Win64 fix (I never can seem to build this under Win64... grrr) Here is an updated Win32 binary:
PCem-build-335-pcap-slirp.7z
I've only included 2 executables, the debug, and an -O2 fast float. It turns out all the other stuff had a negligible impact on performance. I wouldn't call it the 'best possible' but overall the 1-2% difference and having executables crash just isn't worth it.
Let me know if you have exe issues with this build!
And for the gopher fans, this ought to be a direct link!
gopher://nodedeploy.superglobalmegacorp.com:70/00/install/pcem/PCem-build-335-pcap-slirp.7z
PCem-build-335-pcap-slirp.7z
I've only included 2 executables, the debug, and an -O2 fast float. It turns out all the other stuff had a negligible impact on performance. I wouldn't call it the 'best possible' but overall the 1-2% difference and having executables crash just isn't worth it.
Let me know if you have exe issues with this build!
And for the gopher fans, this ought to be a direct link!
gopher://nodedeploy.superglobalmegacorp.com:70/00/install/pcem/PCem-build-335-pcap-slirp.7z
Re: Networking discussion
Crap, I built both exe's as debug by mistake, I've updated the archive. Also I included the OpenAL32 runtime for people that don't have it.
Re: Networking discussion
BTW, to get pcap network to work, I have to use just the interface GUID in pcap_device setting in pcem.cfg - it doesn't work with the \Device\NPF_ prefix.
Re: Networking discussion
Can you run the debug version, and tell me what version of pcap it is picking up on your system?ender wrote:BTW, to get pcap network to work, I have to use just the interface GUID in pcap_device setting in pcem.cfg - it doesn't work with the \Device\NPF_ prefix.
I know \Device\NPF_{guid} works in mine....
Re: Networking discussion
Code: Select all
pcap_device = {6F2E068C-EB95-4887-9887-D2B0CA99A50C}
midi = 0
[Novell NE2000]
netcard = 1
addr = 0x300
irq = 10
[Sound Blaster AWE32]
onboard_ram = 2048
Config loaded
Starting with romset 26
timer_reset
ne2000 pcap device {6F2E068C-EB95-4887-9887-D2B0CA99A50C}
ne2000 reset
ne2000 init 0x300 10 slirp is 0 net_is_pcap is 1
ne2000 initalizing libpcap
ne2000 Pcap version [WinPcap version 4.1.3 (packet.dll version 10, 1, 0, 5001), based on libpcap version 1.0 branch 1_0_rel0b (20091008)]
ne2000 pcap is currently in blocking mode
ne2000 Setting interface to non-blocking mode......!
ne2000 Building packet filter.........!
ne2000 Using filter [( ((ether dst ff:ff:ff:ff:ff:ff) or (ether dst ac:de:48:88:bb:aa)) and not (ether src ac:de:48:88:bb:aa) )]
ne2000 net_is_pcap is 1 and net_pcap is e4107c8
ne2000 is_slirp 0 is_pcap 1
Code: Select all
Network devices:
Number NAME (Description)
0 {B1D364E8-1113-4A5C-9F1E-98EFD32EC522} (TAP-Windows Adapter V9)
1 {6F2E068C-EB95-4887-9887-D2B0CA99A50C} (Intel(R) 82574L Gigabit Network Connection)
2 {9B4D31C9-70AD-4154-A956-5F3ACC2521F2} (VMware Virtual Ethernet Adapter)
3 {B15B41C9-B4BE-4323-B581-0D39D82078F1} (TAP-Windows Adapter V9)
4 {676FC95C-4301-43B8-BEAC-D69F75EB7463} (VMware Virtual Ethernet Adapter)
5 {42159F16-615F-4F33-936F-121A84D60E21} (Oracle)
6 {BF540878-2DF5-46C2-B86C-1E46C5146A93} (Intel(R) 82574L Gigabit Network Connection)
Press Enter to continue...
Re: Networking discussion
Ok, so your winpcap is newer I guess, still version 4.13 although yours reports version 10 build 5001? When you list them it only shows the GUID... so I guess at that same time, it makes sense that whatever is in the name field needs t be consistent.
Pcap version [WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008)]
Pcap version [WinPcap version 4.1.3 (packet.dll version 10, 1, 0, 5001), based on libpcap version 1.0 branch 1_0_rel0b (20091008)]
Good to know at any rate!
I assume it works fine?
Pcap version [WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008)]
Pcap version [WinPcap version 4.1.3 (packet.dll version 10, 1, 0, 5001), based on libpcap version 1.0 branch 1_0_rel0b (20091008)]
Good to know at any rate!
I assume it works fine?
Re: Networking discussion
I've got Win10pcap installed, maybe that's the reason.
BTW, do you plan to add any configuration UI for network?
Yup, no problems that I noticed.neozeed wrote:I assume it works fine?
BTW, do you plan to add any configuration UI for network?
Re: Networking discussion
Yeah, my laptop decided to die on me, so that has basically taken me out of the race so to speak, I've had to use my work machine...ender wrote:I've got Win10pcap installed, maybe that's the reason.Yup, no problems that I noticed.neozeed wrote:I assume it works fine?
BTW, do you plan to add any configuration UI for network?
But I just scored an old laptop with Windows 7, and like an idiot I wasted a day and got Windows 10 running on it. I know with a UI I can scroll through whatever pcap tells me is there, so it won't matter if it's registery names, GUIDS, or whatever else they chose to represent ethernet cards.
I also wanted to work in something like the DOSBox ipxrelay thing as well. I need to bug someone else about some kind of discovery service, or maybe not bother. I kind of imagine stuff like deathmatches with it, but maybe I'm dreaming.
- ppgrainbow
- Posts: 479
- Joined: Thu 04 Sep, 2014 7:03 am
- Contact:
Re: Networking discussion
*yawn*
Has anyone tried running DESQview/X with the NE2000 network card? According to the ToastyTech article on DESQview/X, you can run applications remotely!
Anyone have a idea how this can be done with the current revision of PCem and other emulated machines such as VMware Player and VirtualBox?
Has anyone tried running DESQview/X with the NE2000 network card? According to the ToastyTech article on DESQview/X, you can run applications remotely!
Anyone have a idea how this can be done with the current revision of PCem and other emulated machines such as VMware Player and VirtualBox?
Re: Networking discussion
Yes, I have it running it in QEMU, MAME and on a real machine.
See my posting on BetaArchive:
http://www.betaarchive.com/forum/viewtopic.php?t=28286
Some instruction on how to install in MESS (not from me):
http://forums.bannister.org/ubbthreads. ... mber=86865
(you will need to adapt the network install as at the time of writing the 3com emulation was used in these intructions)
See my posting on BetaArchive:
http://www.betaarchive.com/forum/viewtopic.php?t=28286
Some instruction on how to install in MESS (not from me):
http://forums.bannister.org/ubbthreads. ... mber=86865
(you will need to adapt the network install as at the time of writing the 3com emulation was used in these intructions)
Re: Networking discussion
Ive done it once before. it was a little underwhelming. Maybe it would be cool before linux, but it needing quemm and novel TCP/IP.ppgrainbow wrote:*yawn*
Has anyone tried running DESQview/X with the NE2000 network card? According to the ToastyTech article on DESQview/X, you can run applications remotely!
Anyone have a idea how this can be done with the current revision of PCem and other emulated machines such as VMware Player and VirtualBox?
- ppgrainbow
- Posts: 479
- Joined: Thu 04 Sep, 2014 7:03 am
- Contact:
Re: Networking discussion
Thank you so much for the help. I heard that LSL.COM and TCPIP.EXE are huge memory hogs when trying to load the network drivers to use under DESQview/X.amadama wrote:Yes, I have it running it in QEMU, MAME and on a real machine.
See my posting on BetaArchive:
http://www.betaarchive.com/forum/viewtopic.php?t=28286
Some instruction on how to install in MESS (not from me):
http://forums.bannister.org/ubbthreads. ... mber=86865
(you will need to adapt the network install as at the time of writing the 3com emulation was used in these intructions)
Can these drivers be loaded and unloaded? If so, can it be done by modifying the DVX.BAT file?
The AMI WinBIOS 486 66 MHz machine for example has 612 KB of free memory under 1 MB and 598 KB of memory used as the largest executable size.
Last edited by ppgrainbow on Tue 08 Sep, 2015 10:26 pm, edited 1 time in total.
- ppgrainbow
- Posts: 479
- Joined: Thu 04 Sep, 2014 7:03 am
- Contact:
Re: Networking discussion
Thank you for the link. Because I installed DESQview/X without any networking, I will have to install networking first before I can use it.neozeed wrote:Ive done it once before. it was a little underwhelming. Maybe it would be cool before linux, but it needing quemm and novel TCP/IP.ppgrainbow wrote:*yawn*
Has anyone tried running DESQview/X with the NE2000 network card? According to the ToastyTech article on DESQview/X, you can run applications remotely!
Anyone have a idea how this can be done with the current revision of PCem and other emulated machines such as VMware Player and VirtualBox?
Re: Networking discussion
neozeed's writeup is very good. I would add a few things:
Install Windows 3.1 before installing Desqview/X (dvx will recognize it and configure itself for use with Windows).
Haven't tried it out in PCem, but in QEMU and VMWare qemm will bomb out during the aggressive memory optimization parts thus leaving you with a lot less ram available.
You may need to use an older version of ctmouse.
Arachne will probably not work in DOS session.
Good luck and have fun.
Install Windows 3.1 before installing Desqview/X (dvx will recognize it and configure itself for use with Windows).
Haven't tried it out in PCem, but in QEMU and VMWare qemm will bomb out during the aggressive memory optimization parts thus leaving you with a lot less ram available.
You may need to use an older version of ctmouse.
Arachne will probably not work in DOS session.
Good luck and have fun.
- ppgrainbow
- Posts: 479
- Joined: Thu 04 Sep, 2014 7:03 am
- Contact:
Re: Networking discussion
QEMM memory optimisation does work in PCem. I don't know if QEMM optimisation has been tested in Bochs either.amadama wrote:neozeed's writeup is very good. I would add a few things:
Install Windows 3.1 before installing Desqview/X (dvx will recognize it and configure itself for use with Windows).
Haven't tried it out in PCem, but in QEMU and VMWare qemm will bomb out during the aggressive memory optimization parts thus leaving you with a lot less ram available.
You may need to use an older version of ctmouse.
Arachne will probably not work in DOS session.
Good luck and have fun.
Windows for Workgroups 3.11 does not work in DESQview/X, because WFW 3.11 removed Standard Mode support and required a 386-based PC to run.
Why will Arachne never work in a DESQview-based MS-DOS session, btw?
Re: Networking discussion
I did not say WfW 3.11, I said Windows 3.1. What does Bochs have anything to do here?
Arachne requires it's own packet driver which DVX will not provide to a DOS session. People have gotten Arachne working by using two NICs in a real machine with one dedicated to Arachne.
Arachne requires it's own packet driver which DVX will not provide to a DOS session. People have gotten Arachne working by using two NICs in a real machine with one dedicated to Arachne.
- ppgrainbow
- Posts: 479
- Joined: Thu 04 Sep, 2014 7:03 am
- Contact:
Re: Networking discussion
Oh, okay. I don't think that no one has tested Bochs.amadama wrote:I did not say WfW 3.11, I said Windows 3.1. What does Bochs have anything to do here?
Arachne requires it's own packet driver which DVX will not provide to a DOS session. People have gotten Arachne working by using two NICs in a real machine with one dedicated to Arachne.
As for DVX, I don't think that you'll be able to achieve more than 500 KB in a DVX-based MS-DOS session without having to optimise memory using QEMM and including a lot of UMB address segments.
Re: Networking discussion
Closest thing to that is that I did have an OS/2 machine with one NIC for Novell traffic, and another for TCP/IP.amadama wrote: Arachne requires it's own packet driver which DVX will not provide to a DOS session. People have gotten Arachne working by using two NICs in a real machine with one dedicated to Arachne.
That almost makes me want to try Novell Netware on OS/2, but it's such a bear to fight I don't think it'll be worth the war.
- ppgrainbow
- Posts: 479
- Joined: Thu 04 Sep, 2014 7:03 am
- Contact:
Re: Networking discussion
I've noticed that whenever I start PCem (the debugger version renamed as PCem.exe), the slirplog.txt file gets created everywhere.
For example I have the disk images when I start the AMI 386 clone machine inside D:\PCem\disks\ami386 subdirectory, the slirplog.txt file gets created in that sub directory.
I'm wondering if there is a way to fix some of the issues to a point where the slirplog.txt file always remains in the directory where I start PCem and not anyplace else.
I also noticed that in the slirplog.txt, it contains the lines, "Slirp Cockatrice special". I'm wondering if that line could be changed to "PCem SLiRP".
Also, would it be better to add the ability to configure network options in the PCem dialog, including the option to either use SLiRP or WinPcap based networking?
I mean, since networking support isn't going to make it in v10, I'm guessing that it might make in in v10.1. :p
For example I have the disk images when I start the AMI 386 clone machine inside D:\PCem\disks\ami386 subdirectory, the slirplog.txt file gets created in that sub directory.
I'm wondering if there is a way to fix some of the issues to a point where the slirplog.txt file always remains in the directory where I start PCem and not anyplace else.
I also noticed that in the slirplog.txt, it contains the lines, "Slirp Cockatrice special". I'm wondering if that line could be changed to "PCem SLiRP".
Also, would it be better to add the ability to configure network options in the PCem dialog, including the option to either use SLiRP or WinPcap based networking?
I mean, since networking support isn't going to make it in v10, I'm guessing that it might make in in v10.1. :p
Re: Networking discussion
The log file opens where you start the exe.ppgrainbow wrote:I've noticed that whenever I start PCem (the debugger version renamed as PCem.exe), the slirplog.txt file gets created everywhere.
For example I have the disk images when I start the AMI 386 clone machine inside D:\PCem\disks\ami386 subdirectory, the slirplog.txt file gets created in that sub directory.
I'm wondering if there is a way to fix some of the issues to a point where the slirplog.txt file always remains in the directory where I start PCem and not anyplace else.
I also noticed that in the slirplog.txt, it contains the lines, "Slirp Cockatrice special". I'm wondering if that line could be changed to "PCem SLiRP".
Also, would it be better to add the ability to configure network options in the PCem dialog, including the option to either use SLiRP or WinPcap based networking?
I mean, since networking support isn't going to make it in v10, I'm guessing that it might make in in v10.1. :p
Code: Select all
int slirp_init(void)
{
#ifdef SLIRP_DEBUG
// debug_init("/tmp/slirp.log", DEBUG_DEFAULT);
// debug_init("slirplog.txt",DEBUG_DEFAULT);
debug_init("slirplog.txt",DBG_CALL);
Code: Select all
void
debug_init(file, dbg)
char *file;
int dbg;
{
/* Close the old debugging file */
if (dfd)
fclose(dfd);
dfd = fopen(file,"w");
Even PCem does it.
Code: Select all
FILE *pclogf;
void pclog(const char *format, ...)
{
#ifndef RELEASE_BUILD
char buf[1024];
//return;
if (!pclogf)
pclogf=fopen("pclog.txt","wt");
Well this slirp code did come from
Code: Select all
Cockatrice
Code: Select all
Qemu
If anything, it's more so my fork that I've renamed a bunch of stuff so it doesn't collide with local TCP/IP symbols, and a few fixes I found while getting Internet Explorer 3 & 4 running on MacOS. I'll re-use it again in Dynamips as I add a SLiRP module for natting IN/OUT of virtual networks.
Maybe I should give it it's own name, make it a DLL. I guess.
Re: Networking discussion
Oh yeah, before I get new build based on build 347.
- ppgrainbow
- Posts: 479
- Joined: Thu 04 Sep, 2014 7:03 am
- Contact:
Re: Networking discussion
Thanks for the update!neozeed wrote:Oh yeah, before I get new build based on build 347.
- SarahWalker
- Site Admin
- Posts: 2054
- Joined: Thu 24 Apr, 2014 4:18 pm
Re: Networking discussion
What's the current status of this? Is it stable enough for me to look at merging it?
Re: Networking discussion
So i did a little experiment with the slirp version of PCEm.
I've set up pywb (https://github.com/ikreymer/pywb) to fetch archived pages from the Internet Archive at a fixed date.
Pywb acts as a HTTP proxy which is used by the browser running in PCem.
With this setup, you can browse the internets like it's 1998 all over again!
I've set up pywb (https://github.com/ikreymer/pywb) to fetch archived pages from the Internet Archive at a fixed date.
Pywb acts as a HTTP proxy which is used by the browser running in PCem.
With this setup, you can browse the internets like it's 1998 all over again!
Re: Networking discussion
any news on this thread?
Re: Networking discussion
As I said, I have taken Neozeed's work further and even added the first PCI network card, the RTL8029AS (also known as the NE2000 PCI), but I first want to get that working right before I am going to commit an official patch. I'm also going to have to add a way to list PCap devices in PCem settings.
Re: Networking discussion
I had to take an unexpected long trip and it's left me with no time for fun stuff.. I need to get someone to poke my dev box as I guess it's asleep.
The only good news is that I did score an i7 laptop. . And an older mac book, so I should be in a good build space soon.
Pulling the NIC list isn't too hard check that ethlist.c. .. it shouldn't be too hard to stitch the bits together. Also from a few other projects I've helped in there should be more slirp updates. And I'd love to see some ability to run more than one pcem with GNU bios components so we can add it into GNS3...
The only good news is that I did score an i7 laptop. . And an older mac book, so I should be in a good build space soon.
Pulling the NIC list isn't too hard check that ethlist.c. .. it shouldn't be too hard to stitch the bits together. Also from a few other projects I've helped in there should be more slirp updates. And I'd love to see some ability to run more than one pcem with GNU bios components so we can add it into GNS3...