I have now a multiboot system without any problem.

First disk, first partition WinX
first disk second partition: Gnewsense (Ubuntu based)

Second disk first partition Freedos (Old Win98 fat32)
Second disk second partition data space
second disk third partition Knoppix 5.3.x (DVD version)


2010/8/11 Alain Mouette <ala...@pobox.com>:
> Knopix is a bit old, but I usualy dualboot with Ubuntu. This is the easy
> path:
>
> * FreeDOS should be in the first primary partition (sda1)
> * the partition should be set active.
> * Use grub, Ubuntu configures it automaticaly, but calls it "windows"
>
> FreeDOS will not boot from extended partitions, and there are
> *sometimes* problems with other primary partitions (but I have done it)
>
> Alain
>
> Em 11-08-2010 19:20, david lowe escreveu:
>> Has any FreeDOS user ever dualbooted with Knoppix (DSL)?
>>
>>  > From: freedos-user-requ...@lists.sourceforge.net
>>  > Subject: Freedos-user Digest, Vol 382, Issue 1
>>  > To: freedos-user@lists.sourceforge.net
>>  > Date: Sun, 8 Aug 2010 13:01:57 +0000
>>  >
>>  > Send Freedos-user mailing list submissions to
>>  > freedos-user@lists.sourceforge.net
>>  >
>>  > To subscribe or unsubscribe via the World Wide Web, visit
>>  > https://lists.sourceforge.net/lists/listinfo/freedos-user
>>  > or, via email, send a message with subject or body 'help' to
>>  > freedos-user-requ...@lists.sourceforge.net
>>  >
>>  > You can reach the person managing the list at
>>  > freedos-user-ow...@lists.sourceforge.net
>>  >
>>  > When replying, please edit your Subject line so it is more specific
>>  > than "Re: Contents of Freedos-user digest..."
>>  >
>>  >
>>  > Today's Topics:
>>  >
>>  > 1. Re: Recommondation of TCP/IP stack, DHCP client (Someone)
>>  > 2. Re: Recommondation of TCP/IP stack, DHCP client (Mike Eriksen)
>>  > 3. Re: Recommondation of TCP/IP stack, DHCP client (Ulrich Hansen)
>>  > 4. Re: Recommondation of TCP/IP stack, DHCP client (4625)
>>  > 5. Re: Recommondation of TCP/IP stack, DHCP client (4625)
>>  > 6. Re: Recommondation of TCP/IP stack, DHCP client (Ulrich Hansen)
>>  > 7. Re: Recommondation of TCP/IP stack, DHCP client (4625)
>>  > 8. Re: Recommondation of TCP/IP stack, DHCP client (Ulrich Hansen)
>>  >
>>  >
>>  > ----------------------------------------------------------------------
>>  >
>>  > Message: 1
>>  > Date: Fri, 06 Aug 2010 19:53:35 -0700
>>  > From: Someone <plu...@robinson-west.com>
>>  > Subject: Re: [Freedos-user] Recommondation of TCP/IP stack, DHCP
>>  > client
>>  > To: freedos-user@lists.sourceforge.net
>>  > Message-ID: <1281149616.24338.100.ca...@goose.robinson-west.com>
>>  > Content-Type: text/plain
>>  >
>>  >
>>  > On Fri, 2010-08-06 at 23:10 -0300, Alain Mouette wrote:
>>  > > I completly disagree.
>>  > >
>>  > > Just today I installed FreeDOS on a brand new Asus board with SATA2 a
>>  > > gigabit ethernet chip.
>>  > >
>>  > > Simple: go to www.netbootdisk.com and create a floppy. After it boots
>>  > > and detects the NIC, copy it's driver including packet driver. Easy...
>>  > >
>>  > > The truth is that if you have an application that is worth using with
>>  > > FreeDOS, drivers exist :)
>>  > >
>>  > > And it is damn fast
>>  > >
>>  > > Alain
>>  >
>>  > Command line Linux tuned properly is also fast where Linux supports more
>>  > network cards than Freedos does. Another problem, how did you find out
>>  > that there is a driver for your particular card? For Linux users, the
>>  > kernel supports a lot of network cards straight off.
>>  >
>>  > Does Freedos support common nics such as:
>>  >
>>  > Netgear Fa311/Fa312?
>>  >
>>  > Thuderlan dual port 10/100 nics?
>>  >
>>  > AOpen nics?
>>  >
>>  > Tulip nics?
>>  >
>>  > Other nics?
>>  >
>>  > I stand by my statement that TCP/IP and DOS are probably not the best
>>  > combination. DOS does not protect the hardware from programs that
>>  > execute, because it can't. DOS cannot stop viruses/worms very easily
>>  > because it doesn't shield the hardware in the first place. This is
>>  > all the more reason to avoid connecting to global networks from a
>>  > DOS based environment.
>>  >
>>  > How about DOSbox, Virtualbox, and VMWARE nics? Can Freedos use any
>>  > virtual NICS?
>>  >
>>  >
>>  >
>>  >
>>  > ------------------------------
>>  >
>>  > Message: 2
>>  > Date: Sat, 7 Aug 2010 12:32:20 +0200
>>  > From: Mike Eriksen <thinstation.m...@gmail.com>
>>  > Subject: Re: [Freedos-user] Recommondation of TCP/IP stack, DHCP
>>  > client
>>  > To: freedos-user@lists.sourceforge.net
>>  > Message-ID:
>>  > <aanlktimx31etkdoc4_4srppfww_ycdpr1t59mg__-...@mail.gmail.com>
>>  > Content-Type: text/plain; charset=ISO-8859-1
>>  >
>>  > On Sat, Aug 7, 2010 at 3:22 AM, Someone <plu...@robinson-west.com> wrote:
>>  > > I question whether TCP/IP is the best way to go in a DOS environment.
>>  >
>>  > That depend on your needs. Been a member of the Thinstation Linux thin
>>  > client team, I have all the lightweight Linux I could wish. My
>>  > original need came from the need to BIOS upgrade a floppyless Ubuntu
>>  > box. I ended up by adding the DOS flash program and the BIOS image to
>>  > a Balder image, make an ISO of it and problem solved. Not very
>>  > elegant. So I decided to explore if I could make a boot floppy with
>>  > USB support so I could put the flash program and BIOS image on a
>>  > writable device and not have to create a new ISO every time (not that
>>  > it happens often, but now it got a pet project).
>>  >
>>  > Having reached this, I wanted more: the ability to download the flash
>>  > program and the image directly with wget or even a text browser. This
>>  > is a bit hard to accomplish without TCP/IP :-) I've put the network
>>  > stack, applications and packet drivers on the floppy due to size
>>  > restriction on the floppy. It isn't quite working yet, but I think I
>>  > just need to put a bit more time into it. I see no fundamental
>>  > obstacles now.
>>  >
>>  >
>>  >
>>  > ------------------------------
>>  >
>>  > Message: 3
>>  > Date: Sat, 07 Aug 2010 22:16:46 +0200
>>  > From: Ulrich Hansen <uhan...@mainz-online.de>
>>  > Subject: Re: [Freedos-user] Recommondation of TCP/IP stack, DHCP
>>  > client
>>  > To: "freedos-user@lists.sourceforge.net"
>>  > <freedos-user@lists.sourceforge.net>
>>  > Message-ID: <4c5dbf2e.8060...@mainz-online.de>
>>  > Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>  >
>>  > Am 07.08.2010 03:22, schrieb Someone:
>>  > > Command line linux is much easier to network than freedos and there
>> is a
>>  > > lot of utility to it.
>>  >
>>  > You are right. There is no doubt that GNU/Linux is much better
>>  > equipped for networking than (Free)DOS. GNU/Linux also runs on old
>>  > hardware, although it can be difficult (and painfully slow) to
>>  > install. Modern installers need a lot of resources. I run Debian (Dual
>>  > boot with FreeDOS) on some 486SX with 20 MB RAM so I know something
>>  > about that.
>>  >
>>  > > Companies aren't releasing dos drivers
>>  >
>>  > This is not necessarily true. Two weeks ago we had a discussion about
>>  > drivers for the RTL8101E/RTL8102E PCI Express Fast Ethernet controller
>>  > in a quite modern Acer Aspire One netbook. As we found out, Realtek
>>  > still released ODI (Netware) and NDIS (MS Client for DOS) drivers for
>>  > that NIC, so it can be used with shims as packet drivers for
>>  > networking in FreeDOS.
>>  >
>>  > So even when some companies do not release packet drivers for DOS, the
>>  > NIC might be still usable.
>>  >
>>  > > I question whether TCP/IP is the best way to go in a DOS environment.
>>  >
>>  > You are right. Security is an issue. ftpsrv32.exe for instance - one
>>  > of the few FTP servers that exist for DOS - doesn't ask for a password
>>  > and opens the whole DOS system for guests. And if you are using WLAN
>>  > in DOS, you are limited to 802.11b cards with WEP encryption, which is
>>  > insecure per definition.
>>  >
>>  > On the other hand, most TCP/IP networking software in DOS cannot run
>>  > as TSR. It runs fullscreen in the foreground, which is hard to ignore.
>>  > So there are no ports unintentionally open. And if you are running a
>>  > server in DOS you are at least not running anything else. ;-)
>>  >
>>  > > For security reasons, most of us probably don't want
>>  > > our DOS environments to connect directly to the Net, but for
>>  > > gaming purposes, local area networking can be quite fun.
>>  >
>>  > Gaming is one possible purpose of networking DOS machines. Another
>>  > reason may be the need to run old DOS software that has to have
>>  > network access.
>>  >
>>  > But I think the most important reason people have to network (Free)DOS
>>  > is simply to be able to exchange data.
>>  >
>>  > Modern computers don't have floppies, parallel or serial ports. Old
>>  > computers don't have USB or SD-cards. Some old computers have CD-Rom
>>  > but burning CDs for data exchange can be annoying, as Mike Eriksen
>>  > pointed out.
>>  >
>>  > TCP/IP for DOS has been around since the eighties, so it is the common
>>  > ground for old and new hardware, for DOS and a more modern OS.
>>  >
>>  > Just as example: How do I myself exchange data between FreeDOS on my
>>  > old 486SX laptops and my modern Thinkpad running Ubuntu Lucid? By
>>  > starting a ftp server in freedos and logging in with filezilla. How
>>  > else could I do this? By loading MS Client and creating a shared
>>  > directory.
>>  >
>>  > > How about DOSbox, Virtualbox, and VMWARE nics? Can Freedos use any
>>  > > virtual NICS?
>>  >
>>  > I installed FreeDOS in Virtualbox last week. Virtualbox uses a AMD
>>  > PCnet-Fast III card. A free packet driver "pcntpk.com" for this card
>>  > is available at:
>>  > <http://www.crynwr.com/drivers/amdpd.zip>
>>  >
>>  > For MS Client you can get the NDIS driver "pcntnd.dos" at:
>>  >
>> <ftp://ftp.dlink.com/NIC/de520/Driver/uncompressed/MSLANMAN.DOS/DRIVERS/ETHERNET/PCNTND/>
>>  >
>>  > In Virtualbox the only way to exchange data between the FreeDOS guest
>>  > and the host (Ubuntu in my case) is to create a network: I use the
>>  > vbox network adapter in bridged mode. In the FreeDOS guest I run a DOS
>>  > server in my LAN (behind a router of course) and connect to it from
>>  > the Ubuntu host with filezilla. I also connected the FreeDOS guest
>>  > with a scond Virtualbox guest running Windows XP via MS Client in DOS.
>>  >
>>  > So yes, you are right: TCP/IP and DOS are probably not the best
>>  > combination.
>>  > And no, you are not right: Networking DOS via TCP/IP is still needed
>>  > for many reasons.
>>  >
>>  >
>>  >
>>  > ------------------------------
>>  >
>>  > Message: 4
>>  > Date: Sat, 07 Aug 2010 14:18:36 -0700 (PDT)
>>  > From: 4625 <4625...@gmail.com>
>>  > Subject: Re: [Freedos-user] Recommondation of TCP/IP stack, DHCP
>>  > client
>>  > To: freedos-user@lists.sourceforge.net
>>  > Message-ID: <abg1jqj8pymlc3dyp7gdppsnldc3u...@4625>
>>  > Content-Type: text/plain; charset=koi8-r
>>  >
>>  > 6-Aug-2010 ?????, ? 18:22 ?????, Someone ???????(?) ?????????:
>>  >
>>  > > I'd say that Freedos is okay for networking if you have a card that
>>  > > is supported by open source drivers, but that seems to be a very
>>  > > short list of cards at this time. I guess the question to ask of
>>  > > anyone seeking to
>>  >
>>  > Does anyone have success experience with "Edimax EN-9130TXL" PCI
>>  > network adapter on FreeDOS? It looks like EN-9130TXL will work, but I
>>  > want to be sure.
>>  >
>>  > This is how *BSD recognize the EN-9130TXL card: "rl0 at pci0 dev 8
>>  > function 0 "Realtek 8139" rev 0x10: irq 10".
>>  >
>>  > Attention! I notice to everyone that "ASUS NX1001" PCI network adapter
>>  > won't work on old motherboard "Giga-Byte i440BX". Windows, *BSD, Linux,
>>  > they all report that card not pluged into PCI slot. However, on modern
>>  > motherboard this card work very well.
>>  >
>>  > --
>>  > /4625 () ???????? ascii ribbon - ?????? ????? ? html ???????
>>  > /\ www.asciiribbon.org - ?????? ????????????? ????????
>>  >
>>  >
>>  >
>>  >
>>  > ------------------------------
>>  >
>>  > Message: 5
>>  > Date: Sat, 07 Aug 2010 14:19:28 -0700 (PDT)
>>  > From: 4625 <4625...@gmail.com>
>>  > Subject: Re: [Freedos-user] Recommondation of TCP/IP stack, DHCP
>>  > client
>>  > To: freedos-user@lists.sourceforge.net
>>  > Message-ID: <u1vsgdt0ann4n4p2e5j7cnz9s2vfz...@4625>
>>  > Content-Type: text/plain; charset=koi8-r
>>  >
>>  > 6-Aug-2010 ?????, ? 19:53 ?????,, Someone ???????(?) ?????????:
>>  >
>>  > > execute, because it can't. DOS cannot stop viruses/worms very easily
>>  > > because it doesn't shield the hardware in the first place. This is
>>  > > all the more reason to avoid connecting to global networks from a DOS
>>  > > based environment.
>>  >
>>  > Are you sure that modern worms are able to intrude? Do you know any
>>  > modern worm for DOS?
>>  >
>>  > --
>>  > /4625 () ???????? ascii ribbon - ?????? ????? ? html ???????
>>  > /\ www.asciiribbon.org - ?????? ????????????? ????????
>>  >
>>  >
>>  >
>>  >
>>  > ------------------------------
>>  >
>>  > Message: 6
>>  > Date: Sun, 08 Aug 2010 00:21:25 +0200
>>  > From: Ulrich Hansen <uhan...@mainz-online.de>
>>  > Subject: Re: [Freedos-user] Recommondation of TCP/IP stack, DHCP
>>  > client
>>  > To: freedos-user@lists.sourceforge.net
>>  > Message-ID: <4c5ddc65.9080...@mainz-online.de>
>>  > Content-Type: text/plain; charset=KOI8-R; format=flowed
>>  >
>>  > According to a google search, the EN-9130TXL card works with a Realtek
>>  > RTL8139D chip.
>>  >
>>  > Drivers for that chip can be found at Realteks site:
>>  >
>> <http://www.realtek.com/downloads/downloadsView.aspx?Langid=1&PNid=6&PFid=6&Level=5&Conn=4&DownTypeID=3&GetDown=false>
>>  >
>>  > If you scroll down you find:
>>  > - a DOS packet driver,
>>  > - a DOS NDIS driver and
>>  > - a Novell ODI driver.
>>  >
>>  > So I think there is a good chance the NIC will work in FreeDOS.
>>  >
>>  > BTW: According to Realtek, the DOS packet driver was updated four days
>>  > ago (2010/8/4).
>>  >
>>  >
>>  >
>>  >
>>  > ------------------------------
>>  >
>>  > Message: 7
>>  > Date: Sun, 08 Aug 2010 02:30:08 -0700 (PDT)
>>  > From: 4625 <4625...@gmail.com>
>>  > Subject: Re: [Freedos-user] Recommondation of TCP/IP stack, DHCP
>>  > client
>>  > To: uhan...@mainz-online.de, freedos-user@lists.sourceforge.net
>>  > Message-ID: <f5ijbhfsb9lmvfelsiaodhw5hwo7h...@4625>
>>  > Content-Type: text/plain; charset=koi8-r
>>  >
>>  > 8-Aug-2010 ?????, ? 00:21 ?????, Ulrich Hansen ???????(?) ?????????:
>>  >
>>  > > According to a google search, the EN-9130TXL card works with a
>>  > > Realtek RTL8139D chip.
>>  > >
>>  > > Drivers for that chip can be found at Realteks site:
>>  > >
>> <http://www.realtek.com/downloads/downloadsView.aspx?Langid=1&PNid=6&PFid=6&Level=5&Conn=4&DownTypeID=3&GetDown=false>
>>  > >
>>  > > If you scroll down you find:
>>  > > - a DOS packet driver,
>>  > > - a DOS NDIS driver and
>>  > > - a Novell ODI driver.
>>  >
>>  > I see that, but downloading won't to begin. Download link redirect me
>>  > to http://www.realtek.com/downloads/ .
>>  >
>>  > > BTW: According to Realtek, the DOS packet driver was updated four days
>>  > > ago (2010/8/4).
>>  >
>>  > Good news.
>>  >
>>  > --
>>  > /4625 () ???????? ascii ribbon - ?????? ????? ? html ???????
>>  > /\ www.asciiribbon.org - ?????? ????????????? ????????
>>  >
>>  >
>>  >
>>  >
>>  > ------------------------------
>>  >
>>  > Message: 8
>>  > Date: Sun, 08 Aug 2010 15:01:46 +0200
>>  > From: Ulrich Hansen <uhan...@mainz-online.de>
>>  > Subject: Re: [Freedos-user] Recommondation of TCP/IP stack, DHCP
>>  > client
>>  > To: freedos-user@lists.sourceforge.net
>>  > Message-ID: <4c5eaaba.30...@mainz-online.de>
>>  > Content-Type: text/plain; charset=KOI8-R; format=flowed
>>  >
>>  > Am 08.08.2010 11:30, schrieb 4625:
>>  >
>>  > > I see that, but downloading won't to begin. Download link redirect me
>>  > > to http://www.realtek.com/downloads/ .
>>  >
>>  > It worked for me yesterday after I tried it a few times. See pm.
>>  >
>>  >
>>  >
>>  >
>>  >
>>  > ------------------------------
>>  >
>>  >
>> ------------------------------------------------------------------------------
>>  > This SF.net email is sponsored by
>>  >
>>  > Make an app they can't live without
>>  > Enter the BlackBerry Developer Challenge
>>  > http://p.sf.net/sfu/RIM-dev2dev
>>  >
>>  > ------------------------------
>>  >
>>  > _______________________________________________
>>  > Freedos-user mailing list
>>  > Freedos-user@lists.sourceforge.net
>>  > https://lists.sourceforge.net/lists/listinfo/freedos-user
>>  >
>>  >
>>  > End of Freedos-user Digest, Vol 382, Issue 1
>>  > ********************************************
>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev
>>
>>
>>
>> _______________________________________________
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>



-- 
--
+-+-+-+-+-+-+-+
Marco A. Achury
Tel: +58-(212)-6158777
Cel: +58-(414)-3142282
Skype: marcoachury
Ekiga.net: marcoachury
http://www.achury.com.ve

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to