Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Help on make a amd64 server to getting OS DOS installed
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Gentoo on AMD64
View previous topic :: View next topic  
Author Message
Gert Andersen
Tux's lil' helper
Tux's lil' helper


Joined: 24 Aug 2007
Posts: 138
Location: Broendby, Denmark

PostPosted: Sat Sep 19, 2009 7:45 pm    Post subject: Help on make a amd64 server to getting OS DOS installed Reply with quote

I have not made dosemu to work and installed with patch for newer cpu's, and after my pc now is changed from be a desktop computer to a linux server, is there this miss and trouble that the OS DOS freedos is been messaging from emerge that it is not testet for a server to be installed on a server, and it shall be reported to Gentoo Hardened.
So it now I like to knoe if there is some OS DOS for linux and Gentoo to can be installed by internet and get, either by emerge or via download and installed on the gentoo amd64 server for use to make dosemu work complete.
I need this DOS OS liek msdos or Ibm DOS files to be installed befor my dosemi is complete working so dosemu not just say hit a key to return to linux.

So give me a helt on how and wher ei can finde some way to get installed the dos binaries files.
_________________
Gert K. Andersen
Back to top
View user's profile Send private message
Elv13
Guru
Guru


Joined: 13 Nov 2005
Posts: 388
Location: Socialist land of North America

PostPosted: Sat Sep 19, 2009 7:55 pm    Post subject: Reply with quote

Never heard of OS DOS, but I know DosBox and qemu
Back to top
View user's profile Send private message
Gert Andersen
Tux's lil' helper
Tux's lil' helper


Joined: 24 Aug 2007
Posts: 138
Location: Broendby, Denmark

PostPosted: Sat Sep 19, 2009 8:08 pm    Post subject: Reply with quote

I can more say DOS like MSDOS and IBM DOS Utilties to run by dosemu, the DOS system there ws befr Windos and OS/2 the old Operation System.
_________________
Gert K. Andersen
Back to top
View user's profile Send private message
Elv13
Guru
Guru


Joined: 13 Nov 2005
Posts: 388
Location: Socialist land of North America

PostPosted: Sat Sep 19, 2009 9:04 pm    Post subject: Reply with quote

Use the real dos if you want, but why can't dosbox work? Did you tried it?
Back to top
View user's profile Send private message
Gert Andersen
Tux's lil' helper
Tux's lil' helper


Joined: 24 Aug 2007
Posts: 138
Location: Broendby, Denmark

PostPosted: Sat Sep 19, 2009 9:21 pm    Post subject: Reply with quote

It is by dosbox dosemu I am by dos mode and I find that the old freedos interprenter fiels was there still, but symlink to them is not working and if I copy them into directory /dosemu/drive_c is doemu coming with wrong command interprenter and ask for shell command, the old freedos files is form my working dosemu and freedos before I got upgrade my cpu form a old 2Ghz cpu of amd66 AMD Athlont I X1 processor, amd now is the system and pc a server installation before was it a desktop pc and the freedos (dosemu-freedis binaries do emerge nd the system not like to install now.
_________________
Gert K. Andersen
Back to top
View user's profile Send private message
Elv13
Guru
Guru


Joined: 13 Nov 2005
Posts: 388
Location: Socialist land of North America

PostPosted: Sat Sep 19, 2009 9:34 pm    Post subject: Reply with quote

I think you need to compile your dos emulator with multilib instead of native 64bit. Or use qemu as I said earlier.
Back to top
View user's profile Send private message
Gert Andersen
Tux's lil' helper
Tux's lil' helper


Joined: 24 Aug 2007
Posts: 138
Location: Broendby, Denmark

PostPosted: Sat Sep 19, 2009 9:42 pm    Post subject: Reply with quote

That is the problem on the pc it is a server now where it before was desktop pc and emerge come with that the freedos not is teste enough to be installed on a server. So I have to see if I by a sourve file have to do the work personly and not as binaries.
Then is so the way to make this be done by emerge of freedos from soruces.
else have it to be without emerge of it.
_________________
Gert K. Andersen
Back to top
View user's profile Send private message
Elv13
Guru
Guru


Joined: 13 Nov 2005
Posts: 388
Location: Socialist land of North America

PostPosted: Sat Sep 19, 2009 9:52 pm    Post subject: Reply with quote

Emerging FreeDOS without multilib on a 64bit system (you are in the 64bit Linux forum, I assume you use 64bit OS) will create a 64bit DOS system. Somethign that never existed and will never exist. It will not be compatible with DOS applications (at least, I don't think so) as DOS is a 16bit OS. Please consider using an emulator with the official binary and not try to do something strange.

If freedos does not fill your needs, use MsDO,S DrDOS, IBM DOS or somethint that feel your needs.
Back to top
View user's profile Send private message
Gert Andersen
Tux's lil' helper
Tux's lil' helper


Joined: 24 Aug 2007
Posts: 138
Location: Broendby, Denmark

PostPosted: Sat Sep 19, 2009 10:02 pm    Post subject: Reply with quote

I am right of trying to emerge and compile freedos as they was in a binary packet there should put the right places by run emerge dosemu, but as the system before was a desktop system is it now a server system, and it is here the kernel and emerge stops with it is not tested for a server and I shall report it to hardened project guys.

I find that the freedos still was at my syste on /etc/dosemu/ directory but when I tryied to copy the most used 3 files to /dosemu/drive_c directory come dosemu out with it was the wrong command interprenter files and ask for a shell command.
_________________
Gert K. Andersen
Back to top
View user's profile Send private message
Elv13
Guru
Guru


Joined: 13 Nov 2005
Posts: 388
Location: Socialist land of North America

PostPosted: Sun Sep 20, 2009 12:41 am    Post subject: Reply with quote

A server and a desktop are not different. It is exactly the same. If you run x86_64, then it would not work in any x64_86 system configured like yours, no mater if it is a server or a desktop.

Quote:
From scharkalvin:
Just as the 386 family (that's 386,586,pentium,PII,PIII.P4,athlon,etc) have a real-8086 emulation mode which
enables you to run DOS programs inside of a 32 bit OS (such as windows-NT) the AMD64 cpu's have an
emulation mode that enables you to run 32 bit programs inside of a 64bit OS. However the buck stops there.
You CAN'T run the real-86 emulation mode inside the 32 bit emulation mode, or inside the 64 bit mode.
This means that the DOS-emu package will NOT run with a 64bit OS. I don't know how many people need
to run DOS-emu, but if you do you CAN'T run it on an AMD-64 system UNLESS you run it on a 32 bit
kernel. So in this case you will need a dual boot system, chroot is NOT enough!


Thats your problem, so just use qemu, thats all
Back to top
View user's profile Send private message
keet
Guru
Guru


Joined: 09 Sep 2008
Posts: 570

PostPosted: Sun Sep 20, 2009 2:00 am    Post subject: 32-bit Disk Operating System? Reply with quote

Just a curious question... D.O.S. was never 32-bit, either (at least none of the versions that I used... 3.x > 6.22), so how would a 32-bit DOS in Linux be compatible with DOS programs, either?

Ah, maybe I understand... i386-type processors can emulate a 16-bit environment, and a 64-bit C.P.U. can emulate a 32-bit one, but they can't emulate two layers down (64 > 32 > 16)
Back to top
View user's profile Send private message
Gert Andersen
Tux's lil' helper
Tux's lil' helper


Joined: 24 Aug 2007
Posts: 138
Location: Broendby, Denmark

PostPosted: Sun Sep 20, 2009 7:06 am    Post subject: Reply with quote

Ok, so if the cystem is a server kan it not run dosemu and use freedos, so the syste has to be setup another way to work with dosemu.
My Gentoo expert and helper has setup the system as a server, s in this case has the system to be setup as a desktop system else will it not work. Right?
_________________
Gert K. Andersen
Back to top
View user's profile Send private message
Elv13
Guru
Guru


Joined: 13 Nov 2005
Posts: 388
Location: Socialist land of North America

PostPosted: Sun Sep 20, 2009 8:12 pm    Post subject: Reply with quote

A desktop and a server is exactly the same thing, there is no difference in the system itself. The only differences are in the packages choice. For the last time, I will not repeat it again USE QEMU or an older computer with 32bit OS. You can't DosEMU with a 64bit OS, you -need- qEmu to emulate a 32 or 16bit CPU and use it to run DOS.
Back to top
View user's profile Send private message
Gert Andersen
Tux's lil' helper
Tux's lil' helper


Joined: 24 Aug 2007
Posts: 138
Location: Broendby, Denmark

PostPosted: Mon Sep 21, 2009 7:47 am    Post subject: Reply with quote

Ok, then is it qemu I shall use on my amd64, but strange as I have run dosemu on that amd64 pc before without troubles, but it could have been a cpu there could emulate for dos and go down to 32bit.
So qemu to dos on my amd64 now with my new cpu AM Athlon II X2 A3/2+ 245, should it.
I have dosemu installed in the pc and it works until I shall use a command interpreter as msdos command.com to run the dos part and it is here it stops self if there is the freedos files from before I had upgrade the cpu and the pc is setup as a server.
_________________
Gert K. Andersen
Back to top
View user's profile Send private message
Gert Andersen
Tux's lil' helper
Tux's lil' helper


Joined: 24 Aug 2007
Posts: 138
Location: Broendby, Denmark

PostPosted: Mon Sep 21, 2009 12:06 pm    Post subject: Reply with quote

Qemu have soem problem as dosemu freedos have, that it is not tested + not like to be installed with gcc4.x compiler and say require gcc3 to be good and well installed.
THen for dosemu is it running adn there is only freedos there not is weel working from hardened.
_________________
Gert K. Andersen
Back to top
View user's profile Send private message
i92guboj
Bodhisattva
Bodhisattva


Joined: 30 Nov 2004
Posts: 10315
Location: Córdoba (Spain)

PostPosted: Mon Sep 21, 2009 12:16 pm    Post subject: Reply with quote

Instead of all this hit and miss that this thread is right now, I suggest posting the real error messages in place of the vague descriptions.
Back to top
View user's profile Send private message
Gert Andersen
Tux's lil' helper
Tux's lil' helper


Joined: 24 Aug 2007
Posts: 138
Location: Broendby, Denmark

PostPosted: Mon Sep 21, 2009 12:26 pm    Post subject: Reply with quote

ERROR: setup
qemu requires gcc-3 in order to build and work correctly please compile it switching to gcc-3.
We are aware that qemu can guess a gcc-3 but this feature could be harmful.

Code:
ERROR: app-emulation/qemu-softmmu-0.9.1-r3 failed.
Call stack:
                     ebuild.sh, line   49:  Called pkg_setup
  qemu-softmmu-0.9.1-r3.ebuild, line   40:  Called die
The specific snippet of code:
        die "gcc 4 cannot build qemu"
 The die message:
  gcc 4 cannot build qemu

If you need support, post the topmost build error, and the call stack if relevant.
A complete build log is located at '/var/log/portage/app-emulation:qemu-softmmu-0.9.1-r3:20090921-114819.log'.
The ebuild environment file is located at '/var/tmp/portage/app-emulation/qemu-softmmu-0.9.1-r3/temp/die.env'.


I have gcc4.x on my Amd64 Server with Cpu AM64 AM Athlon II X2 A3/2+ 245 Fam. 16 processor.

mod edit by i92guboj: added code tags. Please, use code tags (there's a button for that in the edit box) when pasting the output from programs, it makes them much more readable and preserves indentation as well. You also need to make sure the the option to disable BBCode is NOT enabled.
_________________
Gert K. Andersen
Back to top
View user's profile Send private message
i92guboj
Bodhisattva
Bodhisattva


Joined: 30 Nov 2004
Posts: 10315
Location: Córdoba (Spain)

PostPosted: Mon Sep 21, 2009 12:31 pm    Post subject: Reply with quote

So you need to install gcc-3.x, you can do so with

Code:
emerge -va "<gcc-4"


After that, you need to use gcc-config to set the right compiler version before compiling qemu.
Back to top
View user's profile Send private message
Gert Andersen
Tux's lil' helper
Tux's lil' helper


Joined: 24 Aug 2007
Posts: 138
Location: Broendby, Denmark

PostPosted: Mon Sep 21, 2009 12:42 pm    Post subject: Reply with quote

I came on thinking on try change keywords in my make.conf from "amd64" to "~amd64" and this make it now to go on with the latest ebuild 0.10.6 for it and it is on to be done, but there is some more time for it self of I prefer to make dreedos installed for dosemu.
_________________
Gert K. Andersen
Back to top
View user's profile Send private message
i92guboj
Bodhisattva
Bodhisattva


Joined: 30 Nov 2004
Posts: 10315
Location: Córdoba (Spain)

PostPosted: Mon Sep 21, 2009 1:50 pm    Post subject: Reply with quote

The problem with dosemu is not because your pc is a "server". I have no idea of what do you understand by that. But as others said, server vs. desktop doesn't make a difference. The only thing that defines a server is the use that you give to the pc. If you use the pc to browse the internet and play games then it's a desktop, if you use the pc to put a website or an irc server, then it's a server. At a given moment one machine can be both things if necessary.

That is, unless you are talking about portage profiles. In any case, if you could post the output of these two commands we would have a more accurate idea about how your system is set up, and about the package set that's available to you:

Code:
equery profile list
emerge --info


For what I can understand from the thread (and this is just me trying to guess something, because it's not clear at all), what you really meant is x86 vs x86_64. Probably, your machine had a 32 bits Gentoo (or whatever Linux you used) before, that'x x86. Now, it has a 64 bits Gentoo, that's x86_64. That makes sense because x86_64 CPUs can run 32 and 64 bits OSes without a problem.

Now, I have no idea about dosemu, never used it, but I am on x86_64 and I have just emerged dosemu without a single problem, so I am really not sure about what your problem is, unless you are using an ancient version of dosemu. Here it seems to work ok. So if you really have problems with it you will need to be more specific about the concrete problems, and start posting error messages or the exact output/feedback that you get from either emerge, dosemu or whatever is troubling you. Below there's a screenshot, look at the uname output to check that's a 64 bits system, and see the dosemu window working on top of it.

http://jesgue.homelinux.org/screenshots/dosemu.jpg

So, there's no doubt that it *does work* under x86_64.
Back to top
View user's profile Send private message
Gert Andersen
Tux's lil' helper
Tux's lil' helper


Joined: 24 Aug 2007
Posts: 138
Location: Broendby, Denmark

PostPosted: Mon Sep 21, 2009 2:13 pm    Post subject: Reply with quote

Ok, I have got dosemu to work with a cpu patch for the newer cpu's and it just now that freedos not like to work to be installed to make it working on my amd64 pc.
Here is my emerge.info from command 'emerge --info' :

Portage 2.1.6.13 (default/linux/amd64/2008.0/server, gcc-4.1.2, glibc-2.9_p20081201-r2, 2.6.28-gentoo-r5 x86_64)
=================================================================
System uname: Linux-2.6.28-gentoo-r5-x86_64-AMD_Athlon-tm-_II_X2_245_Processor-with-gentoo-1.12.11.1
Timestamp of tree: Sat, 19 Sep 2009 21:45:01 +0000
app-shells/bash: 4.0_p28
dev-lang/python: 2.6.2-r1
dev-python/pycrypto: 2.0.1-r8
sys-apps/baselayout: 1.12.11.1
sys-apps/sandbox: 1.6-r2
sys-devel/autoconf: 2.13, 2.63-r1
sys-devel/automake: 1.9.6-r2, 1.10.2
sys-devel/binutils: 2.18-r3
sys-devel/gcc-config: 1.4.1
sys-devel/libtool: 1.5.26
virtual/os-headers: 2.6.27-r2
ACCEPT_KEYWORDS="amd64 ~amd64"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=k8 -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/udev/rules.d"
CXXFLAGS="-march=k8 -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="distlocks fixpackages parallel-fetch protect-owned sandbox sfperms strict unmerge-orphans userfetch"
GENTOO_MIRRORS="http://ftp.klid.dk/ftp/gentoo/ http://ftp.snt.utwente.nl/pub/os/linux/gentoo"
LDFLAGS="-Wl,-O1"
MAKEOPTS="-j1"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage/layman/gate.junc.org"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="acl amd64 apache2 bzip2 cli cracklib crypt debug dri gpm isdnlog mmx multilib ncurses nls nptl nptlonly openmp pam pcre perl pppd python readline reflection session snmp spl sse sse2 ssl svg sysfs tcpd truetype unicode xml xorg zlib" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard" KERNEL="linux" USERLAND="GNU"
Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LANG, LC_ALL, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS

The cpu is a upgrade cpu from AMD Athlon I 2Ghz to a Athlon II X2 A3/2+ 245 Fam 16 Processor.
and when I instaal dosemu by emerge dosemu is freedos not been unpacked and compiled + installed and I got this from emerge on the screen and in the log file.

* This profile has not been tested thoroughly and is not considered to be
* a supported server profile at this time. For a supported server
* profile, please check the Hardened project (http://hardened.gentoo.org).

* This profile is merely a convenience for people who require a more
* minimal profile, yet are unable to use hardened due to restrictions in
* the software being used on the server. This profile should also be used
* if you require GCC 4.1 or Glibc 2.4 support. If you don't know if this
* applies to you, then it doesn't and you should probably be using
* Hardened, instead.

>>> Unpacking source...
>>> Unpacking dosemu-1.4.0.tgz to /var/tmp/portage/app-emulation/dosemu-1.4.0/work
* Applying dosemu-1.3.4-shm.diff ...
 [ ok ]
* Running eautoreconf in '/var/tmp/portage/app-emulation/dosemu-1.4.0/work/dosemu-1.4.0' ...
* Running aclocal ...
 [ ok ]
* Running autoconf ...
 [ ok ]
* Running autoheader ...
 [ ok ]
_________________
Gert K. Andersen
Back to top
View user's profile Send private message
i92guboj
Bodhisattva
Bodhisattva


Joined: 30 Nov 2004
Posts: 10315
Location: Córdoba (Spain)

PostPosted: Mon Sep 21, 2009 2:35 pm    Post subject: Reply with quote

Ok, now we can start clearing some of the myths in this thread.

Code:

* This profile has not been tested thoroughly and is not considered to be
 * a supported server profile at this time.  For a supported server
 * profile, please check the Hardened project (http://hardened.gentoo.org).

 * This profile is merely a convenience for people who require a more
 * minimal profile, yet are unable to use hardened due to restrictions in
 * the software being used on the server. This profile should also be used
 * if you require GCC 4.1 or Glibc 2.4 support. If you don't know if this
 * applies to you, then it doesn't and you should probably be using
 * Hardened, instead.


This message is *NOT* harmful, and it doesn't relate to dosemu specifically, you will see it every time you emerge a package, no matter which one. This means that this profile is not that well maintained, and developers have no interest in it. You should probably choose either the default/linux/amd64/10.0 profile, or the hardened/linux/amd64/10.0 one. You can see the profiles with this command:

Code:
equery profile list


And set one with

Code:
equery profile set <number>


But, as said, that message is NOT related to your problem, and has nothing to do with dosemu in any way.

Now, the real question is: does dosemu emerge? Can you post the output of emerge -pv dosemu? If it doesn't emerge we will need to see the full error message, if you are not sure what to copy/paste Just upload the whole build log file somewhere (for example, pastebin.ca) and paste a link here so we can review it.
Back to top
View user's profile Send private message
Gert Andersen
Tux's lil' helper
Tux's lil' helper


Joined: 24 Aug 2007
Posts: 138
Location: Broendby, Denmark

PostPosted: Mon Sep 21, 2009 2:56 pm    Post subject: Reply with quote

Dosemu is been merge as it shal it is just freedos-1.0-bin.tgz there not is done it by the messager of it here over.

emerge -pv dosemu:

[ebuild U ] app-emulation/dosemu-1.4.0.1 [1.4.0] USE="debug gpm X (svga)" 0 kb

I have run 'ebuild /usr/portage/app-emulation/dosemu/dosemu-1.4.0.1.ebuild unpack' and copied patch file cpu.patch into the work dosemu directory and run 'patch -p0 < cpu.patch' 3 times and got the config.c file good patch updated for family 16 processors, and then run emerge dosemu 3 times and got dosemu to work and start up with my cpu and the it is worked until it got to the freedos files to be unpacked and end there, with no palced and updated freedos files.
But the old freedos files and command interpreters gives error for wrong type and that there not is any freedos t execute dosemu longer and end up with hit a key to retur to linux.
_________________
Gert K. Andersen
Back to top
View user's profile Send private message
i92guboj
Bodhisattva
Bodhisattva


Joined: 30 Nov 2004
Posts: 10315
Location: Córdoba (Spain)

PostPosted: Mon Sep 21, 2009 3:10 pm    Post subject: Reply with quote

Well, first, sorry if this very evident, my knowledge about dosemu is very limited, but there are some things that makes not much sense to me. Maybe it's just because I am ignorant about dosemu so just bear with me.

One thing, though. You say:

Gert Andersen wrote:
Dosemu is been merge as it shal it is just freedos-1.0-bin.tgz there not is done it by the messager of it here over.

emerge -pv dosemu:

[ebuild U ] app-emulation/dosemu-1.4.0.1 [1.4.0] USE="debug gpm X (svga)" 0 kb

I have run 'ebuild /usr/portage/app-emulation/dosemu/dosemu-1.4.0.1.ebuild unpack' and copied patch file cpu.patch into the work dosemu directory and run 'patch -p0 < cpu.patch' 3 times and got the config.c file good patch updated for family 16 processors, and then run emerge dosemu 3 times and got dosemu to work and start up with my cpu and the it is worked until it got to the freedos files to be unpacked and end there, with no palced and updated freedos files.


First thing is that when you run "emerge dosemu", everything into /var/tmp/portage/dosemu* is completely deleted and recreated from the start, so your logical sequence fails, you are doing this (or at least this is what you wrote: first ebuild unpack, then patch, then emerge dosemu. This last step erases the tmp dirs and recreates them, so your patch is gone to heaven.

Besides that, I have absolutely no idea of what you mean by "run patch 3 times". A patch is applied once, and it either works or fail. A patch is not "applied three times". You will have to explain that a bit better because it makes no sense to me. Emerging dosemu 3 times doesn't make any sense either, unless it's some kind of ritual.

As for the patch itself, I have no idea what do you think that this patch does, maybe you could supply a link to it or to whatever instructions you are following... I have the same exact architecture (k8) in my CFLAGS, so the code for my machine and yours is *identical* regardless of what your physical cpu is, and here it compiles and works.
Back to top
View user's profile Send private message
Mousee
Apprentice
Apprentice


Joined: 29 Mar 2004
Posts: 291
Location: Illinois, USA

PostPosted: Mon Sep 21, 2009 3:31 pm    Post subject: Reply with quote

According to the FreeDOS build.txt file (located in the latest distribution - ke2039s.zip):

Quote:

To cross compile on Linux you need to install Open Watcom 1.8 from
www.openwatcom.org and NASM which is probably included in your
distribution. You can then copy config.m to config.mak and adjust
for the same reasons mentioned above.
----> snip <----
The recommended compiler and assembler at the time of writing (2009/05/19)
are OpenWatcom 1.8 and NASM 2.05.01.


And for the ALL IMPORTANT LINE that explains WHY you are having problems getting FreeDOS working currently:
Quote:

This kernel compiles with Turbo C 2.01, Turbo C++ 1.01 (now freely
available!), Turbo C 3.0, Borland C 4.51 & 5.01. It should work with
other Borland and Microsoft compilers and (Open)Watcom C. GCC can
compile the kernel but the result does *not* work (no 16-bit x86 support).



So basically you need to use the Watcom and NASM compilers to get FreeDOS working on your x86/x86_64 machine. It will never work otherwise, unless you use a much older machine.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on AMD64 All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum