On Thu, 28 Jul 2005 19:56:40 +0100, you wrote:
Hi Gerry,
>But you didn't tell it to write an MBR?
FDISK should automatic update the MBR when quit (or I'm wrong?)
>OK, but if there was no MBR, this may not create one. That's what my
>earlier post was all about. Can you try this (all data will b
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 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
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
Hi,
Jack R. Ellis have message:
-
I have read all the comments on FD-User re: Mark Bailey's problem
using the FD-EMM386 "VDS" parameter. I also noted Mike DeVore's
reply, that using "VDS" only enables 32-bit physical addresses to
b
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 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
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 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:
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,
Hi Johnson,
Something doesn't add up here. As I understand it, we are ONLY trying to
fix the problem of it not booting at this stage - is that right? The 8Gb
thing is a different problem.
Are you sure you followed the exact steps, in the exact order I listed?
If you did, and it didn't boot,
Eric Auer wrote:
2. FDISK /CLEARALL 1
3. FDISK /MBR
4. FDISK /PRI:2000
That would be dangerous, I think. The bug report was just "it does
not boot after fdisk and sys", not "I want to kill all my data".
The solution FDISK /MBR will already be enough.
He's testing on a new server, that's soo
Hi Eric,
"previous o/s". To fix it requires changing attribs on BOOT.INI, editing
it, then re-apply attribs...
You could write a small batch script to automate that...
I explained in an earlier post why that is not practical nor desirable.
FreeDOS Beta9sr1:
...
4.
5. FORMAT C:
Did you
In a surprise move the other day, Slashdot posted a new snippet about
OpenGEM. I'm not sure how much traffic this generated for FreeDOS
(which was linked from the news article), but it's certainly swamped my
site.
If you want to read the news article you can do so here:
http://developers.slashdot
In a surprise move the other day, Slashdot posted a new snippet about
OpenGEM. I'm not sure how much traffic this generated for FreeDOS
(which was linked from the news article), but it's certainly swamped my
site.
If you want to read the news article you can do so here:
http://developers.slashdot
This one is the best yet. It is possible to read web
email on yahoo, but not send it. Likewise with
another web email service I tried.
Charlie
--- Florian Xaver <[EMAIL PROTECTED]> wrote:
> Hi!
>
> There is a new version of Arachne!
>
> http://www.cisnet.com/glennmcc/arachne/
>
> Bye, Flo
Hi,
Eric Auer escribió:
Could be used with software with restrictive licenses.
Okay, I get it. Read: Antivirus stuff and VIDE-CDD. What else?
By the way, Bernd just never got a reply from Acer about the
driver, but they never said that you cannot put it on CD either.
What is the license of
> What is the license of ACRODOS, for those that have used it?
Acrobat Reader? This is almost useless and Ghostscript for DOS can
view more files than Acrobat Reader for DOS. Plus, Ghostscript is
open-source.
---
SF.Net email is sponsored by:
On Fri, 29 Jul 2005 23:00:50 +0100, you wrote:
Hi Gerry,
>Something doesn't add up here. As I understand it, we are ONLY trying to
>fix the problem of it not booting at this stage - is that right? The 8Gb
>thing is a different problem.
Yes.
>Are you sure you followed the exact steps, in the e
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
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 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: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:
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
24 matches
Mail list logo
