Re: [Freedos-user] DOS ethernet drivers
I find it convenient to use a text-based browser for my local (inhouse) websites, which display data from my homebrew weather station, home heating system, and various sensors. It's very easy and fast to automatically generate small text oriented html files in my microcontrollers and write them to my local network. On Wed, Jan 20, 2021 at 6:04 PM Greg Gerke via Freedos-user < freedos-user@lists.sourceforge.net> wrote: > Well, yeah, granted - the website you're going to would have to be pretty > compliant in the standards of a 100 years ago but it might at least give > *something* back ;) > > --- > gge...@pm.me > > ‐‐‐ Original Message ‐‐‐ > > On Wednesday, January 20th, 2021 at 2:59 PM, Jose Senna > wrote: > > > Greg Gerke asked: > > > > > ...has anybody tried Lynx on FreeDOS ? > > > > I used it for quite a few years, but > > > > now Lynx is (almost) no good, because > > > > -No Javascript > > > > -Obsolete secure protocols > > > > -Incorrect renderizing of frames, tables > > > > -Few sites still provide pages suitable for > > > > text-mode browsers. > > > > Anyway, trying it will do no harm. > > > > 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 > -- It's all fun and games until someone divides by zero. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] (no subject)
Actually, I do use PLOP whenever I have my 2nd HD plugged in. It has Windows 2000 on it. Sometimes it's handy to use certain windows programs like Disk Management, but mostly I just leave it disconnected and use FreeDos. On Fri, Jan 8, 2021 at 5:12 PM Andrew Robins wrote: > *EDIT: USB2.0 ports via PCMCIA adapter, I mean. > > > > On Sat, Jan 9, 2021, at 8:07 AM, Andrew Robins wrote: > > You might like to consider using Elmar Hanlhofer's "Plop" boot manager > https://www.plop.at/en/bootmanagers.html to assist with booting from your > native USB1.x port. It helps with working around early BIOS versions that > did not permit /enable booting from USB as an option. (Have you checked you > bios to rule this part of the problem out?) However, if you have USB ports > via a PCMCIA adapter, you may have additional struggles with compatibility. > Elmar lists PCMCIA compatibility as 'limited', but I have not had any > success using PLOP to boot from USB. > HTH > > > > > On Sat, Jan 9, 2021, at 2:47 AM, Marv wrote: > > For what it's worth, I'm using a 1998 Intel 440BX machine. It has a > Pentium II. The network adapter on the motherboard works fine, also serial > and parallel ports. The only issue I have is the USB port is non-bootable. > The CD drive is bootable but it is not compatible with FreeDos. I had to > install FreeDos by copying the necessary files to a separate partition on > the HD. I transfer files to and from it mainly over the network, but > sometimes with the 1.44MB floppy. > > > On Fri, Jan 8, 2021 at 11:30 AM Šimon Dobeš > wrote: > > Hello > I want to ask if FREEDOS will run on Intel Pentium old-school PC from 2002 > and if it will work properly if this pc have 256 mb of ram. > I have a old IBM ThinkPad from 1998 and it is great computer. But it is > not working. Where I can fix it? > Thx > Simon > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > > > > -- > It's all fun and games until someone divides by zero. > > > ___ > 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 > -- It's all fun and games until someone divides by zero. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] (no subject)
For what it's worth, I'm using a 1998 Intel 440BX machine. It has a Pentium II. The network adapter on the motherboard works fine, also serial and parallel ports. The only issue I have is the USB port is non-bootable. The CD drive is bootable but it is not compatible with FreeDos. I had to install FreeDos by copying the necessary files to a separate partition on the HD. I transfer files to and from it mainly over the network, but sometimes with the 1.44MB floppy. On Fri, Jan 8, 2021 at 11:30 AM Šimon Dobeš wrote: > Hello > I want to ask if FREEDOS will run on Intel Pentium old-school PC from 2002 > and if it will work properly if this pc have 256 mb of ram. > I have a old IBM ThinkPad from 1998 and it is great computer. But it is > not working. Where I can fix it? > Thx > Simon > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- It's all fun and games until someone divides by zero. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOS software
Hi Ray, do you have any books on x86 assembly? Thanks, Marvin On Wed, Dec 30, 2020 at 3:30 PM Ray Davison wrote: > I will keep DOS running primarily for accounting and word-processing, > because none of the "modern" apps have given me reason to change. > > However, I have about fifteen linear feet of software and third party > books that I may have used but mostly acquired because I thought it > might be useful someday - including a two pound, still skin-packed, > package to connect DOS to a 3270. > > I need the shelf space. Does this stuff have any use to anyone? > > Ray > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- It's all fun and games until someone divides by zero. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Question about FDAPM
Thanks Eric! I had noticed that FDAPM POWEROFF did both a flush and spindown, but after a couple of seconds it says "Warming up...Back...Back on..." so I wasn't quite sure what it had done. In any case, it sounds like I should be ok holding down the power button at that point. This particular laptop has a very minimal bios, at least the part I can access. On Sat, Dec 26, 2020 at 10:43 AM Eric Auer wrote: > > Hi Marv! > > FDAPM FLUSH (no slash needed) does not rely on the BIOS, > it is just meant to give caches hints to write back all > pending writes. Note that none of the caches shipping > with FreeDOS will pool or delay writes, so you actually > do not need to flush with those :-) > > As soon as the last app returns to the prompt, you can > expect that DOS has written all data and closed files. > > The flush command should work for the following caches: > msclient (not a cache, but network drives), CD Blitz, > PC-Cache, QuickCache, Super PC Kwik / QCache, SMARTDRV. > It also tells DOS and BIOS disks to reset some state. > > The latter could help to make sure that things are > written from the built-in cache of your SD card to > the permanent storage of that card. I would expect > most drives - including SSD and SD ones - to default > to not delay writes unless you enable that? And how > long would such delays be at most? Are there rules > about it? Or experiences here on the list? > You could use the SPINDOWN command to tell disks/SD > to shut down - that should give them a hint to flush > their built-in caches :-) Actually, FDAPM POWEROFF > implies flush and spindown anyway. > > Regards, Eric > > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- It's all fun and games until someone divides by zero. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Question about FDAPM
One of my FreeDos machines is a laptop without APM. The only way to shut it down is to hold the off button for several seconds. That is not my preferred way of doing things. Some FDAPM commands seem to work (meaning I don't get any error msg) without the computer having APM, for example, FDAPM /FLUSH. So, I've gotten into the habit of doing that before holding down the off button. But does FDAPM /FLUSH really work in my case? I haven't had any problems that I know of so far. In particular, I'm concerned about the 32GB SD card I use for transferring files back and forth to my Windows machines. -- It's all fun and games until someone divides by zero. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Microsoft 8086 Assembler
The other day I decided to do some experimenting with the parallel port on my FreeDos machine, so I built an adapter with 8 LEDs connected to the output bits. It didn’t take too long to figure out how to turn the LEDs on/off using QBASIC. But I wanted to get a little closer to machine level control over the port. I decided to go with Microsoft’s MASM 6.11. Apparently, it was the last version that ran on MS-DOS. I liked the fact that it came with a lot of reference documentation. I did install it on my FreeDos 1.3 machine and get it working. I’ve been able to turn the parallel port bits on and off, etc. I installed MASM before I realized there are a couple of assemblers listed on the FreeDos software page. The Flat Assembler seems especially well supported. Is anyone here familiar with FASM? MASM is probably overkill for my purpose and like many other Microsoft products, their support for it is mainly reference material for experienced programmers. http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/pkg-html/fasm.html -- It's all fun and games until someone divides by zero. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] What do you do with your FreeDos PC?
I'm running FreeDos on an old Pentium server that came with Windows 2000. I wanted to keep W2K, so I installed FreeDos in a partition. I use PLOP on a diskette to boot to either W2K or FreeDos. I wanted to install Linux on it just for fun, but haven't been able so far. This old beast has a USB input but BIOS can't boot from it. It has a CD which is bootable but Linux is too big and needs a DVD. So, I tried several ways to install Linux from a hard drive but had no success. It's no big deal. I do have 2 Linux servers running in my home computer/radio room. One handles my home automation and weather station. The other is a file server. I also have a laptop running Linux Mint, which can do a lot of things and is even user friendly. But I have other software that only runs on Windows, so I have a desktop and another laptop for that. I was thinking of using the FreeDos PC in some network server capacity, but I had forgotten how loud the fans are in these old Pentium machines. I did replace the main cabinet fan with a quiet one, but the CPU and power supply fans are way too loud. I guess that's just part of the retro experience, but it doesn't do much for marital bliss when my wife has to yell at me to be heard. On Fri, Dec 4, 2020 at 4:06 PM dmccunney wrote: > On Fri, Dec 4, 2020 at 3:19 PM Marv wrote: > > > > I know I'm late to the FreeDos party, but it would help me and maybe > other newcomers to know what you guys do with your FreeDos PCs. I was > thinking of utility type things that are easier or more quickly done in > DOS, but I'm wide open to any ideas. > > > > So far I've got programs like Supercalc, Wordstar, GWBasic, DBase, etc > working. I transfer files back and forth to my Windows PC using FTP over my > local network. > > I'm odd man out, as I don't currently have a dedicated FreeDOS PC. > > I originally installed FreeDOS in a multi-boot setup on an ancient > notebook. The machine was a pass-along from a friend who had upgraded > but didn't want to see it thrown out. It was a Fujitsu p2110 > machine, the a Transmeta Crusoe CPU (and early attempt at a power > saving design, a 30GB IDE4 HD, Intel graphics on the motherboard, and > a whopping 256 *MB* of RAM. The Crusoe CPU grabbed 156MB off the top > for "code morphing", there were 240MB usable. She said it was "Slow, > slow, SLOW." Well, yes. It came to me with WinXP SP2 installed. XP > wants 512MB *minimum*. It took 8 minutes to simply boot, and much > longer to do anything once up. > > I pulled the 30GB HD, swapped in a 40GB model from a failed laptop, > and started hacking. I reformatted and repartitioned the HD, with a > 20GB slice formatted as NTFS with Win2K on it, tow 8GB slices > formatted as Linux ext4 with Ubuntu and Puppy Linux, a 2GB slice for > Linux swap, and a 2GB slice formatted FAT32 for FreeDOS. > > *Getting* it to boot FreeDOS was an involved process. I have no idea > which of the config tweaks I made actually did the trick, but I had a > machine that could boot Win2K, Ubuntu Linux, Puppy Linux, and FreeDOS > from a Grub2 menu. Win2K actually more or less ran in 240MB ram, > after I removed everything from Startup that *could* be removed, and > disabling Windows Update (since it would no longer *get* updates That > saved me a SVCHOST.EXE process and 10MB RAM.) Ubuntu and Puppy also > more or less ran. (Puppy was designed for old hardware, and Puppy > itself ran well. Linux *applications* installed were another matter.) > FreeDOS *flew.* > Linux could read NTFS vis NTFS3g, Win2K could read extfs via an open > source driver. Everything could read FAT32, but FreeDOS couldn't read > anything else. I had no need to and didn't care. > > A problem that required reinstalling Wn2K broke the multiboot and I > couldn't get it to work again. I didn't care. The process had been > an experiment to see what performance I could coax out of ancient > hardware without throwing money at it. It was fun to try and I learned > things, but the real work was done elsewhere, so losing the machine > wasn't an issue. > > These days I run Win10 Pro on a refurbished HP SFF desktop with a > quad-core Intel i5 CPU, Intel HD4600 graphics, 20GB RAM, and OS and > programs boot from and live on a 256GB SSD. > > I still have an assortment of DOS applications, and run them using a > DOS port of the DOSBox MSDOS gaming emulator, or the vDOS fork of > DOSBox specifically aimed at supporting character mode DOS > productivity applications. I do so to flex mental muscles and keep my > hand in. It's a hobby activity done for fun. Actual work happens on > the Windows side, and most of that simply can't be done in FreeDOS. > > (I also have some old DOS apps running on an Android tablet courtesy > of an Android port of DOS
[Freedos-user] What do you do with your FreeDos PC?
I know I'm late to the FreeDos party, but it would help me and maybe other newcomers to know what you guys do with your FreeDos PCs. I was thinking of utility type things that are easier or more quickly done in DOS, but I'm wide open to any ideas. So far I've got programs like Supercalc, Wordstar, GWBasic, DBase, etc working. I transfer files back and forth to my Windows PC using FTP over my local network. -- It's all fun and games until someone divides by zero. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] CDROM Driver
Followup to my post this morning about swapping out the Sony CD drive for an AOpen DVD drive. The new/old (circa 1998) AOpen 1648 came in its original box with paperwork. No mention of installing a driver anywhere in the manual, which explains why I couldn't find a driver for it online. It obviously just uses a standard Microsoft CDROM.SYS driver. In fact, it worked fine with Windows 2000, no complaints or messages. So then I rebooted to FreeDos, which still had the Sony driver I found that worked with it. No messages or complaints there either. The DVD drive works fine under FreeDos using the old Sony driver. Being a glutton for punishment, I had to switch back to the UDVD2.SYS driver that came with FreeDos 1.3 install ISO and see what happened. Well, just like the Sony CD drive, this AOpen DVD drive is recognized and a drive letter is assigned, but it doesn't work - sort of hangs. In any case, all is good. Now I have a working DVD drive under both Windows 2000 and FreeDos. On Fri, Nov 20, 2020 at 10:46 AM tom ehlert wrote: > > > Remember that it was normal that CDROM drives shipped with > > DOS drivers in the past. > > this is true. and each manufacturer took care to only support > it's own drives. until later someone showed that IDE-CDROM drivers are > inherently universal. > > UDVD and vide-cdd.sys https://www.hiren.info/downloads/dos-files > > https://www.uwe-sieber.de/util.html has 3 more > > > It is a challenge for UDVD2 to be > > universal, but it will still find most CD/DVD drives :-) > > nope. that's simply not true, and I'm really surprised that UDVD2 > doesn't work where another driver does. > > DVD drivers are inherently universal, unless a manufacturer puts > > if (manufacturer != "SONY") >exit(); > > style code into it's driver > > Tom > > > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- It's all fun and games until someone divides by zero. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] CDROM Driver
Hi Eric, it's connected to the IDE controller (2nd) on the motherboard (Intel Pentium II 440BX). The UDVD2 I was using is dated 3-5-2015. Looks like it's version 2.0c. It was packaged with the FreeDos 1.3 Live CD I used for my installation. More excitement later today... I'm going to try replacing the Sony CD drive with an old AOpen 1685 DVD drive. Not necessarily for FreeDos but for Windows 2000 which I have running on a 2nd hard drive. I needed it to hopefully install Linux in the 2nd partition on that 2nd drive. For now, FreeDos is the only OS I plan to have on my 1st hard drive. On Fri, Nov 20, 2020 at 9:28 AM Eric Auer wrote: > > Hi! That looks like a normal IDE / ATAPI drive to me according > to online specs. Is it connected to the normal IDE controller > on your mainboard or to some sort of separate controller? Which > version of UDVD2 do you use, is it up to date? See for example > > http://mercurycoding.com/downloads.html#DOS > > (drivers zip might be newer than the individual zips?) > > Remember that it was normal that CDROM drives shipped with > DOS drivers in the past. It is a challenge for UDVD2 to be > universal, but it will still find most CD/DVD drives :-) > > Regards, Eric > > > ... I got to wondering about using a different driver instead of the > > UDVD2.SYS that FreeDos was using. So I found an old 1998 driver for my > > Sony CDU4811 CDROM. Low and behold the CD now works fine in FreeDos. > > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- It's all fun and games until someone divides by zero. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] CDROM Driver
As I mentioned in an earlier post, I installed FreeDos from my hard drive, because my old PC couldn't boot from usb and FreeDos didn't like my CD drive. And of course, FreeDos couldn't use the CD even after it was up and running. Yesterday I got to wondering about using a different driver instead of the UDVD2.SYS that FreeDos was using. So I found an old 1998 driver for my Sony CDU4811 CDROM. Low and behold the CD now works fine in FreeDos. Being a noob when it comes to FreeDos, I have to ask if this typical with CDROMs? I'm not complaining. I understand the installation process can't work with every PC configuration for the past 20+ years. -- It's all fun and games until someone divides by zero. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Printing from FreeDos
After more research and more fooling around, I am now able to print from FreeDOS to my network WiFi printer. Just to clarify a couple of points - my FreeDOS PC is connected to my home network through an ethernet cable to my router. My free-standing laser printer is connected to my home network through WiFi to my router. I'm using lpt2file.com to redirect lpt1 to a text file on my FreeDOS PC. Then I'm using jd.exe to send the text file directly to my printer's IP address. Works fine with pure text files. I'm sure any special formatting codes in the text other than LF/CR, etc would confuse the printer. It does eject a short page automatically, no extra form feed needed. On Thu, Nov 19, 2020 at 9:26 AM Eric Auer wrote: > > Hi Marv! > > So you have a serial port on your DOS PC and on your Windows PC, > a network-only printer and maybe, or maybe not a LPT1 port on the > DOS PC (physically). To print directly over the network, you can > try some trickery with netcat. Some printers might also create a > built-in website which lets you upload printing data. Even if you > only use the network to send the data to Windows, raw or via FTP > or other protocols, you may enjoy the extra speed for non-text? > > Serial ports can often go above 115200 baud today, if cables are > short enough. We have a SMBCLIENT port for network drives, but it > only supports older versions. Not sure how old your Windows can go. > > I guess there is also some sort of hardware with a printer port > input on one side and the ability to forward data to wired or > wireless network or USB on the other side. Maybe others here on > this list can recommend some? > In general, if your printer supports PostScript or PDF, you can > use DOS tools to produce those. For example our GRAPHICS can do > PostScript ;-) I would not exclude the possibility that even a > wifi laser printer still supports plain text, why not? > > Regards, Eric > > > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- It's all fun and games until someone divides by zero. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Printing from FreeDos
Since I don’t have a printer with a parallel port, I’ve been redirecting LPT1 to COM1, which is connected to my Windows 10 PC at 115200 baud. Using a terminal program, I capture what I want to a file that I can either print or save on my Windows 10 PC. Clunky, but it works. It even works ok for something like hitting the PRT SC key to print the screen. But now that I have my FreeDOS machine working on my network, I’d like to find a better way to print. I can FTP into FreeDOS from my Windows 10 PC and retrieve a file for printing, but that’s almost as clunky as what I’ve been doing with my COM1 port. I’d like to find a way to redirect LPT1 to my network printer. I know I can’t do that directly, as I’d never be able to find a DOS printer driver for my network (WiFi) laser printer. Is there a way I could print to a shared printer on my Windows 10 PC from FreeDOS? -- It's all fun and games until someone divides by zero. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] USB Floppy
I was under the impression an external USB floppy wouldn't work under FreeDOS 1.3, but I just noticed my installation of FreeDOS 1.3 on a circa 2011 Gateway laptop with an external USB Chuanganzhuo floppy does work. I'm not sure what driver FreeDOS is using on the Gateway, but if I plug the floppy into my HP Windows 10 laptop, it says it's a TEAC USB UF1000x USB device using a default Windows sfloppy.sys driver. It was plug-n-play. I didn't install any drivers on either laptop. I didn't buy this floppy drive for FreeDOS. My main FreeDOS machine has a builtin floppy drive. I bought it to read some old floppies on my HP Windows 10 laptop. -- It's all fun and games until someone divides by zero. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Multi-Boot with Windows 2000 and FreeDOS
Thanks Robert - I read through the bootmgr.txt file and then gave bootmgr a try. The first hard disk is a 250GB SSD with (3) 32GB FAT32 partitions. The rest of the drive is unallocated because I thought I would install a Linux partition there later on. Windows 2000 is in the first partition, FreeDOS is in the second partition. The third partition is empty. I was planning on using it for data files.FreeDOS was installed after Windows 2000. I do have a second drive but have not set up bootmgr in it. The second drive does have a working FreeDOS installation that I can access if I go into my BIOS and swap drives, which is what I'm trying to avoid. That second drive doesn't have any other operating system in it. I included a link to a screenshot of my bootmgr setup. I think I have it right but maybe not? I setup 3 choices: FreeDOS, Windows 2000, and the floppy drive. FreeeDOS gets an error. Windows 2000 and the floppy boot ok. I'm getting basically the same kind of error I was getting with other multi-boot methods. When I try to boot FreeDOS, I get a message saying" NTLDR is missing" which tells me bootmgr is probably going to the right partition because FreeDOS doesn't have a NTLDR file, which of course Windows 2000 does have. http://allenthings.com/bootmgr1.jpg Marvin Allen On Sat, Nov 14, 2020 at 1:20 PM Robert Riebisch wrote: > Hi Marv, > > > I spent the last 3 days fooling around with several ways to set my > > Windows 2000/FreeDOS machine set up with a multi-boot menu. I tried GAG, > > Grub4Dos, and the boot.ini file that Windows 2000 uses. > > Many years ago I had the DOS/Win2000 combo working on a single drive > using our: https://www.bttr-software.de/products/bootmgr/ > The key is to hide unneeded partitions from the other OS. > See screenshot #2. > > Cheers, > Robert > -- > +++ BTTR Software +++ > Home page: https://www.bttr-software.de/ > DOS ain't dead: https://www.bttr-software.de/forum/ > > > ___ > 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] Multi-Boot with Windows 2000 and FreeDOS
Hey Tom - do you think Windows 2000 boot.ini is the best way to go for my particular setup? If you do, I'll give it another try and report my errors/messages. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Multi-Boot with Windows 2000 and FreeDOS
I spent the last 3 days fooling around with several ways to set my Windows 2000/FreeDOS machine set up with a multi-boot menu. I tried GAG, Grub4Dos, and the boot.ini file that Windows 2000 uses. Windows 2000 is installed on the 1st hard drive, 1st partition and is my primary/default system. FreeDOS is installed on the 2nd hard drive, 1st partition. Both operating systems boot and run ok if I swap drives in my BIOS, but that’s a hassle. GAG actually boots to FreeDOS ok one time each time I install it. Every time thereafter it boots to Windows 2000, instead of FreeDOS. I suspect the TSR program GAG uses to swap hard drives gets confused by Windows 2000. I did try installing FreeDOS to a partition on the 1st drive to avoid the TSR swap program, but then I ended up with Windows NT issues trying to boot to FreeDOS. I don’t have any NT issues with GAG if FreeDOS is on my 2nd drive. I don’t see much hope of getting Grub4Dos or Windows 2000’s boot.ini working with my configuration. Both methods keep getting tangled up in Windows NT issues. Does anyone have any thoughts or advice on setting up a multi-boot menu with my FreeDOS setup? At this point, I feel lucky that both operating systems still boot and run ok by swapping drives in my BIOS! -- It's all fun and games until someone divides by zero. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] PCI Express Network Adapter Board for FreeDos
Thanks - yes, I thought I would keep and use the smaller installation partition for recovery and future :) upgrades. It's not in the way of anything. I'll look into EtherDFS today. My main computer runs on Windows 10, which is always a challenge with sharing/permission rights due to builtin security. The others all run some type of Linux, which is easy to network. Marv On Thu, Nov 12, 2020 at 8:24 PM Jerome Shidel wrote: > > > On Nov 12, 2020, at 7:02 PM, Marv wrote: > > [...] > > > > I copied everything on the FreeDos 1.3 Live CD over to the 1GB partition > using Windows 2000. Then I disconnected the new drive with Windows 2000 and > made the old 4.3GB drive the master. > > > > Next, I rebooted to the Windows Live CD without installing anything. At > that point, I removed the CD and changed over to the 1GB partition [D:] > with the copy of the Live CD and executed setup.bat, which installed > FreeDos in the empty 3.3GB partition [C:]. > > > > The installation completed and rebooted to the new installation of FreeDos > without any complaints. Needless to say, FreeDos doesn’t recognize the CD > drive or the USB port, but that was no surprise, since I couldn’t use them > for the installation, either. > > > That is very similar to the dual disk and OEM style install I demonstrated > for 1.2. > > Basically, the OEM style version had a complete copy sitting on a > partition. That booted and installed 1.2 to a new partition. The installer > activated that new partition during installation. Subsequent boots went > straight to the users installed partition. However, this also has two > interesting effects. First, it leaves the CD contents on the other > partition and the user can easily install or remove packages. Also, > provides a recovery partition to reinstall the OS. > > > [..] > > > If your networking driver is working, consider trying EtherDFS. It’s works > pretty good for transferring files to/from DOS and a Linux 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] PCI Express Network Adapter Board for FreeDos
Thought I'd share my experience getting FreeDos working on my "new" machine. None of the official FreeDos installation methods liked its CD drive, and its USB port wasn’t bootable, so I had to find another way to install FreeDos. This is what worked for me. I’m sure there are other and possibly better ways. The Pentium II machine I had bought had a nice installation of Windows 2000 Pro that I didn’t want to lose, but it only had a 4.3GB drive. I bought another larger IDE drive and moved Windows 2000 over to the new drive. Then I repartitioned the original drive into (2) FAT32 partitions, a 1GB and a 3.3GB. I copied everything on the FreeDos 1.3 Live CD over to the 1GB partition using Windows 2000. Then I disconnected the new drive with Windows 2000 and made the old 4.3GB drive the master. Next, I rebooted to the Windows Live CD without installing anything. At that point, I removed the CD and changed over to the 1GB partition [D:] with the copy of the Live CD and executed setup.bat, which installed FreeDos in the empty 3.3GB partition [C:]. The installation completed and rebooted to the new installation of FreeDos without any complaints. Needless to say, FreeDos doesn’t recognize the CD drive or the USB port, but that was no surprise, since I couldn’t use them for the installation, either. For now, I have to boot into Windows 2000 to get files in and out of my FreeDos partition. It has a floppy, but none of my other computers have one. At present, I’m going into the BIOS and changing my boot drive, which is a bit of a hassle. In my long-ago experience, these computers were prone to corrupting the BIOS with too many changes. Eventually, I’ll setup some type of MBR menu. I did order an external USB floppy to make it easier to trade small files with my other computers. And the best news is my LAN came up first try! On Wed, Nov 11, 2020 at 12:59 PM Ralf Quint wrote: > On 11/11/2020 9:10 AM, Marv wrote: > > Ralf - I gave up on that motherboard with the onboard PCIe Realtek network > adapter and picked up a circa 1999 Intel Pentium II machine with (2) > Adaptec ANA-6911 PCI network adapter boards. I'm pretty sure I found the > right NDIS drivers for them. It also has a spare ISA slot, so I have that > option, too. I'm hoping to install FreeDos on it later today. > > Well, that sounds a bit like "from fire into the pan"... ;-) > > Would have to take a look at what those cards actually are to see what > kind of driver they would use. > > One thing that should generally be kept in mind is that DOS (any DOS) > predates the widespread use of (TCP)IP networking. In it's "networking > heydays", DOS machines were usually networking using other protocols (and > hardware infrastructure!) like IPX, SPX and a lot more proprietary > protocols. IP networking didn't really become a thing until the early '90s, > and by that time, Windows had take over and pretty much all hardware > manufacturers saw DOS driver support (not only for NICs!) just as an after > thought. > > So usually pre 2000 NICs are fairly well supported and should be the first > choice when using both real iron or a VM. NE2000, 3C905, RTL8129, RTL8139, > those are commonly among the well supported cards. > > Anything pretty much made past 2000, it becomes a real hit and miss, first > because manufacture tried to take advantage of the much higher CPU power to > offload some of the workload from their hardware and implement at least > some functionality in software (the infamous "WinModems", but also NICs, > disk controllers,...), while much newer products try to utilize > technologies that in general not "real mode DOS" friendly anymore, like > PCIe and other fluff. Even USB is basically a royal pain in the posterior... > > Ralf > > > <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient_term=icon> > Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient_term=link> > <#m_6172992070244809432_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > ___ > 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] PCI Express Network Adapter Board for FreeDos
Ralf - I gave up on that motherboard with the onboard PCIe Realtek network adapter and picked up a circa 1999 Intel Pentium II machine with (2) Adaptec ANA-6911 PCI network adapter boards. I'm pretty sure I found the right NDIS drivers for them. It also has a spare ISA slot, so I have that option, too. I'm hoping to install FreeDos on it later today. On Wed, Nov 11, 2020 at 11:50 AM Ralf Quint wrote: > On 11/9/2020 7:35 AM, Marv wrote: > > > I assume rtl8139 is a generic virtual driver and is the only choice for a > virtual Realtek adapter. My actual network adapter identifies as a > rtl8111/8168B. but says 8111GR on the chip. I realize my virtual > installation isn't going to use my physical network board. > > Can anyone give me some direction on this? > > Well, at this point in time, unfortunately not really. > > Just one note, a RTL8139 is a real hardware based 100MBit NIC chip, while > the RTL8111 is one of those "hybrid" hardware/software chips. So a 8139 > driver certainly will NOT work on an 8111. Don't recall right now what > exactly a 8168, my guess is that if it is mentioned together with the 8111 > in that driver that you tried, it is a dumbified RTL8169, which is a > hardware based chip. > > Realtek unfortunately seemed to have "cleaned up" their download sections > and removed anything pre-Windows 7. They are also only the (fab-less) > manufacturer of the actual NIC chips, they do not make any actual NIC > boards (or any motherboards for that matter). So a chance trying to find > any Realtek driver for DOS might be better done by roaming the actual board > manufacturers sites, as they might still have access to Realtek's > "internal/OEM" software library. > > Ralf > > > <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient_term=icon> > Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient_term=link> > <#m_-6923549759433770804_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > ___ > 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] PCI Express Network Adapter Board for FreeDos
My ongoing saga of trying to get networking up on FreeDos - I decided to install Linux Mint and QEMU on the machine. Then I did a virtual installation of FreeDos under QEMU. All went ok, and I can run FreeDos virtual just fine. Next, I tried to set up networking on my virtual FreeDos using the same NDIS setup and files that loaded ok under a freestanding installation of FreeDos. That was the NDIS setup that loaded ok without any errors but wouldn't communicate with my network. I expected it to at least load ok using my virtual installation of FreeDos, but the network section of the boot gets an error saying it can't find my network adapter. I'm not very familiar with QEMU or running any virtual machine for that matter, but it didn't take too long to realize I needed to create a network card. My full command to boot my virtual FreeDos under Qemu is: qemu-system-i386 -fda a.fd -hda c.hd -drive file=fat:rw:dos_folder -net nic,model=rtl8139 I don't get any complaints from QEMU about the -net part of the command. But it still gets the same error during boot "No Ethernet PCI Adapter Found", "Ethernet Adapter driver (V1.54) [2019/05/15] installation failed", "Serious internal error", "Hit any key to continue..." It does go ahead and boot the rest of the way up. It installed PROTMAN, RTGND, AND DIS_PKT9 modules, but of course, Netbind was unable to bind. I assume rtl8139 is a generic virtual driver and is the only choice for a virtual Realtek adapter. My actual network adapter identifies as a rtl8111/8168B. but says 8111GR on the chip. I realize my virtual installation isn't going to use my physical network board. Can anyone give me some direction on this? On Sun, Nov 8, 2020 at 4:26 AM Thomas Mueller wrote: > > > Can anyone suggest a PCIe network adapter for FreeDos? One that I > > > can get a packet driver or NDIS driver for. My FreeDos computer > > > doesn't have a regular PCI slot and I've given up trying to get the > onboard network adapter to work. > > > Realtek 8139 has NDIS drivers, E1000 both packet and NDIS > > > there are a couple of other cards with NDIS drivers > > If the motherboard supports PXE boot, might it be possible to boot by PXE > and use (Free)DOS partition as root? Would the BIOS (or UEFI?) then enable > FreeDOS to recognize the Ethernet connection? > > Tom > > > > ___ > 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] PCI Express Network Adapter Board for FreeDos
Looking at my BIOS settings, it looks like this board does support PXE boot. I'm not familiar with PXE, so I'll have to read up on it. I had also thought about installing Linux and FreeDos in separate partitions with a dual boot and seeing if that might solve my network issue under FreeDos. On Sun, Nov 8, 2020 at 4:26 AM Thomas Mueller wrote: > > > Can anyone suggest a PCIe network adapter for FreeDos? One that I > > > can get a packet driver or NDIS driver for. My FreeDos computer > > > doesn't have a regular PCI slot and I've given up trying to get the > onboard network adapter to work. > > > Realtek 8139 has NDIS drivers, E1000 both packet and NDIS > > > there are a couple of other cards with NDIS drivers > > If the motherboard supports PXE boot, might it be possible to boot by PXE > and use (Free)DOS partition as root? Would the BIOS (or UEFI?) then enable > FreeDOS to recognize the Ethernet connection? > > Tom > > > > ___ > 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] PCI Express Network Adapter Board for FreeDos
Just an update to my network adapter issue. I gave up on it and moved on to serial communications. I simply needed to be able to transfer files back and forth between my Windows 10 laptop and my FreeDos machine. I am successfully doing that using Kermit 3.14 on FreeDos and Kermit 95 on Windows 10. Not as fast as I would like, but it works. On Sat, Nov 7, 2020 at 6:29 AM tom ehlert wrote: > > > Can anyone suggest a PCIe network adapter for FreeDos? One that I > > can get a packet driver or NDIS driver for. My FreeDos computer > > doesn't have a regular PCI slot and I've given up trying to get the > onboard network adapter to work. > > while it's MSDOS based, this https://www.netbootdisk.com/cards.htm > has NDIS drivers for 98 cards. > > unfortunately FreeDOS is mostly ignoring network stuff. > > Tom > > > > ___ > 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] PCI Express Network Adapter Board for FreeDos
Thanks - yes, I did try ODI, but had the same results. Drivers install and load ok, but no communication. It's time for me to move on, I think. On Sat, Nov 7, 2020 at 10:47 AM Jerome Shidel wrote: > Have you tried any of the drivers from > http://www.georgpotthast.de/sioux/packet.htm ? > ___ > 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] PCI Express Network Adapter Board for FreeDos
You have a good point. I'm ready to give up on this motherboard and find an older (and cheap) desktop with appropriate card slots. Too bad - this board has some things I wanted like serial, parallel, PS2, VGA, plus HDMI, USB2/USB3, and SATA3. On Sat, Nov 7, 2020 at 11:05 AM ZB wrote: > On Sat, Nov 07, 2020 at 10:45:31AM -0500, Jerome Shidel wrote: > > > Have you tried any of the drivers from > http://www.georgpotthast.de/sioux/packet.htm ? > > If I may suggest something: maybe instead of trying to "rape" obviously > DOS-incompatible hardware it would be better idea to run FreeDOS on > hardware > that is compatible? It's no longer that expensive nowadays. > > So the other way around: rather "what I need to run FreeDOS with no > problems" - instead of: "I bought PCI-express mobo - no ISA, not even PCI - > now what?". > > Just my 2c > -- > regards, > Zbigniew > > > ___ > 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] PCI Express Network Adapter Board for FreeDos
Thanks, Tom - unfortunately, the motherboard I have available only has a PCI Express slot (no PCI slots). I know Startech has a PCIe to PCI adapter for $40, but then I would still need to buy a suitable PCI network card. I don't really want to invest that much in this project. I've looked at a lot of PCIe network cards, but haven't found one that supports DOS type drivers. At present, I'm still fooling around with the onboard Realtek 8111/8168B network adapter. It has me baffled. The NDIS driver and associated files load ok on boot with no errors, but every network program I try to run times out with no connection. I know the hardware is ok, because I booted to Linux on a USB stick and the network works just fine. On Sat, Nov 7, 2020 at 6:29 AM tom ehlert wrote: > > > Can anyone suggest a PCIe network adapter for FreeDos? One that I > > can get a packet driver or NDIS driver for. My FreeDos computer > > doesn't have a regular PCI slot and I've given up trying to get the > onboard network adapter to work. > > while it's MSDOS based, this https://www.netbootdisk.com/cards.htm > has NDIS drivers for 98 cards. > > unfortunately FreeDOS is mostly ignoring network stuff. > > Tom > > > > ___ > 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] PCI Express Network Adapter Board for FreeDos
Thanks Tom - I see the Realtek 8139 is fairly popular with DOS users and I can find PCI cards with that chip. But so far no luck finding a PCIe card that uses the 8139. Will keep looking. On Thu, Nov 5, 2020 at 11:19 AM tom ehlert wrote: > > > Can anyone suggest a PCIe network adapter for FreeDos? One that I > > can get a packet driver or NDIS driver for. My FreeDos computer > > doesn't have a regular PCI slot and I've given up trying to get the > onboard network adapter to work. > > Realtek 8139 has NDIS drivers, E1000 both packet and NDIS > > there are a couple of other cards with NDIS drivers > > > Tom > > > > ___ > 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] PCI Express Network Adapter Board for FreeDos
Can anyone suggest a PCIe network adapter for FreeDos? One that I can get a packet driver or NDIS driver for. My FreeDos computer doesn't have a regular PCI slot and I've given up trying to get the onboard network adapter to work. If not, has anyone tried a PCIe to PCI adapter (Startech for example) to run a suitable PCI network card through a PCIe slot? -- It's all fun and games until someone divides by zero. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Trying to get Freedos working on my LAN
Ralf: Thanks for responding. I've been using various home networks for 25 years or so, but I'll admit I know just enough about networking to be dangerous. In any case, I set networking up on this Freedos machine using the help pages at http://wiki.freedos.org/wiki/index.php/Networking_FreeDOS. I couldn't find a packet driver for my onboard nic, so I went with a ndis driver (RTGND.DOS). Anyway, hopefully, the following will answer most of your questions. *** C:\NET directory *** DHCP.COM NETBIND.COM PING.EXE PROTMAN.DOS PROTMAN.EXE PROTOCOL.INI RTLGND.DOS WATTCP.CFG *** PROTOCOL.INI file *** ;--- PROTOCOL.INI --- [protman] DriverName=PROTMAN$ [RTGND] DriverName=RTGND$ medium=_auto [PKTDRV] drivername=PKTDRV$ bindings=RTGND intvec=0x60 chainvec=0x68 *** FDCONFIG.SYS file *** SET DOSDIR=C:\FDOS !COUNTRY=001,858,C:\FDOS\BIN\COUNTRY.SYS !LASTDRIVE=Z !BUFFERS=20 !FILES=40 !MENUCOLOR=7,0 MENUDEFAULT=1,5 MENU 1 - Load FreeDOS with JEMMEX, no EMS (most UMBs), max RAM free MENU 2 - Load FreeDOS with JEMM386 (Expanded Memory) MENU 3 - Load FreeDOS low with some drivers (Safe Mode) MENU 4 - Load FreeDOS without drivers (Emergency Mode) 12?DOS=HIGH 12?DOS=UMB 12?DOSDATA=UMB 1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST I=TEST NOVME NOINVLPG 234?DEVICE=C:\FDOS\BIN\HIMEMX.EXE 2?DEVICE=C:\FDOS\BIN\JEMM386.EXE X=TEST I=TEST I=B000-B7FF NOVME NOINVLPG 34?SHELL=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\FDAUTO.BAT 12?SHELLHIGH=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\FDAUTO.BAT DEVICE=C:\NET\PROTMAN.DOS /I:C:\NET DEVICE=C:\NET\RTGND.DOS DEVICE=C:\NET\DIS_PKT9.DOS *** FDAUTO.BAT *** @ECHO OFF set DOSDIR=C:\FDOS set LANG=EN set TZ=UTC set PATH=%dosdir%\BIN if exist %dosdir%\LINKS\NUL set PATH=%path%;%dosdir%\LINKS set PATH=%path%;C:\NET set NLSPATH=%dosdir%\NLS set HELPPATH=%dosdir%\HELP set TEMP=%dosdir%\TEMP set TMP=%TEMP% set BLASTER=A220 I5 D1 H5 P330 set DIRCMD=/P /OGN /Y set COPYCMD=/-Y set OS_NAME=FreeDOS set OS_VERSION=1.3-RC3 set autofile=C:\FDAUTO.BAT set cfgfile=C:\FDCONFIG.SYS alias cfg=edit %cfgfile% alias auto=edit %autofile% alias reboot=fdapm warmboot alias reset=fdisk /reboot alias halt=fdapm poweroff alias shutdown=fdapm poweroff if not exist %dosdir%\bin\vinfo.com goto Only8086 vinfo /m if errorlevel 3 goto Support386 if errorlevel 2 goto Support286 :Only8086 if "%config%"=="2" goto END MEM /C /N goto FINAL :Support286 if "%config%"=="3" goto END LH FDAPM APMDOS CTMOUSE MEM /C /N goto FINAL :Support386 if "%config%"=="4" goto END LH FDAPM APMDOS rem LH SHARE rem if EXIST %DOSDIR%\BIN\DOSLFN.COM LH DOSLFN REM NLSFUNC %dosdir%\BIN\COUNTRY.SYS REM DISPLAY CON=(EGA),858,2) REM MODE CON CP PREP=((858) %dosdir%\CPI\EGA.CPX) REM KEYB US,858,%dosdir%\bin\keyboard.sys REM CHCP 858 REM MKEYB UK CTMOUSE SHSUCDX /QQ /D3 REM LH SHSUCDHD /QQ /F:FDBOOTCD.ISO DEVLOAD /H /Q %dosdir%\BIN\UDVD2.SYS /D:FDCD0001 REM DEVLOAD /H /Q %dosdir%\BIN\UIDE.SYS /H /D:FDCD0001 /S5 SHSUCDX /QQ /~ /D:?SHSU-CDR,D /D:?SHSU-CDH,D /D:?FDCD0001,D /D:?FDCD0002,D /D:?FDCD0003,D MEM /C /N SHSUCDX /D C:\NET\NETBIND.COM set ip=10.0.0.40 set netmask=255.255.255.0 set gateway=10.0.0.1 set dns=10.0.0.1 :FINAL if exist %dosdir%\bin\fdnet.bat call %dosdir%\bin\fdnet.bat start if exist %dosdir%\bin\fdassist.bat call %dosdir%\bin\fdassist.bat if exist %dosdir%\bin\welcome.bat call %dosdir%\bin\welcome.bat :END *** WATTCP.CFG *** my_ip=10.0.0.40 netmask=255.255.255.0 nameserver=10.0.0.1 gateway=10.0.0.1 *** boot *** Ethernet board driver installs ok. Modules PROTMAN, RTGND, DIS_PKT9 install ok. NETBIND.COM reports ethernet board's address id D05099769204. *** NTCPDRV.EXE *** NTCPDRV.EXE installs Trumpet TCP version 3.1 Interrupt = 0x61 MAC/DIS converter packet driver version 9 6 ok and reports my ip = 10.0.0.40 netmask = 255.255.255.0 gateway = 10.0.0.1 *** ping *** ping 10.0.0.40 from Freedos machine gets no response. ping 10.0.0.40 from Windows machine gets no response. *** DHCP *** DHCP reports Packet driver failed *** questions/comments *** I'm not sure about NTCPDRV reporting interrupt 0x61 relates to PROTOCO.INI's intvec=0x60? Also not sure why NTCPDRV reports MAC/DIS converter "packet driver" when I've installed a ndis adapter driver? For what it's worth, I've tried 3 different ethernet cables. On Tue, Nov 3, 2020 at 12:46 AM Ralf Quint wrote: > On 11/2/2020 6:54 PM, Marv wrote: > > Freedos noob here. I've been running old Dos programs like Wordstar, > Supercalc, etc. ok on Freedos for a couple of weeks. Now I'm trying to get > it on my LAN so I can move files around easier. > > I'm using an ASRock N3150B-ITX (circa 2015) with an onboard ethernet > adapter. Specs say: PCIE x1 Gigabit LAN 10/100/1000 Mb/s, Realtek RTL8111GR. > > NICSCAN says vendor is 10EC (Realteck) and device is 8168 (RTL8111/8168B > PCI Express Gigabit Ethernet controller). > > I finally found the right ndis driv
[Freedos-user] Trying to get Freedos working on my LAN
Freedos noob here. I've been running old Dos programs like Wordstar, Supercalc, etc. ok on Freedos for a couple of weeks. Now I'm trying to get it on my LAN so I can move files around easier. I'm using an ASRock N3150B-ITX (circa 2015) with an onboard ethernet adapter. Specs say: PCIE x1 Gigabit LAN 10/100/1000 Mb/s, Realtek RTL8111GR. NICSCAN says vendor is 10EC (Realteck) and device is 8168 (RTL8111/8168B PCI Express Gigabit Ethernet controller). I finally found the right ndis driver for the adapter. I can now get thru the boot process without any errors, and Netbind shows the adapter's hardware address. My problem or question is the hardware address Netbind shows on boot doesn't show up in a listing of IP addresses on my router nor does ARP list it. Does the IP address only get assigned to the hardware address when a program uses WATTCP.CFG? I think I have my WATTCP.CFG is setup correctly, but I'm not entirely sure. I want to use a static IP address. But since the device/hardware address doesn't show up on the router, I can't turn it into a static IP there. I've been assuming setting my_ip to an unused IP in WATTSCP.CFG will create the static IP, but apparently not? I know this is not a Freedos question or issue, but how and when does an IP address get assigned to a device in this kind of network? -- It's all fun and games until someone divides by zero. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
