Am Dienstag, 25. Juli 2006 19:11 schrieb Blair Campbell:
I tested also in this morning and I have found the old bug in
command/084pre/ testing
problem is: path=C:\fbb;c:\bpq doesn't work
It does not change from the root in a workpath around there a batch file
to implement.
I don't
At 09:31 AM 7/25/2006 +0200, Norbert Remmel wrote:
As promised detailled error description...
PC description:
Intel Pentium III 600 MHz
256K Cache
ASUS P2B Motherboard (Intel 440BX Chipset, AWARD ACPI Bios Rev. 1012)
384 MB SDRAM (133 MHz)
3COM 309B 10/100 PCI Ethernet Adapter
Config.sys
At 02:20 PM 7/24/2006 +0200, Japeth wrote:
I was advised (thanks Eric!) that there exists a SB option for FD-Emm386.
Setting this option indeed cures the SB MPU issues for the protected-mode
games I tried.
The SB option is easily the goofiest option I've added to any program I've
worked on in
At 07:56 AM 7/24/2006 +0200, Japheth wrote:
But: DOOM does work with the current himem/emm386.
As for me this is true for the newest versions of himem/emm386 (July 2006)
only. In fact, any DOS4G application didn't work with FD-Emm386 previously
because my machine has 768 MB.
Generally
As a matter for record, since it's been incorrectly reported twice now:
FreeDOS, HIMEM, and EMM386 work fine with Doom. It was one of the first
tests of VCPI support and is often checked against as a baseline. There
are no known applications which fail under FreeDOS HIMEM or EMM386 with the
At 06:20 PM 7/18/2006 +0200, you wrote:
There is a bug left in the FD-Himem.exe memory manager.
Nope. But see further...
When a program that had allocated several XMS blocks doesn't release these
blocks in the order FD-Himem likes it, it will report a too small largest
free block. Luckily the
At 09:21 PM 7/12/2006 -0400, Keith Weisshar wote:
Microsoft just released VPC 2004 as freeware today. When I install from
the FreeDOS ISO under VPC 2004 I get an CRC error on mode.com with missing
required package.us during install and at the end of the install and I
reboot I get a missing
booting from DVD/CD drive.
bye
Flo
Hi Flo,
X-FDISK ist sehr schön zum Arbeiten, den nehme ich auch bei sehr vielen Sachen
und das toll funktioniert, wobei ich mit dem vom FreeDOS so meine Probleme
schon hatte, was FAT32 anging.
Gruß Michael
Uploaded to ftp://ftp.devoresoftware.com/downloads/emm386/ are the files
emmx210.zip, EMM386 version 2.10 and HIMEM version 3.13 memory managers,
mostly executables; and emms210.zip, source code files for the new release.
The latest revisions (effectively completed in May) contain several
At 10:18 PM 7/8/2006 -0500, Michael Devore wrote:
a bunch of stuff, but forgot to mention something people asked me about
earlier
I used the newest release UPX 2.01d to compress this version of EMM386 and
HIMEM. It saved about 400 bytes for EMM386.EXE and 200 bytes for HIMEM.EXE
over the old
At 04:39 PM 7/3/2006 -0500, Neal Gompa wrote:
Yet, without much modification to the configuration of the system, and
grabbing some proprietary utils, it cannot run Windows for Workgroups...
It is better, I agree, but to be fully compatible, it should run one of
the most complex apps out of the
At 01:19 PM 6/21/2006 +0200, you wrote:
Hello! It's me again.
I changed my compiler back to Open Watcom 1.1, because 1.2
can't compile the Duke Nukem 3D source code. :)
But now, I have a problem: it comes with an old version of
CauseWay, and I don't know how can I update to the latest
CW. Can
At 08:26 AM 6/15/2006 -0500, jp_freedos wrote:
On Thu, Jun 15, 2006 at 07:44:08AM -0500, Jim Hall wrote:
I'm sorry my president's an idiot. I didn't vote for him.
Clinton is not President anymore.
Clinton was, among other things, a Rhodes Scholar, and generally conceded
as brilliant by his
At 11:38 AM 6/5/2006 -0400, John Hupp wrote:
I could also have added that all my DOS games (Doom, Quake, Duke,
Spacequest, Beneath A Steel Sky) run fine on this computer and configuration.
On the chance that there was a physical memory problem I dropped from 16
to 8 MB (no difference), and
At 12:09 AM 5/6/2006 +0300, dima wrote:
This is screenshot with error message:
http://www.geocities.com/x696365/stuff/xcomap01.zip
Okay, final progress report for a while. I installed new DOS sound drivers
on the old machine. After the installation I was able to successfully run
the xcom
At 04:23 AM 5/6/2006 +0800, someone who refuses to directly face those he
accuses wrote:
As far as I remember, Jack did not want to tell us about the
four (if I remember correctly) critical bugs in himem/emm386,
so Michael cannot fix them either. He only told us THAT there
are bugs, but did
At 08:11 PM 5/6/2006 -0500, I wrote:
I happen to believe that FreeDOS HIMEM probably does still contain an
obscure bug or two. Maybe even three.
I did fix a fairly obscure HIMEM bug today, as a matter of fact. Haven't
found anything which needed the fix, but it was definitely a
At 12:09 AM 5/6/2006 +0300, dima wrote:
Game won't to run without himem and emm386 or fdxxms and umbpic, cause not
enough memory.
Okay, I stole a 48M Pentium 133Mhz laptop from the clutches of a Cro-Magnon
in a passing time-rift and tried the game out on that. Under FreeDOS
SETUP.EXE still
At 11:28 PM 5/5/2006 +0800, Johnson Lam wrote:
Mister,
I also don't like this sort of extremely early speculation coming on the
heels of Mr. Lam's recent spate of ridiculous posts, because it just feeds
Thank you for your praise.
into him posting more irrelevant advice about trying alternate
At 12:09 AM 5/6/2006 +0300, dima wrote:
Game won't to run without himem and emm386 or fdxxms and umbpic, cause not
enough memory.
I found that it also helped to run the game with DOS32A
instead of the built-in DOS4GW. You can get it here:
Yes, sometimes it helps. But in this case I have
At 12:02 AM 5/5/2006 +0300, dima wrote:
Hello.
Does anyone there have experience about how to run x-com apocalypse under
FreeDOS?
Send the game to me or tell me where to grab it; I'll take a look.
---
Using Tomcat but need to do more?
At 04:48 PM 5/3/2006 -0400, Mark Bailey wrote:
Thanks very much. I'll have Steve try to trace the problem.
I am rather DOS illiterate, I'm afraid. What do you mean by
Will the SCSI base address conflict? Do you think the BIOS
grabs some high memory that emm386 might affect? The
current
At 09:04 PM 5/2/2006 -0400, Mark Bailey wrote:
Bad or missing Command Interpreter
Enter the full shell command line:
command.com /P /E:256
The development kernel fixed the Error in the DJ mechanism! but still
doesn't find the shell. Any suggestions? Is there a problem with SCSI
drives?
At 01:43 PM 4/19/2006 +0800, Johnson Lam wrote:
Forward an email from Jack, hoping everyone can understand what's
going on, I'd like the others to understand the whole thing, not out
of context:
snipped
It is a flame, as you well know, but it seems you have become immune to any
sense of
At 01:17 PM 4/17/2006 +0800, Johnson Lam reposted a private e-mail:
that should never have been publicly reposted
What I suggest you reflect upon, Mr. Lam, are your personal reasons for
posting this entire private e-mail to the public list. It serves little
purpose here other than to incite
At 09:29 AM 4/15/2006 -0400, you wrote:
So I added back a range exclusion, thus: NOEMS X=A000-EFFF VDS NOALTBOOT.
This booted up in unstable condition, locking altogether (or with
Ctrl-Alt-Del still not working).
I increased the exclusion to the range that one of you had recommended:
NOEMS
QHIMEM is a totally new and alternate -- utterly superfluous in my opinion
-- memory manager that can have nothing to do with your problem, and I do
not recommend it's use for debugging here.
There is no correlation between the HIMEM-style memory manager and an
application's use of upper
At 06:15 PM 4/14/2006 -0400, you wrote:
Hello, all. Here is another issue arising from my check-out of the new
Service Release 2.
I find that loading EMM386.EXE can cause Ctrl-Alt-Del to fail. I boot
fine, then press Ctrl-Alt-Del from the DOS prompt. The screen goes black,
but the video
At 10:55 PM 3/21/2006 +, FreeDOS Ankreuzen wrote:
Yes on some mainbords PC s with PENTIUM II, there is a problem
to install FDOS BETA 9SR2 from CD.
If it s possibel use a Bootdisk with old FreeDOS Version
and pre-install FreeDOS manually.
Please tell me if you are using a Pentium II or
At 02:07 PM 3/25/2006 -0600, I wrote:
As an alternate choice, you might try locating the actual problem, which
likely is not within EMM386 itself, rather than telling people to use
obsolete versions of software which won't fix the underlying problem and
which fail to provide a full range of
Hi,
I want to know if the original FreeDOS kernel is 16bit or 32bit. I ask it because I coincidentallyfound the website http://freedos-32.sourceforge.net/and I want to use 32bit tools in FreeDOS, too (perhaps).
Thanks for answer.
P.S.: Answering in german language is preferred for me but
At 07:36 AM 3/17/2006 -0800, Andrew Greenberg wrote:
Hi everyone,
HIMEM64 3.11 [Apr 09 2004] has worked solidly for us across many
machines. We thought we'd try the latest version, HIMEM64 3.12
[09/11/2005] but it consistently is freezing on us, especially on thinkpads.
Booting from a CD, with
At 04:50 PM 3/17/2006 -0800, Andrew Greenberg wrote:
-
DEVICE=A:\DRIVERS\HIMEM.EXE
SHELL=A:\COMMAND.COM A:\ /E:1024 /MSG /P=A:\AUTOEXEC.BAT
DOSDATA=UMB
DOS=HIGH,UMB
FILES=20
BUFFERS=20
LASTDRIVE=Z
SET BOOTDISK=A:
SET DIRCMD=/p /ogn
SET
At 11:09 AM 3/15/2006 +0300, Arkady V.Belousov wrote:
MD If I start up FDISK, it sees a partition on the USB
MD stick. If I then use FDISK to remove that partition, afterwards the USB
MD stick cannot be accessed by FreeDOS tools (including FORMAT or DEBUG) or
MD Windows re-format.
Of
At 12:07 PM 3/15/2006 +0300, Arkady V.Belousov wrote:
15-íÁÒ-2006 02:36 [EMAIL PROTECTED] (Michael Devore) wrote to
freedos-user@lists.sourceforge.net:
MD Yes. Creating a new partition with FDISK doesn't work. It thinks it
MD works, but the stick remains unusable until the HP tool reformats
At 09:27 AM 2/28/2006 -0500, Mark Bailey wrote:
Hi Michael:
I received a sealed envelope from you yesterday. It contained
a card with a note about a white cover but no USB stick! :-(
Did the stick fall out or something?
Ha, if there's not a hole somebody nabbed it. And it was worth a whole
At 03:46 PM 2/28/2006 -0600, charlie_chan wrote:
As a postal worker for 22 years, I will tell you with certainity that if
you use an envelope to mail it you made
a mistake. Every post office that processes mail and some that don't have
a collection items that should
never have been mailed in
Hi,
I ask me if FreeDOS can read and use Hardlinks. And if it isn't, is there a tool which makes it possible?
Thanks a lot.
Regards from Germany.
P.S.: You can answer me in german, too.
Aber solange ich die genannten Programme nicht aufrufe, ginge es, oder ?!
DOS ruft die Programme doch nicht etwa beim Booten auf, solange sie nicht in der autoexec.bat stehen?!
Am 13.02.06 schrieb Florian Xaver [EMAIL PROTECTED]:
Hi!Meinst du mit Hardlinks Datei-Links die auf einen anderen Eintrag
Hi,
does a firewall for DOS exist? If it is, where can I find it?
Thanks a lot.
Regards
McStarfighter
P.S.: You CAN answer in german, too.
Oh yes I know what a firewall is. For MS-DOS i know that there is now firewall need, but DR-DOS / FreeDOS is perhaps another thing. Ok, there is no firewall and that is all I wanna know. Thanks to you.
2006/2/13, Robert Riebisch [EMAIL PROTECTED]:
Michael McStarfighter wrote: does a firewall
Hi,
I ask me all the time if applications, which are written for MS-DOS, are compatible for working in FreeDOS. I know the question can't have a general answer but perhaps some additional thoughts can help me. Thanks a lot.
P.S.: (written in german) Antworten in Deutsch wären mir am liebsten,
Hi,
is it possible to get r/w access to NTFS? I have the Winternals Admin Pack 5.0 which includes the NTFSDOS driver, but I don't know how to integrate it into FreeDOS. And ATM I can't find about native access to NTFS from FreeDOS.
The same question I have about USB access.
Thanks a lot.
At 09:17 PM 1/18/2006 -0800, Caleb9849 wrote:
ARG! Can someone please help me with this? I'm trying to run an old DOS
Star Trek Game of mine. By DOS standards, it's pretty resource-heavy and
requires upper memory. So I added the lines into my fdconfig.sys to load
up emm386.exe (with the
At 12:44 AM 12/25/2005 +1100, John Mills wrote:
Thanks for info. I'm out of my depth here.
Apologies to anyone misled by my suggestion.
My EMM386 is version 1.13.
Current EMM386 version is 2.08. You're one major release, many minor
revisions, and a number of recommended updates behind.
At 12:53 PM 12/24/2005 +1100, John Mills wrote:
alan
Don't know if your program uses DPMI, but some out of memory problems can be
solved by disabling memory drivers e.g. EMM386/HIMEM, and letting DPMI take
over extended memory.
Nothing to do with a modern, e.g. FreeDOS version, HIMEM or
At 11:02 PM 11/28/2005 -0800, Blair Campbell wrote:
I would personally really appreciate the ASM in FreeDOS HELP being a
test case, as this assembler won't even compile with Arrow Assembler
or the Watcom Assembler (which both use older MASM/TASM syntax,
afaik).
The only ASM file I found in
At 01:27 PM 12/3/2005 -0600, I wrote:
The three people following to this point might wonder why Nomyso doesn't
just eliminate the 'DWord' in the $DEFINE statement and eliminate the
problem. Well, you can't automatically do that because the DWORD would be
necessary in some cases where you
At 07:15 PM 12/1/2005 +, Gerry Hickman wrote:
What we do know is this:
2. EMM386 with SCSI controllers and VDS enabled is completely unusable and
should never be tried outside the test lab.
What? Completely untrue. More like 2. EMM386 with SCSI and VDS works on
all tested systems,
At 11:02 PM 11/28/2005 -0800, Blair Campbell wrote:
Speaking of bugfixes, a person on FreeDOS IRC has mentioned many times
that the latest versions of HIMEM/EMM386 won't work with certain hard
drives, but will work with others. AFAIR, he also says that NOVDS
does nothing to change this.
Uploaded to ftp://ftp.devoresoftware.com/downloads/emm386 are the files
emmx208.zip, EMM386/HIMEM mostly executable package (EXEs compressed via
mutant UPX), and emms208.zip, EMM386/HIMEM mostly source package. Nomyso
version 2.0 was uploaded to ftp://ftp.devoresoftware.com/downloads/nomyso
At 08:38 PM 11/24/2005 +0100, you wrote:
Anyone else seeing massive virus outbreaks?
I never imagined being able to use 40% of a 250MB hotmail emailbox (add 3%
each hour), but MS manages to not filter these (75KB attachment).
Even the delete junkmail button times out with 1400 emails.
Pretty
At 08:46 PM 11/23/2005 +0800, Johnson Lam wrote:
I have a problem with the SBPCI Sound Driver under FreeDOS, could
someone help me ?
You got the same problem as me, but I'm using SBLIVE.
Try to use:
device=c:\fdos\bin\emm386.exe memcheck x=test ems=1200
If you are using the latest EMM386
At 08:25 PM 11/22/2005 +0100, Almacha wrote:
I have a problem with the SBPCI Sound Driver under FreeDOS, could someone
help me ?
When I use the default configuration for HIMEM and EMM386 :
DEVICE=C:\FDOS\BIN\HIMEM.EXE
DEVICE=C:\FDOS\BIN\EMM386.EXE
I have then 32MB of EMS.
and then I try to
At 11:29 AM 11/17/2005 -0800, Quentin Liedtke wrote:
I'm having a real tough time trying to get FreeDOS to boot from a USB
flash drive and I'm hoping that the fine folks on this list might be able
to help me.
Hardware I'm using:
- I'm using an Intel D865GBF motherboard with BIOS version
At 10:29 PM 11/15/2005 -0800, Brolin Empey wrote:
Michael Devore wrote:
And another warning: NASM done got it some bugs. Even with the
relatively modest source of HIMEM, I hit a couple.
Have you told the NASM maintainers about these issues? I think they would
probably be interested
Message Clarification #3. It's the HX DOS Extender, nor HRX.
Such are the fruits of staying up all night to get the thing out the door.
To make this slightly more useful, here are links to items mentioned in the
original message:
HX Extender: http://www.japheth.de/HX.html
Cygwin site (you
Message clarification #1: The converter file is named nomyso10.zip, not
nomyso.zip
Message clarification #2: NASM may generate harmless warnings if you
recompile other MASM/TASM source code, making complaints about redefinition
of segment attributes. Test files show these warnings are
Andre Tertling [EMAIL PROTECTED] said
Hi there,
recently, I read quite some discussion about network support under DOS
on this list, but couldn't make up a consistent picture from the details
mentioned. That is why I would like to ask for more information and
especially about what
At 02:27 PM 10/11/2005 -0700, Blair Campbell wrote:
bypassed. After three days of on-and-off hacking on it, I built a mutant
UPX 1.25 to compress EMM386.EXE and HIMEM.EXE to work both as a device
driver and as a stand-alone EXE file. As almost always is the case, the
actual changes were
At 11:25 PM 10/11/2005 +0200, Bernd Blaauw wrote:
Markus Oberhumer seems to have his own website and seems quite active.
Maybe he's interested in your patch.
It's not in a good patch form consistently matching the rest of the source,
but rather a basic hack to make things work. Also, it
At 12:39 AM 10/11/2005 +0200, Bernd Blaauw wrote:
Again a nice theoretic discussion :) Anyway, are FreeDOS related programs
and drivers also ment to be used on MSDOS or not as partial replacement?
The drivers could be used on MS-DOS freely, it is only the control programs
which would extend
At 02:36 PM 10/9/2005 +0400, Arkady V.Belousov wrote:
And how this should be look? Drivers doesn't return errorlevels,
whereas INSTALL= executed after DEVICE=.
MD Perhaps you could have it conditional on a register return value from an
MD application,
Even if I introduce new
At 11:28 PM 10/10/2005 +0400, Arkady V.Belousov wrote:
MD %IF CHECK386 DEVICE=EMM386
Why to duplicate checks, which already present in himem and emm386?
Why depend on on drivers to unload cleanly if they fail, which they already
do not always do in closed-source drivers, despite
At 11:30 PM 10/8/2005 +0400, Arkady V.Belousov wrote:
MD We've discussed loading HIMEM at the DOS prompt after CONFIG.SYS
processing
MD before, too. It's a bad idea that could easily open the floodgates of bug
MD reports for people wondering why their drivers aren't loading or working
MD
At 03:01 AM 10/9/2005 +0400, Arkady V.Belousov wrote:
MD As the front line guy taking most of the tech support on EMM386 (and
MD HIMEM), I herewith state that you are incorrect. HIMEM delayed loading
I _not_ say about loading HIMEM from command line, I say about CPU
detection and
At 04:46 AM 10/7/2005 +0200, Eric Auer wrote:
The test already is performed inside the driver, and cannot be performed
in an errorlevel-generating tool. Because errorlevels are not used in
context of DEVICE=... loading. The autoconfigure would look like this:
DEVICE=HIMEM...
DEVICE=FDXMS286...
At 11:13 PM 10/4/2005 +0200, Eric Auer wrote:
various statements which would be unproductive to rehash my disagreements
with
and
The errorlevel thing would also have the problem that EMM386 and HIMEM
are device drivers. You cannot do if errorlevel ... in config sys, so
the suggested
At 11:19 PM 10/3/2005 -0700, Blair Campbell wrote:
Hi. Just wanted to let everyone know that I've copied the Post-1.0
todo list to the FreeDOS wiki so that everyone can view and edit the
list of items. It is available at:
http://wiki.fdos.org/Main/Post_1_0_Todo
No way I can see to discuss a
At 01:11 PM 10/4/2005 +0200, Eric Auer wrote:
soon please - would be nice to have that soon after FreeDOS 1.0, e.g.
before 2.0, for example: several EMM386 / HIMEM
features
aka, none. EMM386 is quite deliberately versioned at 2.x because it's
moved beyond what is needed and necessary
At 04:42 PM 9/21/2005 -0700, Brolin Empey wrote:
FastTracker 2.08 runs fine for me under latest HIMEM and EMM386.
PKUNZIP failing unless the NOEMS option is specified, now that's a
problem I'm working on.
EMM386 v2.05 breaks my FDCONFIG.SYS! When booting, I get the following output:
At 05:48 PM 9/21/2005 -0700, Blair Campbell wrote:
it sounds like VDS again to me. That has the effect that no
I think that it'd be really nice to have a utility to detect the
instances where VDS would fail because then distros like mine can add
the NOVDS option in the installed config.sys
At 11:21 PM 9/19/2005 +0100, you wrote:
A better option would be to get to the bottom of why SCSI and VDS do not
like each other. SCSI is a drive interface - I don't see how it can be
affected by VDS unless there's something bigger going on. It may he SCSI
is merely showing up the problem, as
At 05:05 PM 9/19/2005 -0700, Brolin wrote:
Firstly, I have not tested this new release. That said, what is the status
with regards to having FastTracker II working on FreeDOS? My FreeDOS
installation consists mainly of what was distributed with the Beta9 SR1
CD, so some of the components may
Uploaded to ftp://ftp.devoresoftware.com/downloads/emm386 are the files
emmx205.zip, EMM386/HIMEM mostly executable package, and emms205.zip,
EMM386/HIMEM mostly source package.
This version of EMM386 has a number of compatibility changes to enhance
operability with a variety of DOS
On Thu, 25 Aug 2005 Blair Campbell [EMAIL PROTECTED] said:
Hi all! I finally have a permanent place to put my DOS ports of
software. At http://johnson.tmfc.net/freedos/blair/index.html, you
can find my (considered stable) ports of Speex and vorbis-tools, and
my experimental ports of
On Mon, 22 Aug 2005 Johnson Lam [EMAIL PROTECTED] wrote:
Hi,
I heard of a novel netware emmulator for linux and since here are=20
running allready a lot of linux boxes i thought of using this. does=20
anyone has a idea how to setup this? it seems i do something wrong, at=20
least the
At 04:38 PM 8/10/2005 +0200, up wrote:
Looks like you're not using the latest HIMEM and EMM386, which might make a
difference. Without the EMS report on MEM, I can't tell what the EMS
allocation is, either.
I don't need EMS at all. Only good thing from emm386 is ability to
load some tsr's
At 01:46 PM 8/7/2005 +0100, Gerry Hickman wrote:
I then rebooted without VDS and everything worked correctly.
I then rebooted with VDS again, and everything was messed up.
Thing is, I have no idea what VDS is for, and don't know if I'd ever need it!
When VDS becomes a default option, either
Okay, if you've been following the VDS bouncing ball, be aware there is now
a new EMM386 test release, called emmchimp.zip at
ftp.devoresoftware.com/downloads/emm386 which does fix the problem using
the VDS option of EMM386 on the original problematic HP Pavilion laptop.
How do I know?
At 01:08 AM 7/31/2005 +0100, Gerry Hickman wrote:
Oh good grief. EMM386 doesn't have the code or capability to mess with
disk partitions. Period.
But if drive geometry is being misreported or misunderstood under EMM386
with VDS (which appears to be the case), then my guess is that it would
At 03:38 AM 7/30/2005 +, Mark Bailey wrote:
I see no difference at all with that version, either with the
development kernel/command.com or the stable kernel/
command.com.
Specifically, with
device=a:\himem.exe
device=a:\emm386.exe x=test memcheck vds
vol c: hangs. Remove vds, it works
At 04:05 AM 7/30/2005 +, Mark wrote:
Hi Michael:
Well, the E000 message is repeatable on this box...
Found that problem. A matter of the EMS routines not properly reporting
failure to locate a suitable page frame. Instead they fell through and
reported the default page frame. I
At 04:05 AM 7/30/2005 +, Mark wrote:
Well, the E000 message is repeatable on this box...
Thanks again for all of your help!
Well, we can check if your VDS vector is okay pretty easily. Try this with
the test EMM386 using VDS option. Don't type VOL first to crash things or
load UDMA.
At 09:32 PM 7/30/2005 +0200, Bernd Blaauw wrote:
1) harddisk present, but unpartitioned and not formatted
d 0:12C
U 0307:0145
U 0307:0180
output:
MOV BYTE PTR CS:[0084],00
CMP AL,02
JZ 01E1
You're not using test EMM386 is what that indicates. No test for AL equal
to zero, as was added.
At 08:23 PM 7/30/2005 +0100, Gerry Hickman wrote:
Ah, yes, ... :-) Try emm386 without the VDS argument and under no
circumstances run FreeDOS FDISK unless you want to risk an erased
partition table.
Can you clarify; when your partition table became damaged, were you
running EMM386 at the
At 10:13 AM 7/29/2005 +, Mark Bailey wrote:
This appears to be the same bug that caused FDISK to
wipe out the MBR, so it at least appears that just initializing
the VDS functions is trashing something in memory.
No such thing. VDS functions just are, they don't initialize. Only thing
At 12:42 PM 7/29/2005 -0500, I wrote:
Ha! That's it. Some SCSI BIOS uses INT 4BH. It must be passing the
register value that VDS interprets as a VDS function, which means AH =
81h. Hmm, let me look things over to see if there's a way to resolve the
conflict by further determining the
At 02:58 PM 7/29/2005 -0400, Mark wrote:
Does this provide a means of easily identifying the affected
machines? How do I check the Haunted HP Pavilion? :-)
Here's what to do:
Go to ftp.devoresoftware.com/downloads/emm386 and download
EMMBLORT.ZIP. Try that version of EMM386.EXE with your
At 10:05 PM 7/29/2005 +0200, Bernd Blaauw wrote:
Michael Devore schreef:
Go to ftp.devoresoftware.com/downloads/emm386 and download
Let me know if that fixes or modifies the current behavior with VDS
parameter.
no change in VMware Workstation 4.5.2 (PC emulator, Intel P4 processor
At 03:07 AM 7/30/2005 +, Mark Bailey wrote:
VOL C: works normally. Without device=a:\udma2.sys,
vol c: hangs and forces a reboot. (That's the old behavior
which I checked to make sure of the test case).
This does not appear to be a seperate issue.
Actually it muddies the waters by
At 11:53 PM 7/28/2005 +, Mark wrote:
Do I need VDS? :-) What does it do? How can I help
identify the problem? I do have the Haunted HP Pavilion (TM)!
Turn it off if everything works without it. It's just for upper memory
reporting of true physical address instead of logical address
At 12:22 AM 7/28/2005 +, Mark Bailey wrote:
Help! How do I start to debug this?!?! This is the same machine
which has FDISK overwriting the partition table whenever it is run
with EMM386.
Exclude all high memory via X=A000-EFFF and add NOEMS option. Those two
options only, unless your
At 01:29 AM 7/26/2005 +, Mark Bailey wrote:
I have another FreeDOS problem with NTFS4DOS. This one DOES
NOT affect MS-DOS (I think it's called 7.1...version from Windows98SE).
The problem is a divide error. Without himem.exe loaded, I get
Divide error
Happens on all the machines all
At 03:29 PM 7/23/2005 +0100, Gerry Hickman wrote:
Biggest mitigating factors are that if your hard drive behaves without
errors, is reasonably standard with expected parameters, and there is no
corruption of the program, the MBR write on startup won't occur.
Ah, so this bug only happens with
At 11:33 PM 7/23/2005 +, you wrote:
This may be a side effect of memory corruption with EMM386. In
fact, it appears to be a result of some interaction with EMM386.
I do not believe the hard disk in question is faulty and I do not
believe that it has non-standard parameters.
Doubtful.
At 08:36 PM 7/22/2005 +0100, Gerry Hickman wrote:
[EMAIL PROTECTED] wrote:
By the way, I consider this bug extremely serious.
I agree, and Michael's post would appear to confirm that FDISK is far from
read-only, but has this bug always been there, or is it only in recent
development
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
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
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
601 - 700 of 792 matches
Mail list logo
