Kenneth J. Davis wrote:
its all already written, I just need to add the glue logic to sys for a
user supplied boot sector instead of using compiled in one (something
I've been planning anyway).
:-)
Jeremy
Hi,
I replied to the rest of this post in detail some weeks back
(specifically
Kenneth J. Davis wrote:
I haven't examined MS sys to see if it does anything special, but
basically you need to install MS to a partition on a hard drive (any hd,
any size more-or-less); once for FAT16 and once for FAT32; and extract
that boot sector.
OK, that's not too difficult. Are you
Hi!
In sourcecode, SYS v3.6 is still under development :)
Do you know the new versions of Format and Sys, which are made Dr-DOS
compatible and has more features? You can find it at
http://www.drdosprojects.de/
Bye, Flo
--
Unofficial Dr-DOS page http://www.drdos.org
SWORD - GUI for DOS
Florian Xaver schreef:
Hi!
In sourcecode, SYS v3.6 is still under development :)
Do you know the new versions of Format and Sys, which are made Dr-DOS
compatible and has more features? You can find it at
http://www.drdosprojects.de/
if I remember correctly, this actually IS FreeDOS SYS
Johnson Lam wrote:
On Thu, 18 Aug 2005 21:59:00 +0200, you wrote:
Hi Bernd,
In sourcecode, SYS v3.6 is still under development :)
If you didn't write here, I don't even know there're hidden switch,
how can I test?
It is documented, within kernel source doc directory and at
Kenneth J. Davis wrote:
It is documented, within kernel source doc directory and at
http://freedos.sourceforge.net/kernel/docs/sys.htm
This is very nice, but how do people find it from either FreeDOS.org or
fdos.org (the sites we were given).
If I go to
http://freedos.sourceforge.net/
Kenneth J. Davis schreef:
It is documented, within kernel source doc directory and at
http://freedos.sourceforge.net/kernel/docs/sys.htm
Strange that it says WinME is unsupported, and doesn't mention if Win9x
FAT16/32 bootsector works or is (still) broken.
somewhere 'segent' -- 'segment'
Bernd Blaauw wrote:
Kenneth J. Davis schreef:
It is documented, within kernel source doc directory and at
http://freedos.sourceforge.net/kernel/docs/sys.htm
Strange that it says WinME is unsupported, and doesn't mention if Win9x
FAT16/32 bootsector works or is (still) broken.
somewhere
Hi,
Regarding the MS install issue, one could do something like format with
FreeDOS format, then use FreeDOS sys to install MS-DOS files/bootsector
via its /UPDATEBS (and obtained by its /DUMPBS, winimage, any other
bootsector extracting program, or even from a disk image), etc.
Yes, that's
Hi Bernd,
Here are the latest tests from today using the new SYS 3.6; it did not
solve the problem, but the issues are narrowed down. It all comes down
to getting an MS boot sector onto a FAT16 partition, but without any
other system files (IO.SYS etc). The first test below which failed, is
Gerry Hickman schreef:
Perhaps the simple solution is to have a SYS command line switch, that
allows the end-user to install a 512b boot sector of their choice to the
target partition? This would get round any copyright issues and make it
very flexible. I don't think this is possible with the
Hi Bernd,
Bootsectors contain geometry (disk/partition layout information) which
can change.
So this is all a matter of just copying bootsectors and omitting system
files, it seems.
I don't understand this statement. Do you mean to say So this is _not_
a matter of just copying bootsectors.
Gerry Hickman schreef:
I don't understand this statement. Do you mean to say So this is _not_
a matter of just copying bootsectors. If it _is_ a matter of just
copying bootsectors, why does it seem so difficult to make it work? We
just copy the boot sector and live happily ever after?
Hi Bernd,
OK, in that case the whole thing is much more complicated than I
realized. The only way this could ever work is if FreeDOS SYS or FORMAT
could emulate the MS boot sector _and_ geometry behavior. As you say,
WinImage does seem to manage this.
In terms of copyright, the end user
On Thu, 18 Aug 2005 21:59:00 +0200, you wrote:
Hi Bernd,
In sourcecode, SYS v3.6 is still under development :)
If you didn't write here, I don't even know there're hidden switch,
how can I test?
Without enough testing, more delay to an official release ... this
function may help to installing
Gerry Hickman wrote:
Hi Kenneth,
can't work out how these numbers relate to the directory listing on the
fdos.org/kernel website.
4 different versions,
2034, 2035, and 2035a are on sourceforge file release page,
cvs kernels are the ones (either stable, eg 2035a-cvs or devel
2035w-cvs) on
Hi,
Thanks for the help finding the files! Here's the original text from
Bernd, note where he says 'unofficial'/'development', and gives 'fdos'
as the site:
just get the 'unofficial'/'development' versions of components.
*SYS 3.6 from www.fdos.org/kernel (sys.dev.com)
*kernel 2034, 2035,
*kernel 2034, 2035, 2035A and the CVS kernel
I see 2.0.35a on SourceForge, so that must be the Kernel I need.
Sorry, I've just realized I'm already running kernel 2.0.35a :)
--
Gerry Hickman (London UK)
---
SF.Net email is Sponsored by
Hi Blair,
Of course you only want MS boot sector, not MS kernel, for the Win2k
install versus dual-boot-not-wanted problem. MS DOS 6 supports no
FAT32, so for FAT32, you would use a MS Win9x FORMAT style boot
sector.
Yes, I think that's what we're heading towards - FreeDOS being able to
Hi Bernd,
I can confirm this: strangely upgrading from DOS 6.22, Win2000setup
doesn't finish and I get a spontaneous reboot during last phase of setup.
I've not seen this before, it could be specific to the box.
--
Gerry Hickman (London UK)
Hi Kenneth,
can't work out how these numbers relate to the directory listing on the
fdos.org/kernel website.
4 different versions,
2034, 2035, and 2035a are on sourceforge file release page,
cvs kernels are the ones (either stable, eg 2035a-cvs or devel
2035w-cvs) on fdos.org
I'm
Bernd Blaauw wrote:
just copy IO.SYS, MSDOS.SYS and COMMAND.COM to C:,
then do SYS A: C: /BOOTONLY /OEM:MS
and reboot system.
Then check if MSDOS boots first, and only when it does,
install Windows.
I ran a similar test today, and got an unexpected result.
Using standard FreeDOS:
1. Booted
Hi Bernd,
I've printed this out, I think I understand the important points and I'm
happy to run some tests, but can you clarify the exact files I need to
download. I currently have the latest stable kernel, command, and sys
files. My kernel says it's 1.1.35 and my sys says it's v3.2 - I want
Bernd Blaauw wrote:
just copy IO.SYS, MSDOS.SYS and COMMAND.COM to C:,
then do SYS A: C: /BOOTONLY /OEM:MS
and reboot system.
Then check if MSDOS boots first, and only when it does,
install Windows.
I ran a similar test today, and got an unexpected result.
Using standard FreeDOS:
1. Booted
Hi Bernd,
just get the 'unofficial'/'development' versions of components.
*SYS 3.6 from www.fdos.org/kernel (sys.dev.com)
OK, I got this one from the hyperlink on the front page.
*kernel 2034, 2035, 2035A and the CVS kernel
Sorry, I don't understnad. It looks like four different files
Hi Bernd,
just get the 'unofficial'/'development' versions of components.
*SYS 3.6 from www.fdos.org/kernel (sys.dev.com)
OK, I got this one from the hyperlink on the front page.
*kernel 2034, 2035, 2035A and the CVS kernel
Sorry, I don't understnad. It looks like four different files
Hi Bernd,
I've printed this out, I think I understand the important points and I'm
happy to run some tests, but can you clarify the exact files I need to
download. I currently have the latest stable kernel, command, and sys
files. My kernel says it's 1.1.35 and my sys says it's v3.2 - I want to
Gerry Hickman schreef:
Hi Bernd,
I've printed this out, I think I understand the important points and I'm
happy to run some tests, but can you clarify the exact files I need to
download. I currently have the latest stable kernel, command, and sys
files. My kernel says it's 1.1.35 and my sys
Picking up on this topic, I ran into a serious problem today when trying
to use the FreeDOS SYS command to fix the problem discussed below.
Except I'd completely misunderstood the command line options for my
version of FreeDOS SYS and what it can and can't do! See below...
4. SYS a: c:
Hi Bernd,
Picking up on this topic, I ran into a serious problem today when trying
to use the FreeDOS SYS command to fix the problem discussed below. The
summary of the original problem is this:
Using DOS 6.22 [FDISK FAT16 FORMAT] creates a C: drive that you can then
use to install Windows
Hi,
I've been testing FreeDOS as a Pre-build environment for server and
client Windows builds. In general, everything with FreeDOS is far better
than MS-DOS or real-mode Win95/98/ME. However, I'm now at the stage of
actually building the real PCs and have run into a small but
time-consuming
FreeDOS Beta9sr1:
1. FDISK /CLEARALL
2. FDISK /MBR
3. FDISK /PRI:2000
Not sure if this is the problem, but try without fdisk /mbr
---
SF.Net email is Sponsored by the Better Software Conference EXPO September
19-22, 2005 * San Francisco,
Gerry Hickman schreef:
FreeDOS Beta9sr1:
1. FDISK /CLEARALL
2. FDISK /MBR
3. FDISK /PRI:2000
4. reboot
5. FORMAT C:
6. Start real-mode windows setup program
7. Windows is installed, but now it presents a boot loader menu every
time it starts with a 30 second timeout. Windows has even kindly
But as far as I know FDISK /CLEARALL will remove the MBR. If I don't put
it back, the hard drive will NOT boot at all when Windows setup calls
the reboot code...
The hard drive will not boot, but the Windows CD should be able to.
Unless it is Win95.
Hi Bernd,
FreeDOS Beta9sr1:
1. FDISK /CLEARALL
2. FDISK /MBR
3. FDISK /PRI:2000
4. reboot
5. FORMAT C:
6. Start real-mode windows setup program
C: is NTFS, FAT16 or FAT32?
If you look at Step 3 above, you will perhaps agree that C: is FAT32?
Unknown bootsectors are indeed saved to file
Hi Blair,
But as far as I know FDISK /CLEARALL will remove the MBR. If I don't put
it back, the hard drive will NOT boot at all when Windows setup calls
the reboot code...
The hard drive will not boot, but the Windows CD should be able to.
Unless it is Win95.
Perhaps a misunderstanding?
Perhaps a misunderstanding? I'm not using a Windows CD, I'm building
over the network. You basically put an image of your o/s with
customizations on a network share, boot to FreeDOS, create temporary
partition on the first physical hard-drive, then run the Windows setup
program. The setup
37 matches
Mail list logo
