david lowe wrote:
I want to know if whether I can install from a floppy or if I have to
burn the files on a CD & go from there.
A floppy install is possible, I think. If there's no CD image, there is
at least the ODIN, and you can manually install that... I'm sure by the
final B9 there will
I have a system which is currently running Win98. I am considering upgrading
to FreeDOS if I can get
a CD burner. (I can say 'upgrading' with a perfectly straight face, because
I have had enough head-
aches from Winblows to make me seriously consider this option). I have a few
questions:
(Please
On Wed, 21 Apr 2004 11:26:15 -0500, you wrote:
Hi,
>We get to blame Germany today. Tomorrow France. USA gets blamed all next week.
IMO, though we speak different language and live in different place,
but Internet is a SINGLE thing that we all have responsibility to keep
it in a good shape.
Bu
On Wed, 21 Apr 2004, Eric Auer wrote:
> 2034_16 and 2034_32 are both 8086 kernels.
> 2034_16 supports FAT12 and FAT16
> 2034_32 supports FAT12, FAT16 and FAT32
yes, it's here:
http://sourceforge.net/project/shownotes.php?release_id=231835
also if you run the kernel it will say so in the beginnin
> Even at 4G max, the number of handles XMSDSK could need is 64, plus
> the HIMEM overhead for itself and EMM386 of 2 or 3. Accordingly, I am
> probably going to increase the default setting of HIMEM XMS handles to
> 72.
I would welcome 72 for default as you may anticipate from our
discussions
Hi Arkady,
2034_16 and 2034_32 are both 8086 kernels.
2034_16 supports FAT12 and FAT16
2034_32 supports FAT12, FAT16 and FAT32
FAT32 support means that the kernel needs about 3.5k more space in HMA.
And the changes are explained in history.txt, 200 lines of description
for the 2033 -> 2034 chang
Hi!
21-Апр-2004 00:10 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
BO> The present patches are just intermediate stages to get closer -- maybe
Ask again: please, remind me, ke2034_16 - is a _8086_ kernel with FAT32
or a 8086 kernel with _FAT16_? On site this is not explained
The problem with HIMEM and XMSDSK running under a 2G machine has been resolved.
XMSDSK uses 1 XMS handler per 64M memory allocated. When there are no more XMS
handles, XMSDSK seems to fail checking for a return error code, leading to a crashed
PC. This appears to be a design flaw in XMSDSK.
At 01:10 PM 4/21/2004 +0100, Bart Oldeman wrote:
>On Wed, 21 Apr 2004, Michael Devore wrote:
>
>> At 02:06 PM 4/21/2004 +0800, Johnson Lam wrote:
>>
>> >Also another application call BLASTER MASTER (Sound editor) also said
>> >"EMS Corrupt", I've asked the author, it become free now. I can email
>>
At 06:06 PM 4/21/2004 +0200, Eric Auer wrote:
>Hi, if HIMEM64 crashes but FDXXMS PS does not, try the new
>/VERBOSE and /METHOD:... command line options of HIMEM/HIMEM64
>to find out which of the A20 methods cause the troubles.
You're replying to a glop of mail that was either held or retransmitt
On Wed, 21 Apr 2004 14:52:11 +0200 (MEST), you wrote:
Hi Eric,
>Well, this is not really important, but it would help finding bugs in
>DOS programs. I found the difference when I noticed that one of my own
>programs worked better in DOSEMU than in plain FreeDOS ;-).
You still depends on DOS emul
On Wed, 21 Apr 2004 02:38:29 -0500, you wrote:
Hi Michael,
>I'm not uploading yet another EMM386 release just now for that bit of obscure support
>change, but I'll do it later on. Maybe another modification will come up before
>tomorrow breaks, make it worthwhile.
Wonderful!
You really fast i
On Tue, 20 Apr 2004 14:36:40 -0500, you wrote:
Hi Michael,
>Absolutely different. You seem to have one of the previously-theoretical machines we
>were discussing as potential a problem: a PC that has an entry condition of A20 on,
>but allows it to be turned off.
Seems this is the only one I
Hi, if HIMEM64 crashes but FDXXMS PS does not, try the new
/VERBOSE and /METHOD:... command line options of HIMEM/HIMEM64
to find out which of the A20 methods cause the troubles.
When exactly does the crash happen, did you try F8 single step
mode and combinations of DOS={HIGH,LOW},{UMB,NOUMB} and
Hi, I myself do not have time for package management in the
near future and Wolf tells by ICQ:
"For my part we can let it die, I don't have time to work on it now... ):"
did not meet Natalia on ICQ today.
I think we can at least freeze FDPM development then.
By the way, BW Basic graphics/sound ex
Eric Auer wrote:
> Hi Pat, your patches and/or MEMDISK have the problem that they do
> not DETECT which A20 setting styles work and which not!
>
> - PS/2: port 92h -> or 2 to enable, and ~2 to disable A20
> - 8042: command d1 / port 60 ... here, too, ONLY bit 1 should be messed
> with (or 2 / an
Patrick J. LoPresti wrote:
> I believe I have solved my own problem.
>
> (I am CC'ing [EMAIL PROTECTED] for complete archives, but please
> direct additional followups to freedos-devel since this is definitely
> not a SYSLINUX problem.)
>
>
> This patch uses the BIOS (INT15/AX=2400 and 2401) int
I believe I have solved my own problem.
(I am CC'ing [EMAIL PROTECTED] for complete archives, but please
direct additional followups to freedos-devel since this is definitely
not a SYSLINUX problem.)
I have been experimenting with my own himem sources. I applied the
following patch to himem64.as
Eric Auer <[EMAIL PROTECTED]> writes:
> Hi Pat, your patches and/or MEMDISK have the problem that they do
> not DETECT which A20 setting styles work and which not!
>
> - PS/2: port 92h -> or 2 to enable, and ~2 to disable A20
> - 8042: command d1 / port 60 ... here, too, ONLY bit 1 should be mess
Hi Pat, your patches and/or MEMDISK have the problem that they do
not DETECT which A20 setting styles work and which not!
- PS/2: port 92h -> or 2 to enable, and ~2 to disable A20
- 8042: command d1 / port 60 ... here, too, ONLY bit 1 should be messed
with (or 2 / and ~2). It is important to do
"Blaauw,Bernd B." <[EMAIL PROTECTED]> writes:
> (are you using UNDI driver btw for PXE, instead of DOS network drivers?)
I am using 3com's universal NDIS-over-UNDI driver. But I am not even
getting that far...
> could you leave everything identical on the bootdisk but use a MSDOS
> kernel on th
Michael Devore <[EMAIL PROTECTED]> writes:
> MEMDISK appears to give a great deal of printed feedback, based on
> the printf()'s in the code. Is there a lot of information on the
> screen from MEMDISK prior to the reboot? IF so, posting that
> information here would be handy.
Yes, MEMDISK print
(FreeDOS developers, I apologize for the redundant parts of this
message. But I want to bring the SYSLINUX folks into the discussion,
and the SourceForge mailing list archives are broken.)
Background: I have a little Sourceforge project
(http://unattended.sourceforge.net/) for which I use SYSLINU
Hi,
> > ... which reminds me that when I fail to close() in plain DOS,
> > stat() does not reflect current file size while it does in
> > DOSEMU redirection drives. The DESIRED behaviour is that only
> > after close() the stat() information (directory entry) should
> > be updated, so plain DOS is
Eric Auer wrote:
Hi, is FDPM still alive or did it get replaced by the
GUI and text mode installers which were used in beta 9.4 and 9.5?
http://www.freedos.org/bugs/bugzilla/show_bug.cgi?id=12
asks for package management in the installer, and I think at
least the GUI installer can be described as h
On Wed, 21 Apr 2004, Eric Auer wrote:
> ... which reminds me that when I fail to close() in plain DOS,
> stat() does not reflect current file size while it does in
> DOSEMU redirection drives. The DESIRED behaviour is that only
> after close() the stat() information (directory entry) should
> be u
On Wed, 21 Apr 2004, Michael Devore wrote:
> At 02:06 PM 4/21/2004 +0800, Johnson Lam wrote:
>
> >Also another application call BLASTER MASTER (Sound editor) also said
> >"EMS Corrupt", I've asked the author, it become free now. I can email
> >or upload to your FTP if you want.
>
> I grabbed Blast
Hi, is FDPM still alive or did it get replaced by the
GUI and text mode installers which were used in beta 9.4 and 9.5?
http://www.freedos.org/bugs/bugzilla/show_bug.cgi?id=12
asks for package management in the installer, and I think at
least the GUI installer can be described as having such a
fe
At 02:06 PM 4/21/2004 +0800, Johnson Lam wrote:
>Also another application call BLASTER MASTER (Sound editor) also said
>"EMS Corrupt", I've asked the author, it become free now. I can email
>or upload to your FTP if you want.
I grabbed Blaster Master off the web. Turns out that for it to run und
29 matches
Mail list logo
