Hi Michael:
No change with this version...system hangs on vol c: with VDS
option, works without.
Mark Bailey
> 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.c
Michael Devore schreef:
At 08:07 PM 8/1/2005 +0200, Bernd Blaauw wrote:
either this is to scare non-technical people away (invalid URL) or
you're spending too much time in DOS :)
ftp.devoresoftware.com/downloads/emm386
Both styles work in IE and Firefox. Logs show browsers are how 90% of
At 08:07 PM 8/1/2005 +0200, Bernd Blaauw wrote:
either this is to scare non-technical people away (invalid URL) or you're
spending too much time in DOS :)
ftp.devoresoftware.com/downloads/emm386
Both styles work in IE and Firefox. Logs show browsers are how 90% of
people get the files. Wh
Michael Devore schreef:
Specifically, with
device=a:\himem.exe
device=a:\emm386.exe x=test memcheck vds
Alright, one more time. I rewrote the VDS routines such that any
reserved function which was unused (0, 1, 0dh-0ffh) no longer returns an
error code, but simply sets carry flag and chains
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 no
[EMAIL PROTECTED] schreef:
Hi Michael:
I dual or triple boot all of my machines and routinely switch
from DOS to WindowsXP and back. So, this makes sense.
Mark, I booted with HIMEM and EMM386 (+VDS parameter) now (Michael's COW
test version), but without DOS=HIGH, without DOS=UMB, and withou
Hi Michael:
I dual or triple boot all of my machines and routinely switch
from DOS to WindowsXP and back. So, this makes sense.
Frankly, XP makes for a more convenient Web and e-mail
interface (IMHO! :-)). So, during much, even most, of
my testing, I boot XP a lot...sometimes just to copy
som
Michael Devore schreef:
At 04:05 AM 7/30/2005 +, Mark wrote:
If you want to try this test version of EMM386, Go to
ftp.devoresoftware.com\downloads\emm386 and download emmcow.zip. It
should fix your page frame feedback problem. Very much doubt it affects
your VDS situation, but you can g
Hi!
30-Июл-2005 04:39 [EMAIL PROTECTED] (Michael Devore) wrote to
freedos-user@lists.sourceforge.net:
MD> After bootup, type debug to run DEBUG.EXE. At debug prompt, type d 0:12c
MD> and press enter.
MD> There will be a display of 2-digit hex numbers, the first line lists four
MD> of them.
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 suppo
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. The
Michael Devore schreef:
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.
After bootup, type debug to run DEBUG.EXE. At debug prompt, type d
0:12c and press enter.
debugging on t
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.
Hi Michael:
Well, the E000 message is repeatable on this box...
Thanks again for all of your help!
Mark
> At 03:38 AM 7/30/2005 +, Mark Bailey wrote:
>
> >Specifically, with
> >device=a:\himem.exe
> >device=a:\emm386.exe x=test memcheck vds
> >
> >vol c: hangs. Remove vds, it works norma
At 03:38 AM 7/30/2005 +, Mark Bailey wrote:
Specifically, with
device=a:\himem.exe
device=a:\emm386.exe x=test memcheck vds
vol c: hangs. Remove vds, it works normally. (development)
With stable kernel, I get screenfulls of garbage I can't read
(no newlines) with VDS, normal operation wit
Hi Michael:
OK, I have done so. The new version still reports version 2.04,
July 6, 2005, but is much larger!
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.e
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 intro
Hi Bernd:
OK, back to development kernel, development command.com, UDMA2
V2.5.
With config.sys:
device=a:\himem.exe
device=a:\udma2.sys
device=a:\emm386.exe x=test memcheck vds
VOL C: works normally. Without device=a:\udma2.sys,
vol c: hangs and forces a reboot. (That's the old behavior
which
Michael Devore schreef:
Different issue entirely. Don't know what's going on in VMware, it may
just not like VDS.
very probably, yes, Michael.
Mark, can you try loading UDMA2.SYS anyway (in front of EMM386)?
DEVICE=HIMEM.EXE
DEVICE=UDMA2.SYS
DEVICE=EMM386.EXE VDS other_options
if that works,
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)
booting
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)
booting from BIOS directly to harddisk.
Maybe a floppy wou
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 m
Hi Michael:
Does this provide a means of easily identifying the affected
machines? How do I check the Haunted HP Pavilion? :-)
Mark
Michael Devore wrote:
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 inter
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 diffe
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
th
Hi Michael:
Well, what's trying to use it is the FreeCOM VOL command!
(Or something else in FreeCOM). I doubt that there are
any explicit calls to VDS functions there. The kernel may
be more likely.
This appears to be the same bug that caused FDISK to
wipe out the MBR, so it at least appears th
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 f
Hi Bernd et al:
I wish to thank all of you again for the wonderful support and help!
I have been amazed at the responsiveness of the FreeDOS
community!
Back with the haunted HP Pavilion (TM). Development kernel,
sys, and command.com from fdos.org/kernel. EMM386.EXE
and HIMEM.SYS from emm204x.zi
Hi Michael, et al:
OK, I am back with the Haunted HP Pavilion (TM).
Downloaded development kernel, command.com, and sys.com
from fdos.org/kernel. Downloaded emm204x and extracted
himem.exe and emm386.exe.
Did a SYS: on a USB floppy from WindowsXP. Copied a random
version of edit.com on the flo
[EMAIL PROTECTED] schreef:
Hello all:
As I mentioned before, remove the VDS parameter and see if things go
better then.
VMware suffers from incompatibility with the VDS parameter, maybe your
system also. Maybe even a lot of systems, but that's a wild guess.
IF things fail even without the V
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
Hello all:
OK, now that I've at least identified the FDISK problem, and solved
the DIR divide by zero problem, I need to work on why FreeDOS
doesn't boot and/or run stably on many computers.
Fortunately, I have the Haunted HP Pavilion. I have a repeateable
problem with the VOL command built into
32 matches
Mail list logo
