On 31 Dec 2019 at 13:30, Eric Auer wrote: > > Hi! As the links got line-wrapped, here are the contents: > > > http://support.fccps.cz/download/adv/frr/FreeDos/zero_padded_pkt_dump.txt > > contains the following text: > > > # tcpdump -n -i tap0 > > 16:47:39.592071 00:00:00:00:00:00 > 00:00:00:00:00:00 Null Information, > > send seq 0, rcv seq 0, Flags [Command], length 2586 > > 0x0000: 0000 0000 0000 0000 0000 0000 0000 0000 ................ > [etc.] > > ...etc. The last row starts at 0x0a10 and contains 10 bytes. > The e-mail client in Windows that I'm using for mailing lists (Pegasus Mail) uses a fixed maximum line length. Which used to be a rule in the old days... That's why long URL's in message body get line-wrapped and that's why I prefer to attach text with longer lines as a separate file, where the formatting is not subject to the MUA's intelligent interventions...
> > http://support.fccps.cz/download/adv/frr/FreeDos/FreeDOS_QEMU_DHCP_hangs.jpg > > is a photograph (why not a screenshot?) of this text in QEMU: > It was just easier to take a photo. To take a screenshot, I'd probably have to install further software into the funny diskless client environment. > Defaulting to NIC found in slot 0x0002. > PCI\VEN_8086&DEV_1209&SUBSYS_11001AF4&REV_0F > > Permanent Node Address: 525400123456 > Current Node Address: 525400123456 > Configured Speed/Duplex: Auto > TransmitBuffers: 4 > ReceiveBuffers: 8 > > Microsoft DOS TCP/IP Protocol Driver 1.0a > Copyright (c) Microsoft Corporation, 1991. All rights reserved. > Copyright (c) Hewlett-Packard Corporation, 1985-1991. All rights reserved. > Copyright (c) 3Com Corporation, 1985-1991. All rights reserved. > Microsoft DOS TCP/IP NEMM Driver 1.0 > MAC/DIS to Packet Driver converter loaded. Version 1.19 > Copyrifgt 1991 FTP Software, Inc. All rights reserved. > Portions Copyright(c) 2000-2004 Symantec Corporation > > The command completed successfully. > - Starting netbind > MS-DOS LAN Manager v2.1 Netbind > - Starting umb > - Starting tcp/ip > Initializing TCP/IP via DHCP.... > Ohh amazing, it must've taken you quite some effort to type it all. I didn't bother, as it's just a log of a few drivers starting up... > (and that is where QEMU stops - maybe waiting for DHCP responses?) > Yes, that's where the TCP/IP stack (TCPTSR.EXE?) should report "okay, got an IP address" and then some messages about Samba logon. Again Windows or Linux just start up and start working with the emulated NIC, their DHCP queries succeed etc. Just in FreeDOS with JEMMEX or HimemX, I get the DHCP queries zero-padded on the outside - while the drivers seem to be otherwise happy with the emulated network hardware they should cater for. I have a faint awareness of PCI IOMEM mapping to the CPU address space on bare metal, I know how to ask for it in Linux driver source code and I seem to recall seeing that in DPMI as well, but I know next to nothing about how this could interact with a hypervisor (QEMU+KVM) and in what ways the DOS+DPMI environment (or DPMI-less, maybe) can differ from a full-fledged modern OS at the guest side... Maybe Japheth would have a clue, but the last update of his memory manager is several years old... And the version of QEMU that I'm using is not very new, either - if that should matter. Frank _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
