Re: [Freedos-user] networking over 86box
Le Wed, 24 Apr 2024 16:05:10 -0400 Brandon Taylor via Freedos-user a écrit > My apologies for the confusion. I know FreeDOS has internet capability, but > not on 86Box, since FreeDOS for some reason treats 86Box as if it were a > real computer. > > GetOutlook for Android > From: Robert Riebisch via Freedos-user freedos-user@lists.sourceforge.net> > Sent: Wednesday, April 24, 2024 2:04:17 PM > To: freedos-user@lists.sourceforge.net freedos-user@lists.sourceforge.net> > Cc: Robert Riebisch r...@bttr-software.de> > Subject: Re: [Freedos-user] Dial-up emulation? > Hi Brandon, > > > Since FreeDOS doesn't support physical network hardware (even if it's > > emulated in a program like PCem or 86Box), I figure there's no way > > FreeDOS is gonna be able to connect to the Internet, right? Well... Frankly, using networking over 86box seems harder than on QEMU... where I have posted some weeks ago the line I use to have the networking emulated. You would need to read: https://86box.readthedocs.io/en/latest/hardware/network.html that shows that the default is to drop all network information. Slirp seems easier to select but not really what you want (because it seems to request a program to connect to internet) pCap seems what you would want... but then need some additional program than 86box. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking on UTM
Docs ( https://docs.getutm.app/settings-qemu/devices/network/network/#hardware) say that the emulated network device is a “virtio-net-pci” device. Docs also mention that the OS will require a driver for it. virtio is a common interface for modern Linux, Windows, and I think Mac OS VMs. For DOS, you’ll need to find a packet driver for it. I’m not aware of any. On Fri, Oct 27, 2023 at 6:33 AM Knedlik via Freedos-user < freedos-user@lists.sourceforge.net> wrote: > Hello there! > > I’ve been venturing a bit into DOS world once again just for run, and it > seems that my UTM virtual machine doesn’t automatically set up networking. > I installed the networking packages from FDIMPLES, but when I boot the > machine, I get „QEMU network detected“ and right after that „Physical > hardware networking is not supported at this time“… > > Does anyone have an idea on how to solve this? I’m fine using FreeDOS > without networking, but having to download stuff onto my Mac and then stick > it into the VM can be a painful process… > > Thanks in advance, > -Knedlik > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking FreeDOS 1.3 on QEMU
I've found that the ADM PCNet adaptor in QEMU (-device pcnet) with the matching DOS drivers work well under FreeDOS. I wasn't able to get any of the other QEMU emulated ethernet devices to work properly under DOS. I spent a lot of time fighting with the Intel adaptors - it seems the QEMU emulated Intel adaptors are pretty new, and the Intel DOS drivers are pretty old. I finally gave up and went back to AMD PCNet. I was able to use NDIS2 drivers with MSNET (using TCP/IP bindings and talking to a Samba server) as well as packet drivers with the DOS based TCP stacks. Also works well with etherdfs. Hopefully that saves you some time (I spent a lot of time troubleshooting these adaptors on the DOS side.) - Darrin On Tue, Sep 6, 2022 at 3:41 PM Jerome Shidel wrote: > Hi, > > > On Sep 6, 2022, at 11:43 AM, Phil Reynolds < > phil-free...@tinsleyviaduct.com> wrote: > > > > I had FreeDOS 1.2 working quite nicely, networking included, on qemu, > > but I am lost as to (a) how I originally achieved it (b) how I might do > > likewise with 1.3 - is there any specific documentation I can follow? > > By default during the boot process, FDAUTO runs "FDNET.BAT start” > > The “start” option tells FDNET to only run on known compatible virtual > machines (ie. VirtualBox and VMware). > > You will need to configure QEMU with an appropriate network card. I don’t > use QEMU much to run DOS. Can’t help you there. > > Then if it is one of the Network cards supported by FDNET, you can just > remove the “start” option. > > Otherwise, you could create a custom batch called FDNETPD.BAT that knows > how to configure your packet driver. You would then place both your custom > FDNETPD.BAT and Packet Driver in the FDNET directory. Then running FDNET > should bring up your networking. This prevents the need for customizing the > FDCONFIG and/or FDAUTO every time you reinstall, upgrade the OS or update > packages. > > Hope that helps at least a little. > > :-) > > Jerome > > > > > -- > > Phil Reynolds > > mail: phil-free...@tinsleyviaduct.com > > Web: http://phil.tinsleyviaduct.com/ > > > > > > ___ > > Freedos-user mailing list > > Freedos-user@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/freedos-user > > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking FreeDOS 1.3 on QEMU
Hi, > On Sep 6, 2022, at 11:43 AM, Phil Reynolds > wrote: > > I had FreeDOS 1.2 working quite nicely, networking included, on qemu, > but I am lost as to (a) how I originally achieved it (b) how I might do > likewise with 1.3 - is there any specific documentation I can follow? By default during the boot process, FDAUTO runs "FDNET.BAT start” The “start” option tells FDNET to only run on known compatible virtual machines (ie. VirtualBox and VMware). You will need to configure QEMU with an appropriate network card. I don’t use QEMU much to run DOS. Can’t help you there. Then if it is one of the Network cards supported by FDNET, you can just remove the “start” option. Otherwise, you could create a custom batch called FDNETPD.BAT that knows how to configure your packet driver. You would then place both your custom FDNETPD.BAT and Packet Driver in the FDNET directory. Then running FDNET should bring up your networking. This prevents the need for customizing the FDCONFIG and/or FDAUTO every time you reinstall, upgrade the OS or update packages. Hope that helps at least a little. :-) Jerome > > -- > Phil Reynolds > mail: phil-free...@tinsleyviaduct.com > Web: http://phil.tinsleyviaduct.com/ > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] networking/wifi
Long time ago, I had an orinoco card that was 802.11b that was supposed to work with DOS. Could never get it to work, eventually threw it out in frustration. Some very good and interesting suggestions have been made. However, I believe the cheapest/easiest may be a simple wireless bridge. An old tplink wr841n can make a good bridge. For my laptop, I bought an old IOGear GWU627. (I have a handful of small bridges - that one boot the fastest) Plug it in the ethernet, usb for power, duct tape it together and there you have it: Wireless DOS with Lynx. (or links, or telnet, or ftp, ect) On Fri, Mar 19, 2021 at 11:55 PM Louis Santillan wrote: > IMO, ISA is a better option for truly vintage machines. I think if > someone combined the ideas PiModem/Wifi232, Pi Virtual Floppy [0], and > ISA8019 [2] (which is an NE2000!), then that would be the ideal. An ISA > card powered by a Pi Zero W that could emulate a Floppy/HDD/CD-ROM/DVD-ROM > and provide 1000BaseT Ethernet and/or WiFi would be a super card. Doing > BaseT or WiFi transparently in SW like Dr. Baker did showed could be done > in the Pi Virtual Floppy would be awesome. > > [0] > https://www.smbaker.com/raspberry-pi-virtual-floppy-for-isa-pc-xtat-computers > [1] https://github.com/Manawyrm/ISA8019 > > On Fri, Mar 19, 2021 at 2:03 PM wrote: > >> Hi! Eric >> as for the wi-fi I have solved the problem in an empirical way: I have >> long bought >> >> a TP-Link TPL-MR3020 mini router which detects available wireless >> networks and which >> >> has an ethernet port to which I can connect my laptop . >> >> It also has the possibility to connect - on the move - an internet key. >> >> The only problem is that to configure it and to detect the networks I >> need a win or linux browser because with LINKS - which I use in dos -it is >> obviously not possible. >> >> regards >> andrea >> >> Il 18.03.2021 13:55 Eric Auer ha scritto: >> >> Hi! >> >> Am just wondering if this is the current status, or some old comment: >> "Wireless devices connected via USB can not yet be used with FreeDOS." ( >> http://freedos.sourceforge.net/wiki/index.php/WiFi) >> >> This meant "USB dongles which serve as WiFi or Bluetooth modems >> have no DOS drivers" and is still the case as far as I know: >> >> In rare cases, DOS drivers for PCMCIA WiFi modems have existed. >> For current computers, the recommended workaround would be to >> use an external WiFi to LAN converter, as it is much easier to >> find LAN style wired network drivers for DOS. >> >> Similarily, I would expect Bluetooth to serial port converter >> modules to work reasonably well with DOS: Those tend to have a >> modem-style command system to control them and actually serial >> interfaces between microcontrollers and Bluetooth modules are >> widespread. It is slow enough to be useful even if not connected >> by for example a faster SPI bus. Of course you would still need >> a converter for RS232 signal levels. Combined products may exist. >> Also, DOS users tend to have modem command skills and dialup tools. >> >> Maybe people here could talk about their experiences with specific >> brands of WiFi LAN gateways or Bluetooth RS232 adapters in DOS :-) >> >> Regards, Eric >> >> >> >> ___ >> Freedos-user mailing >> listFreedos-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/freedos-user >> >> >> >> >> Con Tiscali Mobile Smart 30 4G hai minuti illimitati, 100 SMS e 30 Giga >> in 4G a soli 8,99€ al mese. http://tisca.li/smart30 >> >> ___ >> Freedos-user mailing list >> Freedos-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/freedos-user >> > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] networking/wifi
IMO, ISA is a better option for truly vintage machines. I think if someone combined the ideas PiModem/Wifi232, Pi Virtual Floppy [0], and ISA8019 [2] (which is an NE2000!), then that would be the ideal. An ISA card powered by a Pi Zero W that could emulate a Floppy/HDD/CD-ROM/DVD-ROM and provide 1000BaseT Ethernet and/or WiFi would be a super card. Doing BaseT or WiFi transparently in SW like Dr. Baker did showed could be done in the Pi Virtual Floppy would be awesome. [0] https://www.smbaker.com/raspberry-pi-virtual-floppy-for-isa-pc-xtat-computers [1] https://github.com/Manawyrm/ISA8019 On Fri, Mar 19, 2021 at 2:03 PM wrote: > Hi! Eric > as for the wi-fi I have solved the problem in an empirical way: I have > long bought > > a TP-Link TPL-MR3020 mini router which detects available wireless > networks and which > > has an ethernet port to which I can connect my laptop . > > It also has the possibility to connect - on the move - an internet key. > > The only problem is that to configure it and to detect the networks I need > a win or linux browser because with LINKS - which I use in dos -it is > obviously not possible. > > regards > andrea > > Il 18.03.2021 13:55 Eric Auer ha scritto: > > Hi! > > Am just wondering if this is the current status, or some old comment: > "Wireless devices connected via USB can not yet be used with FreeDOS." ( > http://freedos.sourceforge.net/wiki/index.php/WiFi) > > This meant "USB dongles which serve as WiFi or Bluetooth modems > have no DOS drivers" and is still the case as far as I know: > > In rare cases, DOS drivers for PCMCIA WiFi modems have existed. > For current computers, the recommended workaround would be to > use an external WiFi to LAN converter, as it is much easier to > find LAN style wired network drivers for DOS. > > Similarily, I would expect Bluetooth to serial port converter > modules to work reasonably well with DOS: Those tend to have a > modem-style command system to control them and actually serial > interfaces between microcontrollers and Bluetooth modules are > widespread. It is slow enough to be useful even if not connected > by for example a faster SPI bus. Of course you would still need > a converter for RS232 signal levels. Combined products may exist. > Also, DOS users tend to have modem command skills and dialup tools. > > Maybe people here could talk about their experiences with specific > brands of WiFi LAN gateways or Bluetooth RS232 adapters in DOS :-) > > Regards, Eric > > > > ___ > Freedos-user mailing > listFreedos-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/freedos-user > > > > > Con Tiscali Mobile Smart 30 4G hai minuti illimitati, 100 SMS e 30 Giga in > 4G a soli 8,99€ al mese. http://tisca.li/smart30 > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] networking/wifi
Hi! Eric as for the wi-fi I have solved the problem in an empirical way: I have long bought a TP-Link TPL-MR3020 mini router which detects available wireless networks and which has an ethernet port to which I can connect my laptop . It also has the possibility to connect - on the move - an internet key. The only problem is that to configure it and to detect the networks I need a win or linux browser because with LINKS - which I use in dos -it is obviously not possible. regards andrea Il 18.03.2021 13:55 Eric Auer ha scritto: > Hi! > >> Am just wondering if this is the current status, or some old comment: "Wireless devices connected via USB can not yet be used with FreeDOS." (http://freedos.sourceforge.net/wiki/index.php/WiFi [1]) > > This meant "USB dongles which serve as WiFi or Bluetooth modems > have no DOS drivers" and is still the case as far as I know: > > In rare cases, DOS drivers for PCMCIA WiFi modems have existed. > For current computers, the recommended workaround would be to > use an external WiFi to LAN converter, as it is much easier to > find LAN style wired network drivers for DOS. > > Similarily, I would expect Bluetooth to serial port converter > modules to work reasonably well with DOS: Those tend to have a > modem-style command system to control them and actually serial > interfaces between microcontrollers and Bluetooth modules are > widespread. It is slow enough to be useful even if not connected > by for example a faster SPI bus. Of course you would still need > a converter for RS232 signal levels. Combined products may exist. > Also, DOS users tend to have modem command skills and dialup tools. > > Maybe people here could talk about their experiences with specific > brands of WiFi LAN gateways or Bluetooth RS232 adapters in DOS :-) > > Regards, Eric > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net [2] > https://lists.sourceforge.net/lists/listinfo/freedos-user [3] Con Tiscali Mobile Smart 30 4G hai minuti illimitati, 100 SMS e 30 Giga in 4G a soli 8,99€ al mese. http://tisca.li/smart30 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] networking/wifi
Thanks for the links, Louis :-) While the price could be a lot lower, the https://www.cbmstuff.com/proddetail.php?prod=WiModem232 https://www.cbmstuff.com/proddetail.php?prod=WiModem232=all mentioned on one of the pages is pretty similar to what I had in mind: some WiFi controller plus a RS232 level shifter plus good firmware = fake WiFi dial-up modem :-) AND it has everything pre-installed, with WPS quick setup. There seem to be several websites about tinkering with for example a Raspberry Pi and USB serial port adapter, using the tcpser software. One randome exammple for that: https://www.insentricity.com/a.cl/215/putting-your-retro-computer-on-the-line The WiFi232 page http://biosrhythm.com/?page_id=1453 says it is sold out - the concept seems a lot like WiModem232, but with a more bulky non-SMD circuit board for WiFi232. As WiFi232 is ESP8266 based: Arduino-Raspberry-et-al Stores sell you stuff like Waveshare RS232 (SUBD9, header, SP3232E) for 5 Euro and ESP8266 or ESP32 modules on boards with pin headers for 5 to 10 Euro (NodeMCU v2 with Lua, "ESP-01S" or Olimex MOD-WIFI-ESP8266, Olimex ESP32-DevKit-LiPo, NodeMCU-32S or similar) you could easily roll your own if you have access to the right firmware: Some jumper wires or a breadboard can link both ingredients and the ESP32 or ESP8288 listed above have micro USB sockets for power and for uploading firmware. That lets you BUILD a WiFi RS232 modem for less than 20 USD, not counting cables and case. Without even having to solder! As long as software is made? Arduino does support ESP chips. Cheers, Eric ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] networking/wifi
DOS did networking a lot better with ISA and some PCI NICS. WiFi came after DOS was no longer being developed. There might be some 900MHz WaveLAN things that work for DOS if the point is to make a machine connected wirelessly. If the machine has serial you might consider a Wifi232[0] or one of the Pi Zero W[1][2] based options. [0] http://biosrhythm.com/?page_id=1453 [1] http://podsix.org/articles/pimodem/ [2] https://mygpslostitself.blogspot.com/2017/07/raspberry-pi-zero-w-serial-modem.html On Thu, Mar 18, 2021 at 6:41 AM Eric Auer wrote: > > Hi! To do some additional name-dropping on the DOS WiFi topic here: > > > https://www.olimex.com/Products/IoT/ESP32/ESP32-GATEWAY/open-source-hardware > > > https://www.hackster.io/techbase_group/arduino-esp32-serial-port-to-tcp-converter-via-wifi-66d341 > > https://github.com/martin-ger/esp_wifi_repeater/blob/master/README.md > > In short, you can do interesting things with cheap WiFi (and Bluetooth) > enabled controller modules, including things which involve LAN or RS232, > so there might be some "turn some modules for a total of 10-25 USD into > a connector between WiFi and LAN or serial port" project out there for > those who prefer tinkering over ready to use brand devices :-) > > ESP32 are 4 USD 2-core controller modules with WiFi, Bluetooth and more > interfaces, 520 kB RAM, more compute power than your 386 PC. But just > marketed as wireless controller, less as microcontroller. "ESP8266++" > Maybe fast enough to simulate a PC XT, with MDA graphics, in software. > > Cheers, Eric > > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] networking/wifi
Hi! To do some additional name-dropping on the DOS WiFi topic here: https://www.olimex.com/Products/IoT/ESP32/ESP32-GATEWAY/open-source-hardware https://www.hackster.io/techbase_group/arduino-esp32-serial-port-to-tcp-converter-via-wifi-66d341 https://github.com/martin-ger/esp_wifi_repeater/blob/master/README.md In short, you can do interesting things with cheap WiFi (and Bluetooth) enabled controller modules, including things which involve LAN or RS232, so there might be some "turn some modules for a total of 10-25 USD into a connector between WiFi and LAN or serial port" project out there for those who prefer tinkering over ready to use brand devices :-) ESP32 are 4 USD 2-core controller modules with WiFi, Bluetooth and more interfaces, 520 kB RAM, more compute power than your 386 PC. But just marketed as wireless controller, less as microcontroller. "ESP8266++" Maybe fast enough to simulate a PC XT, with MDA graphics, in software. Cheers, Eric ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] networking/wifi
Hi! > Am just wondering if this is the current status, or some old comment: > > "Wireless devices connected via USB can not yet be used with FreeDOS." > > (http://freedos.sourceforge.net/wiki/index.php/WiFi) This meant "USB dongles which serve as WiFi or Bluetooth modems have no DOS drivers" and is still the case as far as I know: In rare cases, DOS drivers for PCMCIA WiFi modems have existed. For current computers, the recommended workaround would be to use an external WiFi to LAN converter, as it is much easier to find LAN style wired network drivers for DOS. Similarily, I would expect Bluetooth to serial port converter modules to work reasonably well with DOS: Those tend to have a modem-style command system to control them and actually serial interfaces between microcontrollers and Bluetooth modules are widespread. It is slow enough to be useful even if not connected by for example a faster SPI bus. Of course you would still need a converter for RS232 signal levels. Combined products may exist. Also, DOS users tend to have modem command skills and dialup tools. Maybe people here could talk about their experiences with specific brands of WiFi LAN gateways or Bluetooth RS232 adapters in DOS :-) Regards, Eric ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] networking/wifi
Simon, I can read from a USB stick without any extra tricks, as long as it is inserted before booting (which usually means I have to make sure the bios is set to boot from disk 1st; I find it easier to write the files to the Freedos disk from inside Windows, if I need to do that). However, I'm not sure this says anything either way about networking. /Tomas On Thu, 18 Mar 2021 11:43:19 +0100, Šimon Dobeš wrote: > Hello, > Well I tried to use USB with FreeDOS. You can use USB with FreeDOS but > you need to do some things. > 1st: You need to unzip FreeDOS USB installer to USB that you wnat to > use. > 2nd: Create special folder for files you want to transfer. E.G.: > Folder named TRANSFER > 3rd: Boot from USB. > 4th: Cancel installation. > 5th: Your USB is ready to go. > Note: USB is C: and you main hard drive is D: or sometimes even E: > > I hope this will work, > Šimon Dobeš ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] networking/wifi
Hello, Well I tried to use USB with FreeDOS. You can use USB with FreeDOS but you need to do some things. 1st: You need to unzip FreeDOS USB installer to USB that you wnat to use. 2nd: Create special folder for files you want to transfer. E.G.: Folder named TRANSFER 3rd: Boot from USB. 4th: Cancel installation. 5th: Your USB is ready to go. Note: USB is C: and you main hard drive is D: or sometimes even E: I hope this will work, Šimon Dobeš -- Pôvodná správa -- Od: "Tomas By" Komu: "Discussion and general questions about FreeDOS." Odoslané: 18. 3. 2021 10:27:13 Predmet: [Freedos-user] networking/wifi Hi all, Am just wondering if this is the current status, or some old comment: "Wireless devices connected via USB can not yet be used with FreeDOS." (http://freedos.sourceforge.net/wiki/index.php/WiFi) /Tomas ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking without ethernet?
I'm interested in this approach, but I'm finding it hard to find documentation and software. From what I've heard so far, it seems using the on-board modem will be more of a hassle than just using serial or parallel to connect to something else with ethernet. I'd like to stick with free/libre software wherever possible, and I'm not opposed to writing my own software to accomplish this either; I just need documentation. All the documentation I can find seems to make too many assumptions about my knowledge (i.e. "Just use " as if I have it and know how to use it already). If the users on this list can work together and get me the pieces I need to make a working setup for this, I'd be more than happy to compile it all into a comprehensive how-to document for future users. Happy Hacking, David E. McMackins II Supporting Member, Electronic Frontier Foundation (#2296972) Associate Member, Free Software Foundation (#12889) www.mcmackins.org www.delwink.com www.eff.org www.gnu.org www.fsf.org On 07/10/2018 03:11 PM, geneb wrote: >> On Jul 10, 2018, 1:23 PM, David McMackins wrote: >> >>> Even if I did, that doesn't answer my question. Even if I get connected >>> to dial-up, will TCP/IP applications still work, or will they complain >>> about drivers since they are trying to access a NIC? >>> > > David, you might be well served by looking into SLIP & PPP options for > DOS. Something like Trumpet WinSock, but for DOS. > > You could configure a Raspberry Pi as a PPP or SLIP host and connect to > it via a null modem cable. > > g. > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking without ethernet?
Or DOSPPP. On Tue, Jul 10, 2018 at 3:32 PM Louis Santillan wrote: > You could also use something like EPPPD and Arachne includes a dialer > packet driver as well (might even be EPPPD). > > On Tue, Jul 10, 2018 at 3:13 PM geneb wrote: > >> > On Jul 10, 2018, 1:23 PM, David McMackins wrote: >> > >> >> Even if I did, that doesn't answer my question. Even if I get connected >> >> to dial-up, will TCP/IP applications still work, or will they complain >> >> about drivers since they are trying to access a NIC? >> >> >> >> David, you might be well served by looking into SLIP & PPP options for >> DOS. Something like Trumpet WinSock, but for DOS. >> >> You could configure a Raspberry Pi as a PPP or SLIP host and connect to >> it >> via a null modem cable. >> >> g. >> >> -- >> Proud owner of F-15C 80-0007 >> http://www.f15sim.com - The only one of its kind. >> http://www.diy-cockpits.org/coll - Go Collimated or Go Home. >> Some people collect things for a hobby. Geeks collect hobbies. >> >> ScarletDME - The red hot Data Management Environment >> A Multi-Value database for the masses, not the classes. >> http://scarlet.deltasoft.com - Get it _today_! >> >> >> -- >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> ___ >> Freedos-user mailing list >> Freedos-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/freedos-user >> > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking without ethernet?
You could also use something like EPPPD and Arachne includes a dialer packet driver as well (might even be EPPPD). On Tue, Jul 10, 2018 at 3:13 PM geneb wrote: > > On Jul 10, 2018, 1:23 PM, David McMackins wrote: > > > >> Even if I did, that doesn't answer my question. Even if I get connected > >> to dial-up, will TCP/IP applications still work, or will they complain > >> about drivers since they are trying to access a NIC? > >> > > David, you might be well served by looking into SLIP & PPP options for > DOS. Something like Trumpet WinSock, but for DOS. > > You could configure a Raspberry Pi as a PPP or SLIP host and connect to it > via a null modem cable. > > g. > > -- > Proud owner of F-15C 80-0007 > http://www.f15sim.com - The only one of its kind. > http://www.diy-cockpits.org/coll - Go Collimated or Go Home. > Some people collect things for a hobby. Geeks collect hobbies. > > ScarletDME - The red hot Data Management Environment > A Multi-Value database for the masses, not the classes. > http://scarlet.deltasoft.com - Get it _today_! > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking without ethernet?
On Jul 10, 2018, 1:23 PM, David McMackins wrote: Even if I did, that doesn't answer my question. Even if I get connected to dial-up, will TCP/IP applications still work, or will they complain about drivers since they are trying to access a NIC? David, you might be well served by looking into SLIP & PPP options for DOS. Something like Trumpet WinSock, but for DOS. You could configure a Raspberry Pi as a PPP or SLIP host and connect to it via a null modem cable. g. -- Proud owner of F-15C 80-0007 http://www.f15sim.com - The only one of its kind. http://www.diy-cockpits.org/coll - Go Collimated or Go Home. Some people collect things for a hobby. Geeks collect hobbies. ScarletDME - The red hot Data Management Environment A Multi-Value database for the masses, not the classes. http://scarlet.deltasoft.com - Get it _today_! -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking without ethernet?
I understand this. I guess my question was really: where can I get a packet driver that will communicate over my phone line instead of a typical NIC? Happy Hacking, David E. McMackins II Supporting Member, Electronic Frontier Foundation (#2296972) Associate Member, Free Software Foundation (#12889) www.mcmackins.org www.delwink.com www.eff.org www.gnu.org www.fsf.org On 2018-07-10 14:20, Mercury Thirteen via Freedos-user wrote: Afaik, TCP/IP interfaces to a packet driver, which then works directly with the NIC. It shouldn't matter over which medium you're ultimately communicating, as long as it presents the packet interface which TCP/IP expects. Sent from ProtonMail mobile Original Message On Jul 10, 2018, 1:23 PM, David McMackins < cont...@mcmackins.org> wrote: Even if I did, that doesn't answer my question. Even if I get connected to dial-up, will TCP/IP applications still work, or will they complain about drivers since they are trying to access a NIC? Happy Hacking, David E. McMackins II Supporting Member, Electronic Frontier Foundation (#2296972) Associate Member, Free Software Foundation (#12889) www.mcmackins.org [1]">www.mcmackins.org [1] www.delwink.com [2]">www.delwink.com [2] www.eff.org [3]">www.eff.org [3] www.gnu.org [4]">www.gnu.org [4] www.fsf.org [5]">www.fsf.org [5] On 2018-07-10 12:17, Louis Santillan wrote: Have you tried setting up a Linux box as a dial-up server? [0] [0] https://www.howtoforge.com/linux_dialin_server [6]">https://www.howtoforge.com/linux_dialin_server [7] [8] On Mon, Jul 9, 2018 at 9:10 PM David McMackins wrote: I have a 1998 Sony Vaio running FreeDOS. This model did not include an ethernet controller (or wlan), but it does have an old modem in it. I've been going through the networking guide referred to by Rugxulo, and I got down to running NICSCAN.EXE only to realize *oops!* this computer doesn't even have an ethernet card. Supposing I could find a working phone line and dial-up service to connect the modem to, is there hope of using TCP/IP applications like wget over it using the software available to me? Happy Hacking, David E. McMackins II Supporting Member, Electronic Frontier Foundation (#2296972) Associate Member, Free Software Foundation (#12889) www.mcmackins.org [1]">www.mcmackins.org [1] [1] www.delwink.com [2]">www.delwink.com [2] [2] www.eff.org [3]">www.eff.org [3] [3] www.gnu.org [4]">www.gnu.org [4] [4] www.fsf.org [5]">www.fsf.org [5] [5] -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot [8]">http://sdm.link/slashdot [9]">http://sdm.link/slashdot [10]">http://sdm.link/slashdot [9]">http://sdm.link/slashdot [9]">http://sdm.link/slashdot [9]">http://sdm.link/slashdot [10]">http://sdm.link/slashdot [9] [6] ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user [11]">https://lists.sourceforge.net/lists/listinfo/freedos-user [12]">https://lists.sourceforge.net/lists/listinfo/freedos-user [13]">https://lists.sourceforge.net/lists/listinfo/freedos-user [12]">https://lists.sourceforge.net/lists/listinfo/freedos-user [12]">https://lists.sourceforge.net/lists/listinfo/freedos-user [12]">https://lists.sourceforge.net/lists/listinfo/freedos-user [13]">https://lists.sourceforge.net/lists/listinfo/freedos-user [12] [7] Links: -- [1] http://www.mcmackins.org [1]">www.mcmackins.org [1] [2] http://www.delwink.com [2]">www.delwink.com [2] [3] http://www.eff.org [3]">www.eff.org [3] [4] http://www.gnu.org [4]">www.gnu.org [4] [5] http://www.fsf.org [5]">www.fsf.org [5] [6] http://sdm.link/slashdot [8]">http://sdm.link/slashdot [9]">http://sdm.link/slashdot [10]">http://sdm.link/slashdot [9]">http://sdm.link/slashdot [9]">http://sdm.link/slashdot [9]">http://sdm.link/slashdot [10]">http://sdm.link/slashdot [9] [7] https://lists.sourceforge.net/lists/listinfo/freedos-user [11]">https://lists.sourceforge.net/lists/listinfo/freedos-user [12]">https://lists.sourceforge.net/lists/listinfo/freedos-user [13]">https://lists.sourceforge.net/lists/listinfo/freedos-user [12]">https://lists.sourceforge.net/lists/listinfo/freedos-user [12]">https://lists.sourceforge.net/lists/listinfo/freedos-user [12]">https://lists.sourceforge.net/lists/listinfo/freedos-user [13]">https://lists.sourceforge.net/lists/listinfo/freedos-user [12] [8] https://www.howtoforge.com/linux_dialin_server [6]">https://www.howtoforge.com/linux_dialin_server [7] -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot [8]">http://sdm.link/slashdot [9]">http://sdm.link/slashdot [10]">http://sdm.link/slashdot
Re: [Freedos-user] Networking without ethernet?
On Tue, 10 Jul 2018 14:58:01 -0400, dmccunney wrote: > Any chance of posting that somewhere that doesn't require a gopher > client to access it? You mean like http or whatever? Bleh. Where would be the fun then? Gopher-disabled people are free to use one of the few web proxies out there. FreeDOS also comes with a gopher client out of the box (gopherus). Anyway, here's a direct (and super-long) link through Floodgap's proxy: https://gopher.floodgap.com/gopher/gw.lite?gopher://gopher.viste.fr:70/1/ myinfobase/%3fdisp2017-03-05+plip+bridge Mateusz -- FreeDOS is present on the USENET, too! alt.os.free-dos -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking without ethernet?
Afaik, TCP/IP interfaces to a packet driver, which then works directly with the NIC. It shouldn't matter over which medium you're ultimately communicating, as long as it presents the packet interface which TCP/IP expects. Sent from ProtonMail mobile Original Message On Jul 10, 2018, 1:23 PM, David McMackins wrote: > Even if I did, that doesn't answer my question. Even if I get connected > to dial-up, will TCP/IP applications still work, or will they complain > about drivers since they are trying to access a NIC? > > Happy Hacking, > > David E. McMackins II > Supporting Member, Electronic Frontier Foundation (#2296972) > Associate Member, Free Software Foundation (#12889) > > [www.mcmackins.org](www.mcmackins.org [www.delwink.com]( href=)">www.delwink.com > [www.eff.org](www.eff.org [www.gnu.org](www.gnu.org > [www.fsf.org](www.fsf.org > > On 2018-07-10 12:17, Louis Santillan wrote: >> Have you tried setting up a Linux box as a dial-up server? [0] >> >> [0] [https://www.howtoforge.com/linux_dialin_server](> href=)">https://www.howtoforge.com/linux_dialin_server [8] >> >> On Mon, Jul 9, 2018 at 9:10 PM David McMackins >> wrote: >> >>> I have a 1998 Sony Vaio running FreeDOS. This model did not include >>> an >>> ethernet controller (or wlan), but it does have an old modem in it. >>> I've >>> been going through the networking guide referred to by Rugxulo, and >>> I >>> got down to running NICSCAN.EXE only to realize *oops!* this >>> computer >>> doesn't even have an ethernet card. >>> >>> Supposing I could find a working phone line and dial-up service to >>> connect the modem to, is there hope of using TCP/IP applications >>> like >>> wget over it using the software available to me? >>> >>> Happy Hacking, >>> >>> David E. McMackins II >>> Supporting Member, Electronic Frontier Foundation (#2296972) >>> Associate Member, Free Software Foundation (#12889) >>> >>> [www.mcmackins.org](www.mcmackins.org [1] [www.delwink.com](>> href=)">www.delwink.com [2] >>> [www.eff.org](www.eff.org [3] [www.gnu.org](>> href=)">www.gnu.org [4] [www.fsf.org](www.fsf.org [5] >>> >>> >> -- >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org! [http://sdm.link/slashdot](>> href=)">http://sdm.link/slashdot;>[http://sdm.link/slashdot](>> href=)">http://sdm.link/slashdot;>http://sdm.link/slashdot;>http://sdm.link/slashdot;>[http://sdm.link/slashdot](>> href=)">http://sdm.link/slashdot [6] >>> ___ >>> Freedos-user mailing list >>> Freedos-user@lists.sourceforge.net >>> [https://lists.sourceforge.net/lists/listinfo/freedos-user](>> href=)">https://lists.sourceforge.net/lists/listinfo/freedos-user;>[https://lists.sourceforge.net/lists/listinfo/freedos-user](>> >>> href=)">https://lists.sourceforge.net/lists/listinfo/freedos-user;>https://lists.sourceforge.net/lists/listinfo/freedos-user;>https://lists.sourceforge.net/lists/listinfo/freedos-user;>[https://lists.sourceforge.net/lists/listinfo/freedos-user](>> href=)">https://lists.sourceforge.net/lists/listinfo/freedos-user [7] >> >> >> Links: >> -- >> [1] http://[www.mcmackins.org](www.mcmackins.org >> [2] http://[www.delwink.com](www.delwink.com >> [3] http://[www.eff.org](www.eff.org >> [4] http://[www.gnu.org](www.gnu.org >> [5] http://[www.fsf.org](www.fsf.org >> [6] [http://sdm.link/slashdot](> href=)">http://sdm.link/slashdot;>[http://sdm.link/slashdot](> href=)">http://sdm.link/slashdot;>http://sdm.link/slashdot;>http://sdm.link/slashdot;>[http://sdm.link/slashdot](> href=)">http://sdm.link/slashdot >> [7] [https://lists.sourceforge.net/lists/listinfo/freedos-user](> href=)">https://lists.sourceforge.net/lists/listinfo/freedos-user;>[https://lists.sourceforge.net/lists/listinfo/freedos-user](> >> href=)">https://lists.sourceforge.net/lists/listinfo/freedos-user;>https://lists.sourceforge.net/lists/listinfo/freedos-user;>https://lists.sourceforge.net/lists/listinfo/freedos-user;>[https://lists.sourceforge.net/lists/listinfo/freedos-user](> href=)">https://lists.sourceforge.net/lists/listinfo/freedos-user >> [8] [https://www.howtoforge.com/linux_dialin_server](> href=)">https://www.howtoforge.com/linux_dialin_server >> >> -- >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! [http://sdm.link/slashdot](> href=)">http://sdm.link/slashdot;>[http://sdm.link/slashdot](> href=)">http://sdm.link/slashdot;>http://sdm.link/slashdot;>http://sdm.link/slashdot;>[http://sdm.link/slashdot](> href=)">http://sdm.link/slashdot >> ___ >> Freedos-user mailing list >> Freedos-user@lists.sourceforge.net >> [https://lists.sourceforge.net/lists/listinfo/freedos-user](>
Re: [Freedos-user] Networking without ethernet?
On Tue, Jul 10, 2018 at 2:31 PM Mateusz Viste wrote: > > Does it have a parallel port? If so, then you could run PLIP. I wrote a > gopher article about connecting a no-NIC PC to the LAN through its > parallel port using PLIP: > > gopher://gopher.viste.fr/1/myinfobase/?disp2017-03-05 plip bridge Any chance of posting that somewhere that doesn't require a gopher client to access it? I have gopher access on Firefox Quantum via Overbyte WX (https://gopher.floodgap.com/overbite/) but it doesn't like the link: Malformed input detected (non-alphanumerical!): 2017-03-05%20plip%20bridge Most folks likely no longer have anything that speaks the gopher protocol. > Mateusz __ Dennis https://plus.google.com/u/0/105128793974319004519 -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking without ethernet?
On Mon, 09 Jul 2018 21:08:35 -0500, David McMackins wrote: > I have a 1998 Sony Vaio running FreeDOS. This model did not include an > ethernet controller (or wlan), but it does have an old modem in it. I've > been going through the networking guide referred to by Rugxulo, and I > got down to running NICSCAN.EXE only to realize *oops!* this computer > doesn't even have an ethernet card. Does it have a parallel port? If so, then you could run PLIP. I wrote a gopher article about connecting a no-NIC PC to the LAN through its parallel port using PLIP: gopher://gopher.viste.fr/1/myinfobase/?disp2017-03-05 plip bridge Mateusz -- FreeDOS is present on the USENET, too! alt.os.free-dos -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking without ethernet?
On Tue, Jul 10, 2018 at 1:24 PM David McMackins wrote: > > Even if I did, that doesn't answer my question. Even if I get connected > to dial-up, will TCP/IP applications still work, or will they complain > about drivers since they are trying to access a NIC? I don't see why not. TCP-IP is a protocol stack. It sees things in terms of packets, and tosses them around. What the TCP-IP applications communicate through may not *be* a NIC. Take a look at the OSI network model. (https://www.lifewire.com/layers-of-the-osi-model-illustrated-818017) The precise medium over which the packets travel is defined on the physical and data link layers. Protocols like http and ftp happen *above* that on the network and transport layers. Here, Internet access from my desktop happens over a CAT5 cable plugged into my router, but my SO's laptop and various Wifi devices communicate over Wifi. The router doesn't care - it sees TCP-IP packets. Incoming arrive over a cable connection. Outgoing arrive via cable or Wifi. As long as the router sees properly formed packets, it can route them. How it gets the packets is irrelevant. Separating the exact physical method by which signals are sent and received from the way they are routed over the net is the point of OSI. Way back when, before I got broadband, I had a 56K dial-up modem connection to an ISP's servers. I could browse the web and do FTP, though an order of magnitude or two slower than what I currently have. Early web developers were advised that the user likely had a 14.4kbps connection, and to send only as much data as was absolutely necessary, so the user didn't grow old and grey waiting. DSL lines still use twisted pair copper, though the DSL model expects to plug into a NIC card. Twisted pair copper, coaxial cable, fiber, Wifi - no matter A packet is a packet is a packet. The bigger challenge here would be coming up with a standard POTS line to *do* dial-up. I went to VIOP ten years ago and dropped the POTS line. I'm in NYC, and Verizon no longer installs copper. Existing copper that works is maintained. Copper that was damaged by Hurricane Sandy is *not* being replaced. If you had that, your options are cellular or fiber. I have a USR 56K modem in a parts drawer. I've been tempted to plug it into a port on the router through which I attach a phone, save that the current desktop doesn't have the port a modem plugs into, and nothing I access does dial-up. > David E. McMackins II __ Dennis -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking without ethernet?
Even if I did, that doesn't answer my question. Even if I get connected to dial-up, will TCP/IP applications still work, or will they complain about drivers since they are trying to access a NIC? Happy Hacking, David E. McMackins II Supporting Member, Electronic Frontier Foundation (#2296972) Associate Member, Free Software Foundation (#12889) www.mcmackins.org www.delwink.com www.eff.org www.gnu.org www.fsf.org On 2018-07-10 12:17, Louis Santillan wrote: Have you tried setting up a Linux box as a dial-up server? [0] [0] https://www.howtoforge.com/linux_dialin_server [8] On Mon, Jul 9, 2018 at 9:10 PM David McMackins wrote: I have a 1998 Sony Vaio running FreeDOS. This model did not include an ethernet controller (or wlan), but it does have an old modem in it. I've been going through the networking guide referred to by Rugxulo, and I got down to running NICSCAN.EXE only to realize *oops!* this computer doesn't even have an ethernet card. Supposing I could find a working phone line and dial-up service to connect the modem to, is there hope of using TCP/IP applications like wget over it using the software available to me? Happy Hacking, David E. McMackins II Supporting Member, Electronic Frontier Foundation (#2296972) Associate Member, Free Software Foundation (#12889) www.mcmackins.org [1] www.delwink.com [2] www.eff.org [3] www.gnu.org [4] www.fsf.org [5] -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot [6] ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user [7] Links: -- [1] http://www.mcmackins.org [2] http://www.delwink.com [3] http://www.eff.org [4] http://www.gnu.org [5] http://www.fsf.org [6] http://sdm.link/slashdot [7] https://lists.sourceforge.net/lists/listinfo/freedos-user [8] https://www.howtoforge.com/linux_dialin_server -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking without ethernet?
Have you tried setting up a Linux box as a dial-up server? [0] [0] https://www.howtoforge.com/linux_dialin_server On Mon, Jul 9, 2018 at 9:10 PM David McMackins wrote: > I have a 1998 Sony Vaio running FreeDOS. This model did not include an > ethernet controller (or wlan), but it does have an old modem in it. I've > been going through the networking guide referred to by Rugxulo, and I > got down to running NICSCAN.EXE only to realize *oops!* this computer > doesn't even have an ethernet card. > > Supposing I could find a working phone line and dial-up service to > connect the modem to, is there hope of using TCP/IP applications like > wget over it using the software available to me? > > Happy Hacking, > > David E. McMackins II > Supporting Member, Electronic Frontier Foundation (#2296972) > Associate Member, Free Software Foundation (#12889) > > www.mcmackins.org www.delwink.com > www.eff.org www.gnu.org www.fsf.org > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
Here's a reference, by the way, on the ipconfig usage that I mention below: ftp://ftp.microsoft.com/misc1/BUSSYS/LANMAN/KB/Q183/8/58.TXT A couple more observations: When I booted up this morning, ipconfig c:\net once again reported the lease expired, but the expiration time coincided exactly -- to the minute -- with the bootup time, and the lease-issued time was exactly 24 hours before I booted up this morning. Thinking to dodge the DHCP lease issue, I set up with a static IP outside the DHCP address scope (but still within the same subnet segment). Nonetheless ipconfig c:\net still reports an IP within the DHCP scope, rather than the static IP I assigned. Current functionality: I can successfully ping an IP address e.g. ping 8.8.8.8 but name resolution fails, so no-go on ping google.com. On 6/15/2015 8:25 PM, John Hupp wrote: I found out that ipconfig usage is not as expected for the DOS client. Ipconfig /all is meaningless. In my case, the one and only good command is ipconfig c:\net. This then reports (now again under DHCP), an IP address, gateway, and DNS server as expected. But it reports Lease Expired. Even after I forced the router to give it a brand new lease on a different IP, it still reports the lease expired. The router shows the lease as freshly issued with a day to live. The date and time are correct on client and server. Ideas? (And no, ipconfig /release or ipconfig /renew won't work either. They too are meaningless.) On 6/15/2015 12:19 PM, John Hupp wrote: I just tried changing the DOS client from DHCP to static configuration, and I still get the same net use error. Furthermore ipconfig /all still reports No DHCP data available. Shouldn't it report my static configuration info? On 6/15/2015 11:46 AM, John Hupp wrote: Fundamentals -- you may be onto something. Though TCP/IP initialization completes without error, running ipconfig /all yields No DHCP data available. I get the same result from two identical cards, both configured the same way. I do note that both cards are old non-PNP ISA cards, which I thought would be appropriate for this vintage rig. In the meantime, in the Registry I changed HKLM\SYSTEM\CurrentControlSet\Control\Lsa\LMCompatibilityLevel=3 – 0, which is Send LM NTLM responses per https://technet.microsoft.com/en-us/library/jj852207%28v=ws.10%29.aspx. Then I rebooted. But I still get the same error on the DOS client. @ Roberto Fazzalari: I have been avoiding your approach to date since I never had more than a rank novice's acquaintance with Wireshark. But it may be that I'll have to get reacquainted! On 6/15/2015 12:09 AM, Louis Santillan wrote: Be sure that you have a good IP, gateway, and DNS setting from your DHCP server. -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
But does your client machine know that? I.E. do you have the DNS server configured in the network settings? -Original Message- From: John Hupp [mailto:free...@prpcompany.com] Sent: Tuesday, June 16, 2015 10:42 AM To: Discussion and general questions about FreeDOS. Subject: Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied The router provides DNS. On 6/16/2015 10:39 AM, Dave Kerber wrote: Do you have a DNS server configured? -Original Message- From: John Hupp [mailto:free...@prpcompany.com] Sent: Tuesday, June 16, 2015 9:48 AM To: Discussion and general questions about FreeDOS. Subject: Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied Here's a reference, by the way, on the ipconfig usage that I mention below: ftp://ftp.microsoft.com/misc1/BUSSYS/LANMAN/KB/Q183/8/58.TXT A couple more observations: When I booted up this morning, ipconfig c:\net once again reported the lease expired, but the expiration time coincided exactly -- to the minute -- with the bootup time, and the lease-issued time was exactly 24 hours before I booted up this morning. Thinking to dodge the DHCP lease issue, I set up with a static IP outside the DHCP address scope (but still within the same subnet segment). Nonetheless ipconfig c:\net still reports an IP within the DHCP scope, rather than the static IP I assigned. Current functionality: I can successfully ping an IP address e.g. ping 8.8.8.8 but name resolution fails, so no-go on ping google.com. On 6/15/2015 8:25 PM, John Hupp wrote: I found out that ipconfig usage is not as expected for the DOS client. Ipconfig /all is meaningless. In my case, the one and only good command is ipconfig c:\net. This then reports (now again under DHCP), an IP address, gateway, and DNS server as expected. But it reports Lease Expired. Even after I forced the router to give it a brand new lease on a different IP, it still reports the lease expired. The router shows the lease as freshly issued with a day to live. The date and time are correct on client and server. Ideas? (And no, ipconfig /release or ipconfig /renew won't work either. They too are meaningless.) On 6/15/2015 12:19 PM, John Hupp wrote: I just tried changing the DOS client from DHCP to static configuration, and I still get the same net use error. Furthermore ipconfig /all still reports No DHCP data available. Shouldn't it report my static configuration info? On 6/15/2015 11:46 AM, John Hupp wrote: Fundamentals -- you may be onto something. Though TCP/IP initialization completes without error, running ipconfig /all yields No DHCP data available. I get the same result from two identical cards, both configured the same way. I do note that both cards are old non-PNP ISA cards, which I thought would be appropriate for this vintage rig. In the meantime, in the Registry I changed HKLM\SYSTEM\CurrentControlSet\Control\Lsa\LMCompatibilityLevel=3 - 0, which is Send LM NTLM responses per https://technet.microsoft.com/en- us/library/jj852207%28v=ws.10%29.aspx. Then I rebooted. But I still get the same error on the DOS client. @ Roberto Fazzalari: I have been avoiding your approach to date since I never had more than a rank novice's acquaintance with Wireshark. But it may be that I'll have to get reacquainted! On 6/15/2015 12:09 AM, Louis Santillan wrote: Be sure that you have a good IP, gateway, and DNS setting from your DHCP server. --- --- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
Yes, in the static setup. And when I have had it configured instead in DHCP mode, I would expect it to pick that up automatically. On 6/16/2015 11:07 AM, Dave Kerber wrote: But does your client machine know that? I.E. do you have the DNS server configured in the network settings? -Original Message- From: John Hupp [mailto:free...@prpcompany.com] Sent: Tuesday, June 16, 2015 10:42 AM To: Discussion and general questions about FreeDOS. Subject: Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied The router provides DNS. On 6/16/2015 10:39 AM, Dave Kerber wrote: Do you have a DNS server configured? -Original Message- From: John Hupp [mailto:free...@prpcompany.com] Sent: Tuesday, June 16, 2015 9:48 AM To: Discussion and general questions about FreeDOS. Subject: Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied Here's a reference, by the way, on the ipconfig usage that I mention below: ftp://ftp.microsoft.com/misc1/BUSSYS/LANMAN/KB/Q183/8/58.TXT A couple more observations: When I booted up this morning, ipconfig c:\net once again reported the lease expired, but the expiration time coincided exactly -- to the minute -- with the bootup time, and the lease-issued time was exactly 24 hours before I booted up this morning. Thinking to dodge the DHCP lease issue, I set up with a static IP outside the DHCP address scope (but still within the same subnet segment). Nonetheless ipconfig c:\net still reports an IP within the DHCP scope, rather than the static IP I assigned. Current functionality: I can successfully ping an IP address e.g. ping 8.8.8.8 but name resolution fails, so no-go on ping google.com. On 6/15/2015 8:25 PM, John Hupp wrote: I found out that ipconfig usage is not as expected for the DOS client. Ipconfig /all is meaningless. In my case, the one and only good command is ipconfig c:\net. This then reports (now again under DHCP), an IP address, gateway, and DNS server as expected. But it reports Lease Expired. Even after I forced the router to give it a brand new lease on a different IP, it still reports the lease expired. The router shows the lease as freshly issued with a day to live. The date and time are correct on client and server. Ideas? (And no, ipconfig /release or ipconfig /renew won't work either. They too are meaningless.) On 6/15/2015 12:19 PM, John Hupp wrote: I just tried changing the DOS client from DHCP to static configuration, and I still get the same net use error. Furthermore ipconfig /all still reports No DHCP data available. Shouldn't it report my static configuration info? On 6/15/2015 11:46 AM, John Hupp wrote: Fundamentals -- you may be onto something. Though TCP/IP initialization completes without error, running ipconfig /all yields No DHCP data available. I get the same result from two identical cards, both configured the same way. I do note that both cards are old non-PNP ISA cards, which I thought would be appropriate for this vintage rig. In the meantime, in the Registry I changed HKLM\SYSTEM\CurrentControlSet\Control\Lsa\LMCompatibilityLevel=3 - 0, which is Send LM NTLM responses per https://technet.microsoft.com/en- us/library/jj852207%28v=ws.10%29.aspx. Then I rebooted. But I still get the same error on the DOS client. @ Roberto Fazzalari: I have been avoiding your approach to date since I never had more than a rank novice's acquaintance with Wireshark. But it may be that I'll have to get reacquainted! On 6/15/2015 12:09 AM, Louis Santillan wrote: Be sure that you have a good IP, gateway, and DNS setting from your DHCP server. --- --- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
Do you have a DNS server configured? -Original Message- From: John Hupp [mailto:free...@prpcompany.com] Sent: Tuesday, June 16, 2015 9:48 AM To: Discussion and general questions about FreeDOS. Subject: Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied Here's a reference, by the way, on the ipconfig usage that I mention below: ftp://ftp.microsoft.com/misc1/BUSSYS/LANMAN/KB/Q183/8/58.TXT A couple more observations: When I booted up this morning, ipconfig c:\net once again reported the lease expired, but the expiration time coincided exactly -- to the minute -- with the bootup time, and the lease-issued time was exactly 24 hours before I booted up this morning. Thinking to dodge the DHCP lease issue, I set up with a static IP outside the DHCP address scope (but still within the same subnet segment). Nonetheless ipconfig c:\net still reports an IP within the DHCP scope, rather than the static IP I assigned. Current functionality: I can successfully ping an IP address e.g. ping 8.8.8.8 but name resolution fails, so no-go on ping google.com. On 6/15/2015 8:25 PM, John Hupp wrote: I found out that ipconfig usage is not as expected for the DOS client. Ipconfig /all is meaningless. In my case, the one and only good command is ipconfig c:\net. This then reports (now again under DHCP), an IP address, gateway, and DNS server as expected. But it reports Lease Expired. Even after I forced the router to give it a brand new lease on a different IP, it still reports the lease expired. The router shows the lease as freshly issued with a day to live. The date and time are correct on client and server. Ideas? (And no, ipconfig /release or ipconfig /renew won't work either. They too are meaningless.) On 6/15/2015 12:19 PM, John Hupp wrote: I just tried changing the DOS client from DHCP to static configuration, and I still get the same net use error. Furthermore ipconfig /all still reports No DHCP data available. Shouldn't it report my static configuration info? On 6/15/2015 11:46 AM, John Hupp wrote: Fundamentals -- you may be onto something. Though TCP/IP initialization completes without error, running ipconfig /all yields No DHCP data available. I get the same result from two identical cards, both configured the same way. I do note that both cards are old non-PNP ISA cards, which I thought would be appropriate for this vintage rig. In the meantime, in the Registry I changed HKLM\SYSTEM\CurrentControlSet\Control\Lsa\LMCompatibilityLevel=3 - 0, which is Send LM NTLM responses per https://technet.microsoft.com/en- us/library/jj852207%28v=ws.10%29.aspx. Then I rebooted. But I still get the same error on the DOS client. @ Roberto Fazzalari: I have been avoiding your approach to date since I never had more than a rank novice's acquaintance with Wireshark. But it may be that I'll have to get reacquainted! On 6/15/2015 12:09 AM, Louis Santillan wrote: Be sure that you have a good IP, gateway, and DNS setting from your DHCP server. --- --- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
The router provides DNS. On 6/16/2015 10:39 AM, Dave Kerber wrote: Do you have a DNS server configured? -Original Message- From: John Hupp [mailto:free...@prpcompany.com] Sent: Tuesday, June 16, 2015 9:48 AM To: Discussion and general questions about FreeDOS. Subject: Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied Here's a reference, by the way, on the ipconfig usage that I mention below: ftp://ftp.microsoft.com/misc1/BUSSYS/LANMAN/KB/Q183/8/58.TXT A couple more observations: When I booted up this morning, ipconfig c:\net once again reported the lease expired, but the expiration time coincided exactly -- to the minute -- with the bootup time, and the lease-issued time was exactly 24 hours before I booted up this morning. Thinking to dodge the DHCP lease issue, I set up with a static IP outside the DHCP address scope (but still within the same subnet segment). Nonetheless ipconfig c:\net still reports an IP within the DHCP scope, rather than the static IP I assigned. Current functionality: I can successfully ping an IP address e.g. ping 8.8.8.8 but name resolution fails, so no-go on ping google.com. On 6/15/2015 8:25 PM, John Hupp wrote: I found out that ipconfig usage is not as expected for the DOS client. Ipconfig /all is meaningless. In my case, the one and only good command is ipconfig c:\net. This then reports (now again under DHCP), an IP address, gateway, and DNS server as expected. But it reports Lease Expired. Even after I forced the router to give it a brand new lease on a different IP, it still reports the lease expired. The router shows the lease as freshly issued with a day to live. The date and time are correct on client and server. Ideas? (And no, ipconfig /release or ipconfig /renew won't work either. They too are meaningless.) On 6/15/2015 12:19 PM, John Hupp wrote: I just tried changing the DOS client from DHCP to static configuration, and I still get the same net use error. Furthermore ipconfig /all still reports No DHCP data available. Shouldn't it report my static configuration info? On 6/15/2015 11:46 AM, John Hupp wrote: Fundamentals -- you may be onto something. Though TCP/IP initialization completes without error, running ipconfig /all yields No DHCP data available. I get the same result from two identical cards, both configured the same way. I do note that both cards are old non-PNP ISA cards, which I thought would be appropriate for this vintage rig. In the meantime, in the Registry I changed HKLM\SYSTEM\CurrentControlSet\Control\Lsa\LMCompatibilityLevel=3 - 0, which is Send LM NTLM responses per https://technet.microsoft.com/en- us/library/jj852207%28v=ws.10%29.aspx. Then I rebooted. But I still get the same error on the DOS client. @ Roberto Fazzalari: I have been avoiding your approach to date since I never had more than a rank novice's acquaintance with Wireshark. But it may be that I'll have to get reacquainted! On 6/15/2015 12:09 AM, Louis Santillan wrote: Be sure that you have a good IP, gateway, and DNS setting from your DHCP server. -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
OK, I think now that there is more than one issue. After reviewing the fact that older Windows PC's have great difficulties connecting to Vista shares, I thought then that it probably shouldn't be surprising that this is very difficult to impossible for the MS-DOS Network Client. To test this idea, I slapped together a Win 98 machine, shared a folder, and found that the DOS client was able to connect and write to it just fine. When I last worked with FreeDOS several years ago, I think I was able to connect to Win XP, but unless one of you is successfully connecting to Vista or newer, I am inclined to write that off as a can't do. A separate issue: When DOS successfully connected to Win 98, ipconfig c:\net was still reporting that the lease was expired! And it did so whether I had configured DOS for DHCP or a static configuration. And likewise, whether it was configured as static or DHCP, the DOS client could still connect to the W98 share. The lease-expired status seems to be a bug. Yet another separate issue: As I described earlier, when I set up for a static configuration, this is ignored. I probably won't invest too much time into investigating, since I much prefer DHCP. - If I can't move files easily to/from the DOS client to a share on the Vista server, then I'll probably want to get wget and/or Arachne working. But so far I just have NDIS drivers installed, and wget seems to require packet drivers. I have a vague recollection that Arachne may also. So I think this will be my next interest. On 6/16/2015 9:48 AM, John Hupp wrote: Here's a reference, by the way, on the ipconfig usage that I mention below: ftp://ftp.microsoft.com/misc1/BUSSYS/LANMAN/KB/Q183/8/58.TXT A couple more observations: When I booted up this morning, ipconfig c:\net once again reported the lease expired, but the expiration time coincided exactly -- to the minute -- with the bootup time, and the lease-issued time was exactly 24 hours before I booted up this morning. Thinking to dodge the DHCP lease issue, I set up with a static IP outside the DHCP address scope (but still within the same subnet segment). Nonetheless ipconfig c:\net still reports an IP within the DHCP scope, rather than the static IP I assigned. Current functionality: I can successfully ping an IP address e.g. ping 8.8.8.8 but name resolution fails, so no-go on ping google.com. On 6/15/2015 8:25 PM, John Hupp wrote: I found out that ipconfig usage is not as expected for the DOS client. Ipconfig /all is meaningless. In my case, the one and only good command is ipconfig c:\net. This then reports (now again under DHCP), an IP address, gateway, and DNS server as expected. But it reports Lease Expired. Even after I forced the router to give it a brand new lease on a different IP, it still reports the lease expired. The router shows the lease as freshly issued with a day to live. The date and time are correct on client and server. Ideas? (And no, ipconfig /release or ipconfig /renew won't work either. They too are meaningless.) On 6/15/2015 12:19 PM, John Hupp wrote: I just tried changing the DOS client from DHCP to static configuration, and I still get the same net use error. Furthermore ipconfig /all still reports No DHCP data available. Shouldn't it report my static configuration info? On 6/15/2015 11:46 AM, John Hupp wrote: Fundamentals -- you may be onto something. Though TCP/IP initialization completes without error, running ipconfig /all yields No DHCP data available. I get the same result from two identical cards, both configured the same way. I do note that both cards are old non-PNP ISA cards, which I thought would be appropriate for this vintage rig. In the meantime, in the Registry I changed HKLM\SYSTEM\CurrentControlSet\Control\Lsa\LMCompatibilityLevel=3 – 0, which is Send LM NTLM responses per https://technet.microsoft.com/en-us/library/jj852207%28v=ws.10%29.aspx. Then I rebooted. But I still get the same error on the DOS client. @ Roberto Fazzalari: I have been avoiding your approach to date since I never had more than a rank novice's acquaintance with Wireshark. But it may be that I'll have to get reacquainted! On 6/15/2015 12:09 AM, Louis Santillan wrote: Be sure that you have a good IP, gateway, and DNS setting from your DHCP server. -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
Fundamentals -- you may be onto something. Though TCP/IP initialization completes without error, running ipconfig /all yields No DHCP data available. I get the same result from two identical cards, both configured the same way. I do note that both cards are old non-PNP ISA cards, which I thought would be appropriate for this vintage rig. In the meantime, in the Registry I changed HKLM\SYSTEM\CurrentControlSet\Control\Lsa\LMCompatibilityLevel=3 – 0, which is Send LM NTLM responses per https://technet.microsoft.com/en-us/library/jj852207%28v=ws.10%29.aspx. Then I rebooted. But I still get the same error on the DOS client. @ Roberto Fazzalari: I have been avoiding your approach to date since I never had more than a rank novice's acquaintance with Wireshark. But it may be that I'll have to get reacquainted! On 6/15/2015 12:09 AM, Louis Santillan wrote: Be sure that you have a good IP, gateway, and DNS setting from your DHCP server. -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
you can install a normal client on a computer and make and reord the transition data using wireshark, and compare, or just sniff the data and see if for example yhe request exit well formed from client, in some cases the error code in the packet data is more explained that what you can see at application level. 2015-06-15 0:15 GMT+02:00 John Hupp free...@prpcompany.com: Yes, but in this case I'm not seeing that have any successful case to compare against. On 6/14/2015 6:01 PM, Roberto Fazzalari wrote: I use to resolve this kind of problem by monitoring the network traffic; capture the traffic data on the network wen the transaction go well aand when not and compare it, in this way you can understand more, in the past i use to do in this way to resolv problems. 2015-06-14 22:22 GMT+02:00 Rugxulo rugx...@gmail.com: Hi, On Sun, Jun 14, 2015 at 12:32 PM, John Hupp free...@prpcompany.com wrote: I installed MS-DOS Network Client, which successfully initializes with TCP/IP via DHCP. But when I try net use z: \\server\share and enter the password (with a user name that matches the Win Vista peer server account), I get Error 5: Access has been denied. ... Linux machines on the LAN connect to the server OK with the same account. I tried disabling SMB2 via a registry entry ... but this made no difference. Anyone know how to fix this? Don't use Vista ... just use Linux! :-)) (Seriously, it's not wrong to dual boot. I know you want to use DOS, which is fine, but you really might have better luck with ZipSlack/Slackware 11.0 [2006] atop UMSDOS: ftp://ftp.slackware.com/pub/slackware/slackware-11.0/zipslack/ ) -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing listFreedos-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
bt you write: Linux machines on the LAN connect to the server OK with the same account., record the transaction on that machine and compare. 2015-06-15 0:15 GMT+02:00 John Hupp free...@prpcompany.com: Yes, but in this case I'm not seeing that have any successful case to compare against. On 6/14/2015 6:01 PM, Roberto Fazzalari wrote: I use to resolve this kind of problem by monitoring the network traffic; capture the traffic data on the network wen the transaction go well aand when not and compare it, in this way you can understand more, in the past i use to do in this way to resolv problems. 2015-06-14 22:22 GMT+02:00 Rugxulo rugx...@gmail.com: Hi, On Sun, Jun 14, 2015 at 12:32 PM, John Hupp free...@prpcompany.com wrote: I installed MS-DOS Network Client, which successfully initializes with TCP/IP via DHCP. But when I try net use z: \\server\share and enter the password (with a user name that matches the Win Vista peer server account), I get Error 5: Access has been denied. ... Linux machines on the LAN connect to the server OK with the same account. I tried disabling SMB2 via a registry entry ... but this made no difference. Anyone know how to fix this? Don't use Vista ... just use Linux! :-)) (Seriously, it's not wrong to dual boot. I know you want to use DOS, which is fine, but you really might have better luck with ZipSlack/Slackware 11.0 [2006] atop UMSDOS: ftp://ftp.slackware.com/pub/slackware/slackware-11.0/zipslack/ ) -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing listFreedos-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
for example you can do this by looking at the data coming from the client network interface sniffing with wireshark outgoing data from the client 2015-06-15 6:09 GMT+02:00 Louis Santillan lpsan...@gmail.com: Be sure that you have a good IP, gateway, and DNS setting from your DHCP server. On Sun, Jun 14, 2015 at 3:37 PM, John Hupp free...@prpcompany.com wrote: Though my initial interest (and testing) was oriented toward moving files on the LAN, I also find that I cannot ping web sites. I get DGN0217: Remote name cannot be resolved. On 6/14/2015 6:14 PM, John Hupp wrote: Thanks, but making that change did not make a difference. I have also now edited the HOSTS file to add the server there, due to what I read at ftp://ftp.microsoft.com/misc1/BUSSYS/LANMAN/KB/Q130/5/38.TXT about not being able to ping the server. So I can indeed ping the server now, but access is still denied for the net use command. On 6/14/2015 3:06 PM, TJ Edmister wrote: Did you check the NTLM compatibility mode in Vista? HKLM\SYSTEM\CurrentControlSet\Control\Lsa There should be a DWORD named LmCompatibilityLevel set to value of 1 On Sun, 14 Jun 2015 13:32:34 -0400, John Hupp free...@prpcompany.com wrote: I installed MS-DOS Network Client, which successfully initializes with TCP/IP via DHCP. But when I try net use z: \\server\share and enter the password (with a user name that matches the Win Vista peer server account), I get Error 5: Access has been denied. Likewise, net view \\server yields the same error. And net view yields Error 6118: The list of servers for this workgroup is not currently available. Linux machines on the LAN connect to the server OK with the same account. I tried disabling SMB2 via a registry entry (per https://www.petri.com/how-to-disable-smb-2-on-windows-vista-or-server-2008 ), but this made no difference. Anyone know how to fix this? -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
Forgive me if I didn't catch it, but are you able to ping successfully w/o a full network setup (just connect via packet driver and DHCP) and are you able to use wget or fdnpkg and download a file? On Mon, Jun 15, 2015 at 2:15 PM, Ralf Quint freedos...@gmail.com wrote: On 6/15/2015 10:38 AM, Dave Kerber wrote: Are you trying to connect by dns name, or by IP address? To take one level of possible trouble out of the equation, try connecting by IP addr. If the ipconfig doesn't show any IP info on the host, it doesn't matter how you try to connect from that host, either way it has to fail. Your approach would only work in case just the DNS server info wouldn't be properly set. But the really strange thing is that he states that he doesn't even get a proper response when setting a static IP on the host, with ipconfig still claiming that it doesn't get info from a DHCP server. That indicates that there is rather something more basic amiss... Ralf --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
Are you trying to connect by dns name, or by IP address? To take one level of possible trouble out of the equation, try connecting by IP addr. -Original Message- From: John Hupp [mailto:free...@prpcompany.com] Sent: Monday, June 15, 2015 12:20 PM To: Discussion and general questions about FreeDOS. Subject: Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied I just tried changing the DOS client from DHCP to static configuration, and I still get the same net use error. Furthermore ipconfig /all still reports No DHCP data available. Shouldn't it report my static configuration info? On 6/15/2015 11:46 AM, John Hupp wrote: Fundamentals -- you may be onto something. Though TCP/IP initialization completes without error, running ipconfig /all yields No DHCP data available. I get the same result from two identical cards, both configured the same way. I do note that both cards are old non-PNP ISA cards, which I thought would be appropriate for this vintage rig. In the meantime, in the Registry I changed HKLM\SYSTEM\CurrentControlSet\Control\Lsa\LMCompatibilityLevel=3 - 0, which is Send LM NTLM responses per https://technet.microsoft.com/en- us/library/jj852207%28v=ws.10%29.aspx. Then I rebooted. But I still get the same error on the DOS client. @ Roberto Fazzalari: I have been avoiding your approach to date since I never had more than a rank novice's acquaintance with Wireshark. But it may be that I'll have to get reacquainted! On 6/15/2015 12:09 AM, Louis Santillan wrote: Be sure that you have a good IP, gateway, and DNS setting from your DHCP server. --- --- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
I found out that ipconfig usage is not as expected for the DOS client. Ipconfig /all is meaningless. In my case, the one and only good command is ipconfig c:\net. This then reports (now again under DHCP), an IP address, gateway, and DNS server as expected. But it reports Lease Expired. Even after I forced the router to give it a brand new lease on a different IP, it still reports the lease expired. The router shows the lease as freshly issued with a day to live. The date and time are correct on client and server. Ideas? (And no, ipconfig /release or ipconfig /renew won't work either. They too are meaningless.) On 6/15/2015 12:19 PM, John Hupp wrote: I just tried changing the DOS client from DHCP to static configuration, and I still get the same net use error. Furthermore ipconfig /all still reports No DHCP data available. Shouldn't it report my static configuration info? On 6/15/2015 11:46 AM, John Hupp wrote: Fundamentals -- you may be onto something. Though TCP/IP initialization completes without error, running ipconfig /all yields No DHCP data available. I get the same result from two identical cards, both configured the same way. I do note that both cards are old non-PNP ISA cards, which I thought would be appropriate for this vintage rig. In the meantime, in the Registry I changed HKLM\SYSTEM\CurrentControlSet\Control\Lsa\LMCompatibilityLevel=3 – 0, which is Send LM NTLM responses per https://technet.microsoft.com/en-us/library/jj852207%28v=ws.10%29.aspx. Then I rebooted. But I still get the same error on the DOS client. @ Roberto Fazzalari: I have been avoiding your approach to date since I never had more than a rank novice's acquaintance with Wireshark. But it may be that I'll have to get reacquainted! On 6/15/2015 12:09 AM, Louis Santillan wrote: Be sure that you have a good IP, gateway, and DNS setting from your DHCP server. -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
Thanks, but making that change did not make a difference. I have also now edited the HOSTS file to add the server there, due to what I read at ftp://ftp.microsoft.com/misc1/BUSSYS/LANMAN/KB/Q130/5/38.TXT about not being able to ping the server. So I can indeed ping the server now, but access is still denied for the net use command. On 6/14/2015 3:06 PM, TJ Edmister wrote: Did you check the NTLM compatibility mode in Vista? HKLM\SYSTEM\CurrentControlSet\Control\Lsa There should be a DWORD named LmCompatibilityLevel set to value of 1 On Sun, 14 Jun 2015 13:32:34 -0400, John Hupp free...@prpcompany.com wrote: I installed MS-DOS Network Client, which successfully initializes with TCP/IP via DHCP. But when I try net use z: \\server\share and enter the password (with a user name that matches the Win Vista peer server account), I get Error 5: Access has been denied. Likewise, net view \\server yields the same error. And net view yields Error 6118: The list of servers for this workgroup is not currently available. Linux machines on the LAN connect to the server OK with the same account. I tried disabling SMB2 via a registry entry (per https://www.petri.com/how-to-disable-smb-2-on-windows-vista-or-server-2008), but this made no difference. Anyone know how to fix this? -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
Did you check the NTLM compatibility mode in Vista? HKLM\SYSTEM\CurrentControlSet\Control\Lsa There should be a DWORD named LmCompatibilityLevel set to value of 1 On Sun, 14 Jun 2015 13:32:34 -0400, John Hupp free...@prpcompany.com wrote: I installed MS-DOS Network Client, which successfully initializes with TCP/IP via DHCP. But when I try net use z: \\server\share and enter the password (with a user name that matches the Win Vista peer server account), I get Error 5: Access has been denied. Likewise, net view \\server yields the same error. And net view yields Error 6118: The list of servers for this workgroup is not currently available. Linux machines on the LAN connect to the server OK with the same account. I tried disabling SMB2 via a registry entry (per https://www.petri.com/how-to-disable-smb-2-on-windows-vista-or-server-2008), but this made no difference. Anyone know how to fix this? -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
Hi, On Sun, Jun 14, 2015 at 12:32 PM, John Hupp free...@prpcompany.com wrote: I installed MS-DOS Network Client, which successfully initializes with TCP/IP via DHCP. But when I try net use z: \\server\share and enter the password (with a user name that matches the Win Vista peer server account), I get Error 5: Access has been denied. ... Linux machines on the LAN connect to the server OK with the same account. I tried disabling SMB2 via a registry entry ... but this made no difference. Anyone know how to fix this? Don't use Vista ... just use Linux! :-)) (Seriously, it's not wrong to dual boot. I know you want to use DOS, which is fine, but you really might have better luck with ZipSlack/Slackware 11.0 [2006] atop UMSDOS: ftp://ftp.slackware.com/pub/slackware/slackware-11.0/zipslack/ ) -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
I use to resolve this kind of problem by monitoring the network traffic; capture the traffic data on the network wen the transaction go well aand when not and compare it, in this way you can understand more, in the past i use to do in this way to resolv problems. 2015-06-14 22:22 GMT+02:00 Rugxulo rugx...@gmail.com: Hi, On Sun, Jun 14, 2015 at 12:32 PM, John Hupp free...@prpcompany.com wrote: I installed MS-DOS Network Client, which successfully initializes with TCP/IP via DHCP. But when I try net use z: \\server\share and enter the password (with a user name that matches the Win Vista peer server account), I get Error 5: Access has been denied. ... Linux machines on the LAN connect to the server OK with the same account. I tried disabling SMB2 via a registry entry ... but this made no difference. Anyone know how to fix this? Don't use Vista ... just use Linux! :-)) (Seriously, it's not wrong to dual boot. I know you want to use DOS, which is fine, but you really might have better luck with ZipSlack/Slackware 11.0 [2006] atop UMSDOS: ftp://ftp.slackware.com/pub/slackware/slackware-11.0/zipslack/ ) -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
Though my initial interest (and testing) was oriented toward moving files on the LAN, I also find that I cannot ping web sites. I get DGN0217: Remote name cannot be resolved. On 6/14/2015 6:14 PM, John Hupp wrote: Thanks, but making that change did not make a difference. I have also now edited the HOSTS file to add the server there, due to what I read at ftp://ftp.microsoft.com/misc1/BUSSYS/LANMAN/KB/Q130/5/38.TXT about not being able to ping the server. So I can indeed ping the server now, but access is still denied for the net use command. On 6/14/2015 3:06 PM, TJ Edmister wrote: Did you check the NTLM compatibility mode in Vista? HKLM\SYSTEM\CurrentControlSet\Control\Lsa There should be a DWORD named LmCompatibilityLevel set to value of 1 On Sun, 14 Jun 2015 13:32:34 -0400, John Hupp free...@prpcompany.com wrote: I installed MS-DOS Network Client, which successfully initializes with TCP/IP via DHCP. But when I try net use z: \\server\share and enter the password (with a user name that matches the Win Vista peer server account), I get Error 5: Access has been denied. Likewise, net view \\server yields the same error. And net view yields Error 6118: The list of servers for this workgroup is not currently available. Linux machines on the LAN connect to the server OK with the same account. I tried disabling SMB2 via a registry entry (per https://www.petri.com/how-to-disable-smb-2-on-windows-vista-or-server-2008), but this made no difference. Anyone know how to fix this? -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
Be sure that you have a good IP, gateway, and DNS setting from your DHCP server. On Sun, Jun 14, 2015 at 3:37 PM, John Hupp free...@prpcompany.com wrote: Though my initial interest (and testing) was oriented toward moving files on the LAN, I also find that I cannot ping web sites. I get DGN0217: Remote name cannot be resolved. On 6/14/2015 6:14 PM, John Hupp wrote: Thanks, but making that change did not make a difference. I have also now edited the HOSTS file to add the server there, due to what I read at ftp://ftp.microsoft.com/misc1/BUSSYS/LANMAN/KB/Q130/5/38.TXT about not being able to ping the server. So I can indeed ping the server now, but access is still denied for the net use command. On 6/14/2015 3:06 PM, TJ Edmister wrote: Did you check the NTLM compatibility mode in Vista? HKLM\SYSTEM\CurrentControlSet\Control\Lsa There should be a DWORD named LmCompatibilityLevel set to value of 1 On Sun, 14 Jun 2015 13:32:34 -0400, John Hupp free...@prpcompany.com wrote: I installed MS-DOS Network Client, which successfully initializes with TCP/IP via DHCP. But when I try net use z: \\server\share and enter the password (with a user name that matches the Win Vista peer server account), I get Error 5: Access has been denied. Likewise, net view \\server yields the same error. And net view yields Error 6118: The list of servers for this workgroup is not currently available. Linux machines on the LAN connect to the server OK with the same account. I tried disabling SMB2 via a registry entry (per https://www.petri.com/how-to-disable-smb-2-on-windows-vista-or-server-2008), but this made no difference. Anyone know how to fix this? -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking, DOSemu and taprouter (new version, with DHCP!)
I care. :) I don't use dosemu as often as before, but it's good to know. I recall some problems with network slowness in dosemu, so it might be of use if I get around. Cheers, Bojan. On Sun, 23 Jun 2013 21:36:24 +0200 Mateusz Viste mate...@viste-family.net wrote: Hi! Not sure anybody cares, but here I go :) -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] networking: virtio, NFS?
Rugxulo rugx...@gmail.com writes: On Sun, Aug 19, 2012 at 12:35 AM, Ivan Shmakov wrote: I'm interested in running multiple instances of FreeDOS within QEMU. So, my questions are: • QEMU offers a “simplified” networking hardware (AKA virtio); is there a packet driver for it for FreeDOS? Dunno, doubt it, esp. if it's not just standard stuff and needs special code. Well, my guess is that virtio should need much less code than, say, ne2k. And with GNU/Linux as the guest, it runs considerably (as in: times) faster. IIRC, most people use Crynwr's NE2000 there. BTW, I was unable to find any Crynwr's packet drivers on the FreeDOS 1.1 image? (quoting old email from Erwin): qemu -L . -m 64 -hda freedos.img -boot c -hdb fat:c:\fat -net nic,model=ne2k_pci -net user ACK, thanks! Somehow, I've ended using mkdosdisk.sh to create ~/tmp/dos-exchange.image (thus -hdb ~/tmp/dos-exchange.image), which I access with Mtools from the host's side, like: $ grep -F -- dos-ex .mtoolsrc drive x: file=/home/private/users/ivan/tmp/dos-exchange.image partition=1 $ mdir x: Volume in drive X has no label Volume Serial Number is 2599-F805 Directory for X:/ … […] PS. Are there any promotional materials (flyers, posters, videos, etc.) for FreeDOS that we can use on our Software Freedom Day celebration next month, BTW? Online files to download (and print out) or actual physical copies? I'm sure it'd be both faster and cheaper to print it ourselves than to wait fo delivery, so I'm interested mainly in files. http://www.freedos.org/images/ ACK, thanks. http://www.zazzle.com/freedos -- FSF associate member #7257 http://sf-day.org/ -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] networking: virtio, NFS?
Hi, On Sun, Aug 19, 2012 at 12:35 AM, Ivan Shmakov oneing...@gmail.com wrote: I'm interested in running multiple instances of FreeDOS within QEMU. So, my questions are: • QEMU offers a “simplified” networking hardware (AKA virtio); is there a packet driver for it for FreeDOS? Dunno, doubt it, esp. if it's not just standard stuff and needs special code. IIRC, most people use Crynwr's NE2000 there. (quoting old email from Erwin): qemu -L . -m 64 -hda freedos.img -boot c -hdb fat:c:\fat -net nic,model=ne2k_pci -net user BTW, what host OS are you planning to use QEMU? IIRC, most development is targeted towards Linux. But our own Bernd often tries to use it atop Windows. The latest Win32 (unofficial) build I can find (1.1.1-1) is here, though I haven't tested it: http://virtuallyfun.superglobalmegacorp.com/ • I've seen mentions of XFS — a (free software?) DOS NFS client; where could it be obtained from? Never heard of it, but I'm far from network savvy. A quick search shows these sites: https://forums.virtualbox.org/viewtopic.php?f=2t=15377 http://sourceforge.net/apps/mediawiki/freedos/index.php?title=NFS http://freedos.trez0r.eu.org/freedos/news/technote/151.html http://www.mmnt.net/db/0/0/hope.eunet.lv/pub/msdos/nfs http://fossies.org/windows/misc/dos/old/ PS. Are there any promotional materials (flyers, posters, videos, etc.) for FreeDOS that we can use on our Software Freedom Day celebration next month, BTW? Online files to download (and print out) or actual physical copies? http://www.freedos.org/images/ http://www.zazzle.com/freedos -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
Christian Masloch said: Don't read Dissecting DOS though. Why not? -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
conclusion: don't use FreeDOS as a 'server' machine. Sure, that's the obvious easy way out. But wouldn't it be better overall (and wiser) to 1). actually find out what MS-DOS does, and 2). fix it in FreeDOS' kernel?;-) sure. as always: talk is cheap good luck Tom -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
conclusion: don't use FreeDOS as a 'server' machine. Sure, that's the obvious easy way out. But wouldn't it be better overall (and wiser) to 1). actually find out what MS-DOS does, and 2). fix it in FreeDOS' kernel?;-) If you are indicating that you want to volunteer... ;-) (... if that would indeed be the case, then I'd suggest gaining practice in C, in 86-mode 386 assembly language, and in using a capable enough 86-mode debugger to inspect DOS kernels as well as reading Undocumented DOS Second Edition and DOS Internals at least, plus optionally FreeDOS Kernel as well. [*] Then, one would have to become acquainted with the FreeDOS kernel's sources. And then the required course of action would either be self-evident, or one would have to start getting creative!) Regards, Chris [*] Don't read Dissecting DOS though. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
Whatever the issue is, it is apparently not that easy to find or fix. Reading RBIL for INT 21.5C, it seem to indicate that DR-DOS never was able to figure out how to do it, and it wasn't until Novell got involved that it actually started working correctly. (E)DR-DOS could be another possibility for the server, too. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
Thanks. Here's some comments if you care to read them. Not all of them are particularly relevant to our thread's topic. MSDOS, and presumably FreeDOS, does not natively provide a framework for safe filesharing and file locks, this needs to come from the server software working in combination with requests from the application via the client networking. If the server software is running on top of a DOS, it either needs to implement locking separately (in the server application), or it has to rely on locking being implemented by the DOS kernel. Normally when a simple DOS application opens a file it opens it in a specific mode, eg read or read/write, and when a file is opened in write mode it is opened exclusively, so any process that tried to open the file is given an access denied. If this is meant to refer to the normal case of local file system access without a proper SHARE extension loaded on eg MS-DOS and FreeDOS, then this is incorrect. The problem is that processes are allowed to freely access the same file in parallel, without any checks going on. and another mode for programs that did not like how share.exe worked. This other mode is the compatibility mode, and it presumably was only intended to allow older, mode-unaware programs to continue to work. Unfortunately, even most DOS programs developed after the introduction of the new modes continued using compatibility mode. Share.exe maintains two tables in memory, one for each file that is opened, and another for which portions of the file were locked, and what mode the portion was locked in Crucially, the entries in that new file table are unique (that is, each existing file might have at most one entry) and they link to all entries in DOS's other (SFT) file table. Lacking the new table, duplicate entries in the other table are entirely undetected. I have run DP over many many different server and networking client combinations, with up to about 40 simultaneous connections and not ever had a problem unless I was running share.exe on the client I don't understand how this could have happened. Given what I know, SHARE should only affect access to the local file system. And using it as opposed to not using it should definitively not cause problems. Regards, Chris -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
Whatever the issue is, it is apparently not that easy to find or fix. whatever the issue is, nobody is going to fix it anyway Reading RBIL for INT 21.5C, it seem to indicate that DR-DOS never was able to figure out how to do it, and it wasn't until Novell got involved that it actually started working correctly. I hate repeating myself, but this is most likely NOT an INT21.5C issue if you want to experiment: start NET.EXE in server mode start big file operations on server xcopy c:\Windows c:\Windows2 /s on client xcopy z:\windows z:\windows3 /s and see if this works reliable. this doesn't require share at all Tom -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
On Mon, Jun 18, 2012 at 6:25 AM, Tom Ehlertt...@drivesnapshot.de wrote: conclusion: don't use FreeDOS as a 'server' machine. Sure, that's the obvious easy way out. But wouldn't it be better overall (and wiser) to 1). actually find out what MS-DOS does, and 2). fix it in FreeDOS' kernel?;-) If it's mission critical then it should be running on an operating system designed to do that kind of task. software should NEVER run on a *buggy* system. but, from http://en.wikipedia.org/wiki/File_locking 'Windows inherits the semantics of share-access controls from the MS-DOS system, where sharing was introduced in MS–DOS 3.3' looks like MSDOS 3.3 was designed for this sort of problem. that FreeDOS kernel doesn't implement proper 'multitasking' with NET.EXE is an entirely different story anjd yes, Linux is the better tool at hand. Tom -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
Tom Ehlert t...@drivesnapshot.de wrote: try using MSDOS or linux (or even Windows) for the 'server' machine, and see if the problema go away I did the test with MS-DOS in the server and FreeDOS in the client. The problem vanished. I even used MODE con rate=32 which is the fastest typematic rate, and kept the arrow keys and PgUp/PgDn pressed in both computers for about a minute. The system is completely stable. then the problem is not related to SHARE, but most likely a kernel problem. SHARE is responsible to resolve conflicts around multiple *write* requests to the same file. just scrolling through a database should work with or without locking. but: in this case the remote machine and the local one (the 'server') ascess the file at the same time, with a decent probability that the server machine is inside DOS, when the read request from the remote machine arrives. if this is not handled properly, you get a lot of interesting (seemingly random) error messages as reported in you initial post From the server: - General failure reading drive C - Disk is write protected From the client: - Not ready reading drive G - (This one is from DataPerfect, in a rare instance when the client did not crash along with the server:) Network error. One or more of the database files can't be accessed because of the current authorization for the files [..] this is the black art of reliable disk access from a TSR (MSCLIENT), along InDOS flag, SDA, possibly some internal calls, ... most likely FreeDOS Kernel behaves just a tiny bit different from MSDOS, and 'multitasking' on top of FreeDOS goes wrong. btw: this could also affect different network stacks, because the problem would be similar. conclusion: don't use FreeDOS as a 'server' machine. Tom -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
Pentium definitely came in a 233MHz version, but I thought the 300MHz version was Pentium II only. -Original Message- From: Rugxulo [mailto:rugx...@gmail.com] Sent: Monday, June 18, 2012 12:10 AM To: freedos-user@lists.sourceforge.net Subject: Re: [Freedos-user] Networking Hi, On Jun 17, 2012 6:32 PM, Ulrich Hansen uhan...@mainz-online.de wrote: Ah, and NEOS: I didn't have time to really create a NEOS network here. I will look into it some other time. But at least the readme sounds good at first glance. The NEOS installer works on my old laptops (486SX33) but it doesn't in VirtualBox. In VirtualBox I get the TurboPascal Runtime Error 200 which seems to mean that the program won't work on computers with a clock speed faster than 200 MHz. So how old are your Pentiums? You can patch those problematic programs or run a TSR. ftp://ftp.sac.sk/pub/sac/utilprog/r200fix.zip BTW, I had vaguely thought the highest Pentium was 200 or 233 Mhz, but Wikipedia says 300 Mhz, but I think they were more common in lower speeds. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
The highest clock rates that were sold were 200MHz for Pentium, 233MHz for Pentium MMX, and 300MHz for Mobile Pentium MMX. The late mobile chips were made with a finer process (250nm IIRC). On Mon, 18 Jun 2012 11:25:01 -0400, David C. Kerber dker...@warrenrogersassociates.com wrote: Pentium definitely came in a 233MHz version, but I thought the 300MHz version was Pentium II only. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
Am 17.06.2012 um 07:37 schrieb Rugxulo: Excellent details, even better if it actually works! ;-) I just can say that I had Debian 4 running quite a few years on several 486SX33 with 20 MB RAM. Because the installation was the hardest part on such an old machine, I pulled out the drive on each of them and put it into a more powerful machine which had the advantage of having a CD drive. That worked well and I even compiled an own kernel for the 486 on it, with everything switched off that wasn't necessary. The more powerful machine was a Pentium 200 MMX with 64 MB RAM. But does Debian run on i386 [sic] anymore? I thought most people had (unfortunately) switched to i686 (CMOVxx), e.g. Fedora. Or is Debian more lenient?? Yes, Debian 6 dropped support for 386 CPUs, but supports everything from 486 upwards (1). Even if the cpu instructions themselves are compatible (no CMOVxx, which Pentium 1 lacks), you may not have enough RAM. I don't know for sure, but everything I had read always seemed to hint that a Pentium typically couldn't have more than 64 MB, so trying to cram a recent Debian might be a bit of a stretch, to say the least. The recommends nowadays for the installer are 64 MB RAM (2). But it will still work with a minimum of 22 MB RAM (3). Of course you can only use the textmode installer and shouldn't install a GUI. I have no idea of a better solution, unfortunately, only a blind guess that maybe?? Slackware 11.0 (circa 2006), aka ZipSlack, might work? At least it's easy to install atop DOS (kernel 2.4.x) and is only 67 MB .ZIP'd. I'd assume it has lower RAM requirements. Though it's not a full install by any means, but you can add on any extras you need (supposedly). ftp://ftp.slackware.com/pub/slackware/slackware-11.0/zipslack/ You are right, if we talk about Linux, there are a lot of options. IMHO Debian stable has the advantage that it gets frequent security updates and that the simple commands apt-get update and apt-get upgrade makes it easy to keep it up-to-date. Of course it depends from the circumstances: If the machine can't be connected to the internet, getting security updates is harder but maybe not as necessary as with a connected machine. A Linux server should be more secure than a DOS server but maybe this isn't necessary if the data isn't worth it. Well, hopefully everything Ulrich said will just work without worrying about all this extra stuff. Good luck! Yes you are right :-/. These things can be harder than I wrote and there still may be difficulties. But I am quite happy that the Samba/MS Client connection worked for me as expected with a recent Debian and FreeDOS (and tested on real hardware). Of course if anybody wants to go on explore or correct things, you are welcome. For instance the socket options work for me, but I didn't really look into them, I got them from (4). Nevertheless I am a bit proud to have even password authentication work fine - I did not get this to work in the past. Gerd Roethig with his smb.conf example (see 4 again) took the easy way out, as he dropped authentication at all. Of course if you add: guest account = YOURUSERNAME in the smb.conf global section and public = yes guest ok = yes in the share definitions you get a system that is open to everybody and everybody has the rights of YOURUSERNAME. But then we have even less security as with a DOS server, so what's the point? What really helped me was this article in german language here (5). I try to translate: The article explains that it may be NOT enough to set lanman auth=yes in the smb.conf global section to allow authentication from old clients like MS Client, Lanman, WFW or Win9x. It will not work if you already have set a user and password BEFORE you added the above line to your smb.conf. This is very likely. To make lanman auth work, SAMBA needs to set a special password hash into its password database for that user. But it will not do that if the above line isn't present. You can check if the hash is set correctly if you type: pdbedit -L -w i on the Linux system. If you see a bunch of X in the third column (after the second :) the hash is NOT set. The (easy) solution is to set the password for the user again by commanding: sudo smbpasswd -a username on the server. Another thing that is worth to explore further are the charset options of Samba. unix charset = ISO8859-15 dos charset = 850 makes sure that Samba shows filenames, that were created by the FreeDOS client, correctly back to the client. I use charset 850 because I live in Western Europe, others will want to use 437 (US). The contents of the files will not be corrected though. Debian internally runs with UTF-8, DOS with codepage 850 (or 437) so special characters will be shown differently in DOS and Linux. IMHO this shouldn't be a problem if the files are written by DOS clients only. All in all, I think it is a good to have proof that
Re: [Freedos-user] Networking
Am 17.06.2012 um 19:21 schrieb Marcos Favero Florence de Barros: It's good to know that it's possible, but we won't need passwords, at least for now -- I've checked it twice with management. As I wrote, if you add: guest account = YOURUSERNAME in the smb.conf global section and public = yes guest ok = yes path = /home/YOURUSERNAME in the share definitions, everybody can login and will be treated as the user YOURUSERNAME. But this means: Everybody who can plug himself into your network can see and access the share. That's not a good idea. So forget the lines above. Of course I can understand that it is just too much effort to create users and passwords for every doctor on the server and every client. But why not use just one username for all of your client machines and have the advantage that no stranger could login and mess with your database? You would configure the user yourself in the SYSTEM.INI (configure once, copy onto all other clients) and once you ran NET.EXE on one machine and your password was saved, you copy the resulting *.PWL file to all your clients into their MS Client folder. So your doctors are authenticating to the server without seeing it and without having to do anything. The PWL file is encrypted, authentication is encrypted and the database file on the server can be configured to be only readable and writable by that user. To me this seems pretty secure and relaxed at the same time. I am bit tired so I just hope I got it right. Debian internally runs with UTF-8, DOS with codepage 850 (or 437) so special characters will be shown differently in DOS and Linux. IMHO this shouldn't be a problem if the files are written by DOS clients only. That's OK. But there's another question here. I'm assuming that as the database developer I will often have to sit at the Debian machine. So we need one more element, DosEmu, and we must check whether text typed in it, for instance report headers, will come out with the right characters. Yes, I just checked. On a DOS client I wrote several special characters into a document before I transferred it to the server. If I open the document with mcedit on the Debian server I just see a . point for the missing characters. If I open it with Dosemu on the same server I see all the special characters again. So yes, Dosemu solves this. Good idea. Ah, and NEOS: I didn't have time to really create a NEOS network here. I will look into it some other time. But at least the readme sounds good at first glance. The NEOS installer works on my old laptops (486SX33) but it doesn't in VirtualBox. In VirtualBox I get the TurboPascal Runtime Error 200 which seems to mean that the program won't work on computers with a clock speed faster than 200 MHz. So how old are your Pentiums? Good night Ulrich -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
Hi, On Jun 17, 2012 6:32 PM, Ulrich Hansen uhan...@mainz-online.de wrote: Ah, and NEOS: I didn't have time to really create a NEOS network here. I will look into it some other time. But at least the readme sounds good at first glance. The NEOS installer works on my old laptops (486SX33) but it doesn't in VirtualBox. In VirtualBox I get the TurboPascal Runtime Error 200 which seems to mean that the program won't work on computers with a clock speed faster than 200 MHz. So how old are your Pentiums? You can patch those problematic programs or run a TSR. ftp://ftp.sac.sk/pub/sac/utilprog/r200fix.zip BTW, I had vaguely thought the highest Pentium was 200 or 233 Mhz, but Wikipedia says 300 Mhz, but I think they were more common in lower speeds. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
Hi Marcos , So where exactly is the file server that's storing the data file(s) in this scenario? Is it on the doctor's PC, assistant's PC, or some other location? In another location. could you be more specific about 1) where is the database located (not geografically, but what machine) 2) what's the 'servers' operating system ? if the answer to 2) is 'FreeDOS' then either SHARE.EXE is not running or SHARE.EXE is buggy. the latter is quite likely as it was never really tested against network access. try using MSDOS or linux (or even Windows) for the 'server' machine, and see if the problema go away hardware problems are very unlikely, given the symptoms you describe. Tom -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
I remember databases benefitting from a high amount of file handles, not 'benefit'. for some problems, many handles are needed, otherwise the database will not work at all. there is NEVER spurious problems caused by too many handles. but likely that's already being taken care of by caching software. ??? I downloaded SHARE from Japheth's site, and it turned out to be the same file I had. Where could I find other versions? I Couldn't find it by searching the internet, perhaps because 'share' is too common a word. Japheth's SHARE is probably the one and only SHARE for FreeDOS. no use to search the internet Tom -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
Hi, On Sat, Jun 16, 2012 at 10:07 AM, Bernd Blaauw bbla...@home.nl wrote: Op 16-6-2012 15:25, Marcos Favero Florence de Barros schreef: I downloaded SHARE from Japheth's site, and it turned out to be the same file I had. Where could I find other versions? I Couldn't find it by searching the internet, perhaps because 'share' is too common a word. I thought the FreeDOS kernel would contain SHARE, but apparently not. I vaguely thought so too, but I see no binary in ke2041_86f32.ZIP. But ke2041s.zip has SOURCE/ke2041/share/share.c and share.hlp and makefile (TC201), so it should be easy to build. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
I'm running FreeDOS, but yes, Linux is a possibility. This database project started modestly in 2006, but now the Health Center is relying more and more on it, so I want it to be very safe. in that case don't gamble with untested share.exe Still I would definitely prefer to stay with FreeDOS if at all possible :-) good luck Tom -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
Hi, On Sat, Jun 16, 2012 at 10:55 AM, Tom Ehlert t...@drivesnapshot.de wrote: Japheth's SHARE is probably the one and only SHARE for FreeDOS. no use to search the internet If I remember correctly (but haven't tested), Japheth made some minor adjustments for FreeDOS (only) to SHARE to work better with a few weird programs in Win 3.1, but this SHARE is far from complete and not a full replacement for the equivalent from MS-DOS. But you'd have to ask him for more details, obviously. Share: This is a version of FreeDOS Share which has a bug fixed making it impossible to run MS Office applications under Windows 3.1. This version of Share runs with FreeDOS only.DOS 08/2006 SHARE (20 kB) http://www.japheth.de/Download/DOS/SHARE.zip -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
but likely that's already being taken care of by caching software. ??? UIDE and LBACACHE will only work with INT 13h (local) drives, not network drives. Caching shouldn't be an issue, at least for the clients -- could be a problem on the server, though. According to RBIL, DR/Novell/Caldera DOS didn't correctly and fully support INT 21.5C until version 7, so it wouldn't surprise me very much if FreeDOS doesn't fully support it yet. I'm thinking the best thing to do is try MS-DOS on the server. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
Hi Tom, This might be irrelevant to the case at hand. if the answer to 2) is 'FreeDOS' then either SHARE.EXE is not running or SHARE.EXE is buggy. the latter is quite likely as it was never really tested against network access. If you know; does FreeDOS's file locking (ie SHARE) propagate file metadata changes to all SFTs referring to the same file? Here's some context for anyone interested: http://www.bttr-software.de/forum/forum_entry.php?id=11572 Regards, Chris -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
Am 15.06.2012 um 23:26 schrieb Marcos Favero Florence de Barros: It did work, but it turned out to be very fragile. As soon as the two people use the database more intensively, the system crashes -- in most cases, both server and client. If on the other hand they do things slowly, it works just fine. The hardware is mostly early Pentiums donated to us. The network software is MS-Client. Server Side: As I understand it, you use a FreeDOS machine with MS Client as server. To have server functions, you updated MS Client with WG1049.EXE (which is not legal but also not officially forbidden, see: http://www.jacco2.dds.nl/samba/dos.html#msclient ). Client Side: FreeDOS with MS Client as client. It's been a few years since I played a lot with FreeDOS and MS Client as server and as far as I remember it was never working great for me. Fragile is the word I have in mind too when I remember MS Client as server. I have read that MS Client with MS DOS works OK for you. But if you want to stick with Free Software, why not use a real Samba server together with the FreeDOS/MS Client clients? A Pentium 1 should be enough for that. Download for instance Debian Stable from here: http://cdimage.debian.org/debian-cd/6.0.5/i386/iso-cd/debian-6.0.5-i386-netinst.iso and when it comes to step Software selection choose File server. This will install Samba. Don't install a desktop environment. The following configuration file for Samba (/etc/smb.conf) works fine with MS Client on FreeDOS: #=== Global Settings === [global] workgroup = WORKGROUP server string = %h (Samba %v) wins support = yes os level = 65 domain master = yes local master = yes preferred master = yes name resolve order = hosts lmhosts host wins bcast dns proxy = no lm announce = true lanman auth = yes #=== Authentication security = share encrypt passwords = true invalid users = root unix password sync = false passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . max log size = 100 #=== Misc socket options = IPTOS_LOWDELAY TCP_NODELAY SO_SNDBUF=4096 SO_RCVBUF=4096 ; Name mangling options for DOS clients case sensitive = no default case = upper preserve case = no short preserve case = no mangle case = yes mangled names= yes mangling method = hash mangle prefix = 6 ; charsets ; unix charset = UTF-8 unix charset = ISO8859-15 dos charset = 850 #=== Shares == [share] comment = Samba Share writeable = true path = /home/USERNAME browseable = yes #=== Please exchange the name of the WORKGROUP with the name you want to use. Please exchange USERNAME with the name of the user you configured in Debian. After you configured the above smb.conf, you have to update his password again with the command sudo smbpasswd -a username. This update is necessary to make lanman auth work. For more info see: http://www.heise.de/ct/hotline/Samba-DOS-Client-zickt-1172774.html On the clients, please edit the line in MS Client's SYSTEM.INI workgroup=WORKGROUP to have the same workgroup name as in smb.conf. I use the full redirector, so in SYSTEM.INI the line is preferredredir=full Also on the clients, please edit the line in MS Client's SYSTEM.INI username=USERNAME to point to the user configured in Debian and Samba. Now reboot the DOS machine with the new user configured. If you start MS Client f.i. by typing net view, it will automatically ask you for your password and store it in the users password list file (*.pwl). You can now connect the FreeDOS machine to your Samba server by typing net use I: \\NAMEOFSERVER\SHARE and have the Samba share mapped to drive I: on the client. I just tested it and it works for me. regards Ulrich -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
Pardon the intrusion from my unexperienced self, just a few questions On Sat, Jun 16, 2012 at 8:59 PM, Ulrich Hansen uhan...@mainz-online.de wrote: I have read that MS Client with MS DOS works OK for you. But if you want to stick with Free Software, why not use a real Samba server together with the FreeDOS/MS Client clients? A Pentium 1 should be enough for that. Download for instance Debian Stable from here: http://cdimage.debian.org/debian-cd/6.0.5/i386/iso-cd/debian-6.0.5-i386-netinst.iso Eek, 191 MB, and that's not even everything, is it?:-( and when it comes to step Software selection choose File server. This will install Samba. Don't install a desktop environment. Excellent details, even better if it actually works! ;-) But does Debian run on i386 [sic] anymore? I thought most people had (unfortunately) switched to i686 (CMOVxx), e.g. Fedora. Or is Debian more lenient?? Even if the cpu instructions themselves are compatible (no CMOVxx, which Pentium 1 lacks), you may not have enough RAM. I don't know for sure, but everything I had read always seemed to hint that a Pentium typically couldn't have more than 64 MB, so trying to cram a recent Debian might be a bit of a stretch, to say the least. I have no idea of a better solution, unfortunately, only a blind guess that maybe?? Slackware 11.0 (circa 2006), aka ZipSlack, might work? At least it's easy to install atop DOS (kernel 2.4.x) and is only 67 MB .ZIP'd. I'd assume it has lower RAM requirements. Though it's not a full install by any means, but you can add on any extras you need (supposedly). ftp://ftp.slackware.com/pub/slackware/slackware-11.0/zipslack/ Well, hopefully everything Ulrich said will just work without worrying about all this extra stuff. Good luck! -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
Hi Marcos :-) - General failure reading drive C - LBACache error - Disk is write protected - Not ready reading drive G ... the internet they never had any issues with networking, except when the client was trying to cache writes -- which is not my case, as I only use UIDE or LBACache. Did you try using only UIDE or only LBACache for caching? If you use UIDE, did you try BIOS mode so it only caches but does not provide UDMA I/O? And have you tried using higher STACKS settings? As far as I remember, LBACache also had an option to provide more stack - but I probably made that the default and removed the option? Read docs ;-) The only difference I can think of between the previous networks that worked well for years and today's is that the former were used basically by a doctor at the office and his/her assistant at the reception desk -- a light load on the system -- whereas this week we tried to use both machines very intensively. Maybe it just never really worked with concurrent access to the database, but doctor and assistant did not happen to trigger problems... As a temporary workaround I wrote MODE con rate=1 delay=4 Interesting trick ;-) I did countless changes of parameters, including the more obvious such as the FILES line, and many others in a trial-and-error basis, in fdconfig.sys. fdauto.bat, protocol.ini, and system.ini. The latter two belong to MS-Client. I tried running with Himemx only (without jemm386/jemmex) and loading everything low. You could also try XMGR instead of HIMEMX, just in case. I think RealTek RTL8139 is nicely PCI Plug n Play, but not using UMB is always worth trying, I agree on that. Note that loading stuff low is not the same as having no UMB at all, e.g. by excluding all / loading no EMM. Otherwise your apps might still use UMB for things. My SHARE line in fdauto.bat is: loadhigh C:\FDOS\BIN\SHARE.COM /L:40 /F:4096 Note that there are multiple free versions of SHARE, possibly involving Tom and/or Japheth. I think there is a version with improved compatibility with s.th. on Japheth's homepage, for example? But it probably is a good idea to use SHARE in general, if it works? Eric -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
Marcos, As far as networking is concerned, I abuse my older machines all of time. I don't think you have a networking problem; I think it is a hardware problem, or very bad device driver settings. General failure reading drive C is a bad sign. I would make a new backup of that server hard drive (do not overwrite an existing backup in case the backup fails mid-way). After getting a good backup, I would try to dump the SMART data on it and run some benchmarks or diagnostics. If the hard drive is having a hard time reading data then all sorts of secondary errors can happen as a result. Next is to inventory and review all of the hardware in the computer and make sure none of it is in conflict. Have a sound card? Pull it out ... you don't need it in a server. Check the BIOS settings. That machine has to be absolutely stable before you start adding clients to it. What OS are you running? If you are running some early form of Windows, then ditch it. You can do better with a current (or recent, but not new) Linux running with a text console. My old Linux boxes share using SAMBA just fine, and Linux is robust and easier to diagnose when hardware or software is misbehaving. Next, you need to start testing the clients and the servers together. It's hard to imagine that the clients are putting such a huge load on the server that the server is glitching - file sharing is not CPU intensive. But you want to do this in a test environment, not with the real database that everybody is using! Setup some batch files to copy and compare files to ensure that the files are not getting corrupted and to generate some load against the server. Remember, a low end Pentium machine can easily saturate a 10Mb/sec Ethernet by itself. That's almost 1MB a second of file transfer capability if you are using TCP/IP. If you have Pentium gear you probably have 100Mb/sec hardware, so that number is closer to 10 times more. Are your clients accessing this database really generating 1MB or more of data per second? I'd be interested to hear your results. Mike -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
Marcos: So where exactly is the file server that's storing the data file(s) in this scenario? Is it on the doctor's PC, assistant's PC, or some other location? -- View this message in context: http://old.nabble.com/Networking-tp34020890p34021413.html Sent from the FreeDOS - User mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
At 07:14 PM 6/15/2012, Marcos Favero Florence de Barros wrote: If all goes well, technicians from the municipality will run the network cables in the building for us. But we don't want them to start drilling walls and roofs before we are sure the system is robust. I haven't touched DataPerfect for 14 years and back then, it was a data conversion of existing DP database files into some other data format. What I remember and at least the available DP manuals also state is that DP is using the very basic DOS (un)lock file region call of DOS 3.0+ to allow concurrent access to the same database on a network. That would be specifically INT21h/AH=5Ch, and that call needs to be properly supported in FreeDOS to begin with. Any file caching software should not touch access to networked drives (on the clients) and on the local machine that acts as server, it needs to be aware of the locking call and act accordingly... Ralf -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] networking software
Garrison Ricketson wrote: ... years back, like 15,or 16 years ago, I did connect my laptop, the early, Tandy, ...I dont remember the whole name,... As Ulrich Hansen already wrote, this might have been the program laplink and Norton Commander provided a similar function. Both programs are commercial products. Just for the sake of completeness: As far as i know, there also is a special packet driver, named plip, which provides networking functionality via the parallel interface. For a simple file transfer this might be overkill, but if more networking (or even TCP/IP) capabilities are desired then it might be worth considering. ___ Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
themouse wrote: Hello, I have the internet card and the drivers. So now what. I looked up all I could and there are alot of sites some the link works some they don't. I'm not really sure what needs to be done. thanks, Adam -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user For me worked the following: 1) Run the file crynwr.bat inside the directory FDOS 2)As suggested by Eric Auer configure the file WATTCP.cfg file as follows: my_ip = dhcp netmask = 255.255.255.0 gateway = 0.0.0.0 domain_list = your.domain.com # domain, gateway, ip, nameserver will be set via DHCP -- View this message in context: http://www.nabble.com/Networking-tp22775948p22777984.html Sent from the FreeDOS - User mailing list archive at Nabble.com. -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
1) Run the file crynwr.bat inside the directory FDOS If you've already installed the network driver in autoexec.bat, just skip that. 2)As suggested by Eric Auer configure the file WATTCP.cfg file as follows: my_ip = dhcp netmask = 255.255.255.0 gateway = 0.0.0.0 domain_list = your.domain.com # domain, gateway, ip, nameserver will be set via DHCP After creating WATTCP.cfg, set WATTCP.CFG=\path\to\file to point to it (in autoexec.bat) -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
Hi Adam, If I understood correctly, you are using a Lifebook 770tx with PCMCIA-Slot. So which card did you buy? Which PCMCIA software do you use to enable the card? And what kind of network do you want to use? Surf the web and email with arachne, connect to ftp and ssh servers, set up your own ftp-server? Then you need to get TCP/IP networking up and running. Or do you want just to share files with some Windows PCs in your workgroup? Then you may like to give Microsofts MSClient a closer look. Maybe you want to do both? So for instance: I use the D-Link DFE-670TXD Fast Ethernet PCMCIA Card, which comes with a packet driver for TCP/IP networking in DOS. I use SystemSofts CardSoft Software for enabling PCMCIA. This was included with my laptop once. It can be received f.i. at driverguide http://www2.driverguide.com/uploads/uploads9/26188.html (You need to register and avoid the many ads in the process, sorry. Maybe you find better sources) So in fdconfig.sys I start socket services: DEVICEHIGH=C:\NETWORK\PCMCIA\SSVLSI.EXE I start card services: DEVICEHIGH=C:\NETWORK\PCMCIA\CS.EXE I let the driver allocate memory, IO port and IRQ (modifications can be done in csalloc.ini): DEVICEHIGH=C:\\NETWORK\PCMCIA\CSALLOC.EXE In AUTOEXEC.BAT I load the packet driver that came with the above PCMCIA card: LH C:\\NETWORK\PCMCIA\DFE670\DFE670PD.COM 0x60 5 0x300 If you don't have a packet driver for your card, you need other drivers that can be made to behave as packet drivers. This means you need a NDIS or an ODI driver. ODI drivers are typically located at a directory called netware, nwclient, ODI or VLM on your PCMCIA drivers disk. NDIS drivers are located f.i. in a directory called NDIS2 and have the ending *.DOS. If the driver is loaded, I have to configure my network settings. This is done either in each network application itself or in a file called WATTCP.CFG which should be in your path and is used by the many network apps that have the free WATTCP kernel built in for networking. For more detailled information about TCP/IP networking in DOS look up http://lazybrowndog.net/freedos and go to chapter 3. Practical Guide: Adding TCP/IP to DOS. Best wishes Uli usul schrieb: Hello, I have the internet card and the drivers. So now what. I looked up all I could and there are alot of sites some the link works some they don't. I'm not really sure what needs to be done. thanks, Adam -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
Uli, I bought ORiNOCO Classic Gold PC Card. http://www.orinocowireless.com/products/wifi/client/goldpccard/index.html I know wireless is a risk but I checked in the documentation it had dos and linux drivers :) and I downloaded the ISO with all of that on it. the iso has several directories \driver \ODI \packet Just not sure how to set it up. I want to, ftp, telnet, browse the web with arachne, SVN when I port the commandline client. etc. Copy files from my windows network at home would be nice, but that would take secondary to the ftp and telnet. Are there any telnet and programs for freedos? I am assuming that wget is the ftp. Oh and I would probably want to be able to read and post to newsgroups and this mailing list. But I can do that from another pc that i usually have next to me. but it would be nice to have a complete evironment. lots of stuff in there and I am unsure of what is what. I have been spoiled by windows and linux LOL. I see alot of things on the web links for PPP etc. Things that sound familiar, but I no longer remember what they are. When I get home tonight after work I will try and comprehend all the help I got here and get it working. -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
usul schrieb: Uli, I bought ORiNOCO Classic Gold PC Card. http://www.orinocowireless.com/products/wifi/client/goldpccard/index.html I know wireless is a risk but I checked in the documentation it had dos and linux drivers :) and I downloaded the ISO with all of that on it. Well, wlan is nice but... Only 1 mbit and are you sure you can encrypt it with something secure like wpa or do you have a hotspot anyway? Note that many internal network cards in modern computers still have some compatible packet driver, just need to find it. the iso has several directories \driver \ODI \packet Just not sure how to set it up. I want to, ftp, telnet, browse the web with arachne, SVN when I port the commandline client. etc. This will be easy after the packet driver is working. For most simple things like arachne you just need the packet driver to work and dhcp at your router (mostly is default). Copy files from my windows network at home would be nice, but that would take secondary Then you need msclient, a memory hog. Dunno if novel netware is compatible but I rather think them implemented their own thing. to the ftp and telnet. Are there any telnet and programs for freedos? Someone else need to answer, there is sshdos. I am assuming that wget is the ftp. wget is for http(s) and ftp(s?) download Oh and I would probably want to be able to read and post to newsgroups and this mailing list. You can check http://www.unet.univie.ac.at/~a0503736/php/drdoswiki/index.php?n=Main.Browsers and see what you like. But I can do that from another pc that i usually have next to me. but it would be nice to have a complete evironment. lots of stuff in there and I am unsure of what is what. I have been spoiled by windows and linux LOL. I see alot of things on the web links for PPP etc. Things that sound familiar, but I no longer remember what they are. ppp is for dial up. -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
usul schrieb: But I can do that from another pc that i usually have next to me. but it would be nice to have a complete evironment. And I have forgotten to say... You are most likely much faster with browsing the web and mailing if you use a modern computer, modern multi tasking operating system and a modern browser / mail client. Sure it's a matter of taste, saying that on a DOS list is much leaning out of the window. I mostly boot to DOS and use Arachne for a quick research on the internet and if I think that booting Windows / Linux takes longer then the whole online session. Often I get bugged up by missing SSL support, slow speed and slow rendering and messed up websites so that I end up starting grub.exe, getting a coffee and booting Windows. Rather I would also say that you can develop way faster when using Linux / Windows most of the time and DOS in a emulator. Imho it's even more effective if you use a modern IDE. regards, -mr -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
If you're struggling to use Freedos to connect to the WWW, consider Damn Small Linux. It will fit on about anything that can run DOS, boots fairly quickly, and uses the capable Dillo browser. All this works on very modest hardware. You can then install Freedos into dosemu for a very nice dos environment to run your dos programs. --- On Mon, 3/30/09, Michael Reichenbach michael_reichenb...@freenet.de wrote: From: Michael Reichenbach michael_reichenb...@freenet.de Subject: Re: [Freedos-user] Networking To: freedos-user@lists.sourceforge.net Date: Monday, March 30, 2009, 2:02 PM usul schrieb: But I can do that from another pc that i usually have next to me. but it would be nice to have a complete evironment. And I have forgotten to say... You are most likely much faster with browsing the web and mailing if you use a modern computer, modern multi tasking operating system and a modern browser / mail client. Sure it's a matter of taste, saying that on a DOS list is much leaning out of the window. I mostly boot to DOS and use Arachne for a quick research on the internet and if I think that booting Windows / Linux takes longer then the whole online session. Often I get bugged up by missing SSL support, slow speed and slow rendering and messed up websites so that I end up starting grub.exe, getting a coffee and booting Windows. Rather I would also say that you can develop way faster when using Linux / Windows most of the time and DOS in a emulator. Imho it's even more effective if you use a modern IDE. regards, -mr -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
I am testing a few Linux OSes to see what works best. Tried Tiny, DLS-N, Puppy so far. :) Just a matter of seeing which one likes the linux driver the best. And looks better, I don't really like the look and feel of DSL. Trying a flux based puppy tonight :) But yeah I was thinking that I would cheat for some of the stuff for developing on FreeDos at first but later I would try and do everything I could inside. Adam -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
usul schrieb: But yeah I was thinking that I would cheat for some of the stuff for developing on FreeDos at first but later I would try and do everything I could inside. Cheat? Which kind of? Because you are not doing everything on pure DOS this makes your development more worse? That's s strange mind. -mr -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
mr, Because you are not doing everything on pure DOS this makes your development more worse? That's s strange mind. :) I'm strange I admit that but thats not whyI think it would be cheating, you are coming from the wrong angle. If I am immersed in the environment, then its better because the things that don't work or become cumbersome get identified and fix, worked around improved. :) Cheating was a bad choice of words and prob an even worse attempt at humor. usul -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
usul schrieb: I want to, ftp, telnet, browse the web with arachne, SVN when I port the commandline client. etc. A ftp-server for DOS that works reliable for me is ftpsrv32.exe from the wattcp32 package available at: http://www.filegate.net/utiln/utilnet/wt32apps.zip Its not secure at all (anonymous login only) but thats OK for exchanging files with other machines in the LAN. I access the server with filezilla in XP. In the filezilla settings I have to set the login to anonymous, server type is default (autodetect) and the possible connections at the same time are limited to 1. The zip above contains a lot of other useful programs like tftp and a smtpsrv. There are more apps available, f.i. here: http://jumpjet.info/DOS_Lives/03/Network.htm Uli -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
Ok, now I got your point and must agree. :) -mr usul schrieb: mr, Because you are not doing everything on pure DOS this makes your development more worse? That's s strange mind. :) I'm strange I admit that but thats not whyI think it would be cheating, you are coming from the wrong angle. If I am immersed in the environment, then its better because the things that don't work or become cumbersome get identified and fix, worked around improved. :) Cheating was a bad choice of words and prob an even worse attempt at humor. usul -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking
Ulrich Hansen schrieb: A ftp-server for DOS that works reliable for me is ftpsrv32.exe from I forgot to mention Datalight Sockets again, which is a FTP server that runs as TSR in DOS. See the mail at: http://www.unet.univie.ac.at/~a0503736/php/drdoswiki/index.php?n=Main.Servers And by the way: Michael Kostylevs port of GNU/Linux smbclient can be found here: http://www.glennmcc.org/download/mik/ It accesses shares at Windows and Linux machines from the command line with: smbclnt.exe \\server\share -U Username Password Uli -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking Freedos
Alain M. wrote: I have already done this for Kqenu (the accelerator for Qemu) which is also non-distributable. a. As of version 1.3.0pre10 KQEMU is released under GNU GPL v2. b. Do you mean, that you made a KQEMU port for use in plain DOS? Robert Riebisch -- BTTR Software http://www.bttr-software.de/ - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking Freedos
Hi Eric! There is a DOS version of the Linux smbclient, a FTP style Samba / Windows network neighborhood client... Sorry, I can't find it. So far I only found the following links: A port of the SMB library by Richard Sharpe, GNU GPL: http://www.bgnett.no/~giva/misc/dossmb02.zip I read on Club DR-DOS Wiki about a DJGPP port of Mplayer which should have this feature: Input: ftp dvdread(external) smb network Unfortunately the site http://mik.mkw.ru/dos-stuff/ is down. Maybe this info from OpenAFS could be useful? http://stuff.mit.edu/afs/dev/user/amb/openafs/src/TechNotes-WIN9X snip--- The main program of the Win9x client, afsd.exe, is implemented as a 32-bit DOS program. It is compiled using the DJGPP compiler and runs in a Windows 9x DOS virtual machine. [...] The Windows AFS clients communicate with user applications using the SMB protocol, as described above. SMB communication is done using the Netbios interface. In Win32, there is a built-in function Netbios() which accomplishes this. In a DOS program, however, this function is unavailable. However, Netbios functionality is available in the BIOS by calling interrupt 0x5c. The NCB (Netbios Control Block) and data buffer must be in conventional DOS memory, i.e., below 1 MB. This memory can only be accessed in DJGPP by using the DOS memory access functions: dosmemget(), dosmemput(), _farpeekX() and _farpokeX(). [...] -snap-- It WOULD be nice to have a driver which keeps running, but afair, the current Watt32 stack is just a library which is loaded each time when you start a program compiled for Watt32 use. The problem here is that this means that the config has to be processed each time. Maybe somebody could modify Watt32 so that it allocates some shared area of DOS memory to store the current config? Maybe the developers of WatTCP/Watt-32 could answer this. http://tech.groups.yahoo.com/group/watt-32/messages/2617?viscount=-30l=1 There's also Trumpets freeware NTCPDRV kernel (no source). 2. Using a NDIS driver for TCP/IP networking (with DIS_PKT). This part is alledgedly very simple: I think it would be very good to write a free replacement for DIS_PKT! AFAIK DIS_PKT and DIS_PKT9 are already free (maybe the binary must show modification message restriction wouldn't be OK for Richard M. Stallman, but a fish is not as big as a Gnu ;-). ---snip from DIS_PKT9 ; DIS_PKT.ASM - Adapter provides Packet Driver v1.09 interface over ; NDIS. ; Version 1.07 18 May 1991 by Joe R. Doupnik, Utah State Univ. ; Version 1.08 9 Aug 1991 by Dan Lanciani, [EMAIL PROTECTED] ; Version 1.09 3 Nov 1991 by Joe R. Doupnik, Utah State Univ. ; Copyright (C) 1988 - 1991 FTP Software, Inc. ; ; This unmodified source file and it's executable form may be used and ; redistributed freely. The source may be modified, and the source or ; executable versions built from the modified source may be used and ; redistributed, provided that this notice and the copyright displayed ; by the exectuable remain intact, and provided that the executable ; displays an additional message indicating that it has been modified, ; and by whom. ---snap What's not free is NDIS3PKT (NDIS3NT, NDIS3CE) which provides a packet driver interface in Windows 9x/NT/CE. (f.i. if you want to run Arachne in a DOS Box.) Uli - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking Freedos
Hi Tom, thanks a lot for your answers! So on the driver side, PKT and ODI drivers fade out, which only leaves NDIS2. Which means we are stuck with MS Client / LAN Manager Client. Unless there is some new free networking software for DOS. Concerning applications, you mention that instead of using MS Client, applications could directly talk to NDIS. This would make things a lot more easier. At the moment I use MS Client's protman (PROTMAN.DOS, PROTMAN.EXE) to configure a) the NDIS driver of the card and b) the free DIS_PKT shim and then MS Client's NETBIND.COM to bind these two. Pretty complicated, just to use a NDIS driver as packet driver, just to use Arachne... Wishlist (it's nearly christmas, OK?) Let Arachne directly talk to the NDIS driver. Or better: Let there be a free external TSR TCP/IP kernel (stack) that communicates directly to the NDIS driver, so everything else could use this kernel. And, of course, a free DOS smbclient. ;-) Uli Tom Ehlert schrieb: The other idea is to write a free replacement for MS Client. I think this would be a big task, so let's ask: How urgently is it needed? this would be very nice and useful. OTOH noone is ever going to implement this, irrelevant how 'urgent' you'd call it. So we'll have to use use MS Client to access Windows/Samba servers for the next few hundred years. *Drivers*: How are other peoples experiences with modern network cards? So far I found a NDIS driver for *every* card, with the notable exception of DLINK cards. Solution is easy: avoid DLINK. Are there still packet drivers or at least ODI drivers included? some provide ODI, very few provide packet drivers. So generally you're left with DIS_PKT. Or is NDIS2 the only DOS driver left that is still supported by manufacturers? in general, yes. Then you need indeed at least PROTMAN.DOS, PROTMAN.EXE and NETBIND.COM or free replacements for these three files to get the network up. or teach your application to talk to NDIS directly (a bit more complicated then packet, but not really difficult either) But what, if they even stop to support NDIS2? then we are in trouble. fortunately this won't happen soon I mean, it is also pretty old, isn't it? younger then packet or ODI Instead: Couldn't we just get the network drivers from GNU/Linux to work under FreeDOS and to provide a packet driver interface? not really Tom - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking Freedos
Hi Ulrich, So on the driver side, PKT and ODI drivers fade out, which only leaves NDIS2. And packet driver over NDIS Which means we are stuck with MS Client / LAN Manager Client. Unless there is some new free networking software for DOS. this is unrelated. NDIS (or packet driver) is a network driver (layer 2) MS client is a protocol handler (layer 3/4), which is something entirely different Concerning applications, you mention that instead of using MS Client, applications could directly talk to NDIS. This would make things a lot more easier. At the moment I use MS Client's protman (PROTMAN.DOS, PROTMAN.EXE) to configure a) the NDIS driver of the card and b) the free DIS_PKT shim and then MS Client's NETBIND.COM to bind these two. Pretty complicated, just to use a NDIS driver as packet driver, just to use Arachne... Teach DIS_PKT to talk directly to NDIS, and you are done. probably easier (and much more useful) then teaching Arachne NDIS Wishlist (it's nearly christmas, OK?) Let Arachne directly talk to the NDIS driver. Or better: Let there be a free external TSR TCP/IP kernel (stack) that communicates directly to the NDIS driver, so everything else could use this kernel. Pointless. Noone will ever talk to this (hypothetical) TCP/IP kernel this millenium ;) And, of course, a free DOS smbclient. don't hold your breath ;) Tom - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking Freedos
Hi again, So on the driver side, PKT and ODI drivers fade out, which only leaves NDIS2. Which means we are stuck with MS Client / LAN Manager Client. Unless there is some new free networking software for DOS. ... MS Client's protman (PROTMAN dot DOS / EXE) to configure a) the NDIS driver of the card and b) the free DIS_PKT shim and then MS Client's NETBIND.COM to bind these two... ... Wishlist (it's nearly christmas, OK?) Let Arachne directly talk to the NDIS driver. Or better: Let there be a free external TSR TCP/IP kernel (stack) that communicates directly to the NDIS driver, so everything else could use this kernel. This would only help Arachne, not the rest. Why not write a free replacement for NETBIND and PROTMAN? I am sure only a fraction of their functionality is actually used to send configuration parameters to DIS_PKT. And Arachne and other DOS apps are happy with the packet driver side of DIS_PKT, so there is no need to teach them how to talk with NDIS directly. So basically I agree with Tom: Teach DIS_PKT to talk directly to NDIS, and you are done. probably easier (and much more useful) then teaching Arachne NDIS ... Pointless. Noone will ever talk to this (hypothetical) TCP/IP kernel this millenium ;) Eric - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking Freedos
Hi Ulrich, Thanks for the nice explanation, 2nd version. I would like to make a few comments. 3. To activate the hardware driver and the DIS_PKT converter we need other parts from the NDIS 2 universe: The Protocol Manager driver (PROTMAN.DOS, PROTMAN.EXE) and the Bind utility (NETBIND.COM). This is unfree software, the files are included in MS Client, LAN Manager and Co. Here I disagree. MS-Client is free software, even if not GPL or distributable. But it can be used along with free software: include a small batch-or-script that 1) downloads the original files with wget, 2) extract what is neeed, 3) once there, anyone can intenaly distribute his copies. This is legaly within the licence limits. I have already done this for Kqenu (the accelerator for Qemu) which is also non-distributable. I can send information to anyone that is interested in making a package of it. Yes, sorry, bad idea. WatTCP and Watt-32 are free and widely used TCP/IP stacks that work great against the packet driver interface. We (Andreas and I) have losta a lot of time with Watt-32, I recommend WatTcp which is small and fast. Unfornunatly WatTcp is 16 bits, I don't know if it is feasible to por it to WatcomC compiler. Alain - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking Freedos
Hi Alain, Alain M. schrieb: (PROTMAN.DOS, PROTMAN.EXE) and the Bind utility (NETBIND.COM). This is unfree software, the files are included in MS Client, LAN Manager and Co. Here I disagree. MS-Client is free software, even if not GPL or distributable. But it can be used along with free software: include a small batch-or-script that 1) downloads the original files with wget, 2) extract what is neeed, 3) once there, anyone can intenaly distribute his copies. This is legaly within the licence limits. Yes, sorry, I meant free as in FSF not as in free beer. I also think the above would be perfectly legal. It would be a good idea anyway if the user sees the license before he downloads MS software, at least when FreeDOS is involved (which he could assume to be free as in FSF). Another thought: The download of the MS files should be initiated with or directly after the *download* of the main software (bootdisk, network application, whatever) and NOT with the *start* of this software. Otherwise the user could be in a catch-22 situation (he'd have to download a file to be able to download files). We (Andreas and I) have losta a lot of time with Watt-32, I recommend WatTcp which is small and fast. Unfornunatly WatTcp is 16 bits, I don't know if it is feasible to por it to WatcomC compiler. This is an interesting point for me, as I am not a programmer and have no practical experience with these libraries - I only use them when they are already working in an application. Thanks for the inside view! Uli - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking Freedos
someone schrieb: Quoting Ulrich Hansen: The legal situation is unfortunate: Some packages seem to include files from MS Client, while Microsoft's license does not allow such distribution. How hard would it be to port Linux's TCP/IP stack to Freedos? Dos is supposedly a very simple, albeit limited OS. For some things such as kiosks though, a network booted dos would be very nice. As work on freedos 1.1 progresses I'd like to see a free replacement for Microsoft Client get developed. I hope there is careful consideration that dos's simplicity is it's strongest selling point. I'd like to write down a few ideas about it. I know here are people with *much more* experience in DOS networking and I am not a programmer as well. So please correct me, if I'm wrong. IMHO MS Client is useful for two things: 1. Accessing SMB shares from a DOS machine. 2. Using a NDIS driver for TCP/IP networking (with DIS_PKT). Everything else is already there, as free software or public domain: A TCP/IP stack (internal: WatTCP, Watt-32 (LGPL); external: NTCPDRV (PD)), packet drivers and packet driver shims, and last but not least a lot of useful packet driver based TCP/IP applications. The problem: MS Client's license permits you to make and use an unlimited number of copies [...] for your internal use. You may transfer the SOFTWARE on a permanent basis provided you retain no copies. So distribution is NOT allowed. There are two ideas to solve that problem. For creating network bootdisks, Alain M. suggested (in PM) to write a script that runs on the user side. As I understand it, this script would ask the user to accept MS Client's license and then automatically download the appropriate MS Client files from their original download location, expand them and merge them into the bootdisk. It may be comparable to PE Builder. This would respect the copyright. The other idea is to write a free replacement for MS Client. I think this would be a big task, so let's ask: How urgently is it needed? *Drivers*: How are other peoples experiences with modern network cards? Are there still packet drivers or at least ODI drivers included? Or is NDIS2 the only DOS driver left that is still supported by manufacturers? Then you need indeed at least PROTMAN.DOS, PROTMAN.EXE and NETBIND.COM or free replacements for these three files to get the network up. But what, if they even stop to support NDIS2? I mean, it is also pretty old, isn't it? Then FreeDOS had to write its own free drivers, like people do for GNU/Linux. Instead of NDIS, wouldn't it be better to write packet drivers then, which are already a free standard for DOS networking? So FreeDOS would need another packet driver king. That's a bit utopic. Or can GNU/Linux network drivers somehow be used in FreeDOS? *SMB*: I know everybody seems to be pretty enthusiastic on the web about MS Client and accessing and providing SMB shares from DOS to Windows XP or GNU/Linux Samba. Maybe everything worked well for them. I had a hard time with it. MS Client with TCP/IP protocol consumes a lot of memory, everything gets sluggish and if I want to make a DOS MS Client communicate with GNU/Linux Samba (from Debian Etch) I have to configure Samba in a way that we don't need to talk about security afterwards, as there isn't any left. So is this really worth the effort? Instead: Couldn't we just get the network drivers from GNU/Linux to work under FreeDOS and to provide a packet driver interface? DOSEMU emulates a DOS packet driver. And once Zipslack ran atop of DOS. Or is this a silly idea? And now I have to go and buy some nice christmas gifts or I will have a bad time next week... :-) Uli - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking Freedos
Hi Alain, thanks for your friendly feedback! Alain M. schrieb: I believe that you should add a refernce to www.netbootdisk.com because it is a very prectical way of putting it all toghether, including brand new MotherBoards ! Thanks for the suggestion. I made some changes to chapter http://lazybrowndog.net/freedos/#Applicatio I included the following lines and links: --snip-- Another special type of applications are network bootdisks, which combine several network techniques. These bootdisks are mostly used for backup, restore and repair. They can be extremely helpful. Examples are: * Bart's Network Boot Disk * Drivesnapshot * Netbootdisk The legal situation is unfortunate: Some packages seem to include files from MS Client, while Microsoft's license does not allow such distribution. --snap-- Is this OK? Uli - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] networking problem
There is a tutorial *somewhere* about how to install a new driver in the ms-client floppy so that instalation can be automatic!!! The sad thing is that I lost that link, if anyone has it, please send it here :) :) Alain Mikiya Matsuzaka escreveu: i try to use ssh2dos and work perfectly!!! the net is working, now i need to mount in FreeDOS a samba shared folder, and i don't know how to do that, i googled and i can get a answer, where i can find this info?¿ Here, http://www.ibiblio.org/pub/micro/pc-stuff/freedos/ftp.gcfl.net/pub/freedos/ms-clients/ and this. http://support.microsoft.com/default.aspx/kb/124175/en-us You also need NDIS driver. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] networking problem
For DOS networking stuff, I usually use Bart's Network Boot Disk: http://nu2.nu/bootdisk/network/ It connects to SMB shares, too. It's possible to use bits of it to setup networking on a HD install of DOS, too. I haven't done it for a few years so I can't be more specific, I'm afraid. -- Jack Alain M. wrote: There is a tutorial *somewhere* about how to install a new driver in the ms-client floppy so that instalation can be automatic!!! The sad thing is that I lost that link, if anyone has it, please send it here :) :) Alain Mikiya Matsuzaka escreveu: i try to use ssh2dos and work perfectly!!! the net is working, now i need to mount in FreeDOS a samba shared folder, and i don't know how to do that, i googled and i can get a answer, where i can find this info?¿ Here, http://www.ibiblio.org/pub/micro/pc-stuff/freedos/ftp.gcfl.net/pub/freedos/ms-clients/ and this. http://support.microsoft.com/default.aspx/kb/124175/en-us You also need NDIS driver. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] networking problem
There is a tutorial *somewhere* about how to install a new driver in the ms-client floppy so that instalation can be automatic!!! The sad thing is that I lost that link, if anyone has it, please send it here :) :) You could write what you've already done and what's the problem. And you will get more precice help. Copying all driver files (OEMSETUP.INF, ...) to ms-client extracted directory, and run setup, might solve the probrem. Remember you still choose [*Network adapter not shown on list below ...]. --- Mikiya Matsuzaka [EMAIL PROTECTED] - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] networking problem
thanks!! i go in to try, i am newbie in MS-DOS to :P, thanks for the info. Regards insulae 2007/6/13, Mikiya Matsuzaka [EMAIL PROTECTED]: i try to use ssh2dos and work perfectly!!! the net is working, now i need to mount in FreeDOS a samba shared folder, and i don't know how to do that, i googled and i can get a answer, where i can find this info?¿ Here, http://www.ibiblio.org/pub/micro/pc-stuff/freedos/ftp.gcfl.net/pub/freedos/ms-clients/ and this. http://support.microsoft.com/default.aspx/kb/124175/en-us You also need NDIS driver. --- Mikiya Mastuzaka [EMAIL PROTECTED] - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Juan Matias Granda http://www.insulae.com.ar GPG FINGERPRINT:459C 4A2D 330C CB8C 0C44 0C3A 572C CBCA 5457 508B - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
