On Thu, 21 Jul 2005 16:21:46 +0200, you wrote:
Hi,
>DEVICE=HIMEM.EXE
>DEVICE=UDMA2.SYS
>DEVICE=EMM386.EXE NOEMS X=A000-EFFF MEMCHECK VDS
>
>-or-
>
>DEVICE=HIMEM.EXE
>DEVICE=EMM386.EXE NOEMS X=A000-EFFF MEMCHECK
>
>I'm not searching for to blame a component, too many factors involved.
Better remo
I agree. It is far too risky to run the FreeDOS FDISK under any
circumstances - just based on the limited tests I have done.
I will run it ONLY on this test computer. It becomes even
more of an adventure given your analysis of the source code! :-)
Mark
> At 11:40 PM 7/21/2005 +, Mark w
At 11:40 PM 7/21/2005 +, Mark wrote:
Are any of the tests that have been suggested (other kernels,
MS-DOS, ommitting VDS, trying UDMA2, older versions of
FDISK, etc.) going to help in getting this problem fixed? I have
a repeatable problem (always a good thing) and have, I think,
done a pre
> By the way, I consider this bug extremely serious.
> The worst possible bug would trash the data instead of
> just the partition table, but this one is close! I'd be
> suprised if the FreeDOS project had very many that were
> more critical.
I tend to agree. Had a simlar bug been found "back in
Hi Michael et al:
Fiddling with this is very time consuming and a bit risky. Though,
so far, it has only been the partition table that has gotten
clobbered. And, only one machine that I know of appears to
have permanently lost all of its data as a result. The rest
have been recoverable using Li
Hello, all:
I downloaded the development kernel, SYS, and command.com files
TODAY and repeated the experiment. Everything worked
fine...the hard disk boots, is recognized, and comes up as C:.
There is no A: confusion.
I did some research and learned way more than I ever wanted
to know about volu
Hi Kenneth,
(this message just appeared, else I would have answered sooner)
Yes, I's used a different alias for this list so I could filter, and
didn't realize it was being blocked. (anti-spam measure). My fault.
the rest of the site is where I post my FreeDOS related stuff, or anyone
else w
At 04:01 PM 7/21/2005 -0500, I wrote:
When you invoke FDISK without arguments, it goes into the
Interactive_User_Interface() routine. That, in turn, asks about FAT32
support, via Ask_User_About_FAT32_Support() function. OK so far. After
that call -- without any further prompting -- FDISK ca
At 03:11 PM 7/21/2005 +, Mark wrote:
I'll try that. I'm only willing to run this on the one computer...too
risky for any others. I'm not blaming fdisk, but do not consider
running it safe. If I do not run fdisk, the disk partition table does
not get destroyed!
Well, maybe I'm wrong and
[EMAIL PROTECTED] wrote:
Yeah, some people just don't like WindowsXP. It's hard to
buy a new computer without it installed, though!
This is true, and this is why Microsoft's dominance is perpetuated. The
big OEMs collude with Microsoft, and Joe Average ends up with no choice.
The EU tried to
Hi Eric,
I think this was a reply to my post, but you didn't include original
text so it's hard to see, anyway answers in line.
Hi, I think by "as if they were IDE drives", you mean that there
is INT13 support. Actually INT13 is the only cached interface.
The others may be present at the same t
Hi,
It seems to me there are three possible reasons for the corruption:
1. Something is up with FDISK
2. Some config is corrupting the memory (e.g. EMM386)
3. Something is a big different with the BIOS or hardware in this machine
Before switching to FreeDOS, I was experiencing similar problems
The program I use to display the splash screen actually converts the
GIFs to RAW files, so in the end there is no licence problem.
---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmap
Hi Bernd:
I'll try that. I'm only willing to run this on the one computer...too
risky for any others. I'm not blaming fdisk, but do not consider
running it safe. If I do not run fdisk, the disk partition table does
not get destroyed!
Mark
> [EMAIL PROTECTED] schreef:
> > Ok, I just added edi
[EMAIL PROTECTED] schreef:
Ok, I just added edit.exe to my boot floppy! :-)
First, modifying config.sys to:
a:\device=himem.exe
a:\device=emm386.exe noems X=a000-efff memcheck vds
EMM386 reports "no suitable UMB memory block found" :-)
FDISK shows a bunch of garbage after "Do you want to use
Hi Carlos,
> > I am really against any illusions that NETWORKING would be easier than
> > CDROM.
> But do you think it could be done?
Supporting NE2000/PCI with DHCP will already support SOME percentage
of PCs. You write that QEmu and VMWare have a virtual network card,
is it ne2000 compatible?
On Thursday 21 July 2005 06:48, Blair Campbell wrote:
> Oh. Mostly what I'm looking for is graphics art for displaying while
> autoexec.bat and config.sys are loading, but if they could be
> converted to a gif somehow, they could be useful.
There are much law problems with GIFs... Why not use PNG
Hi!
Why not using Pakke as package Manager?
http://homepages.nildram.co.uk/~phekda/richdawe/pakke/
DJGPP using it and is happy with it.It needs 386+, yes, but which 8086
has a cd-rom?
Bye, Flo
---
SF.Net email is sponsored by: Discover Easy
18 matches
Mail list logo
