Re: [Freedos-kernel] False triggering of "VDISK detected" by fdxms.sys

2004-04-19 Thread Bernd Blaauw
Steve Gibson schreef:
Hi Folks,

Using the 2034 kernel and fdxms.sys, I have two systems where FDXMS.SYS 
refuses to load because it mistakenly detects that VDISK is present.

Steve,

please retry using experimental HIMEM64.EXE
ftp://ftp.devoresoftware.com/downloads/himem64.zip
or the distributed HIMEM.EXE,
http://www.drivesnapshot.de/freedos/emm386rc.zip
issue might be described at http://www.ludd.ltu.se/~ams/freedos/fdxms/

finally, you might try kernel 2033 for regression testing,
as a lot of changes have been made.
perhaps Bart, Michael or Tom has more knowledge of this.

Don't think Martin (FDXMS author) reads these lists anymore,
so also mail him, as it might mean FDXMS286 (286+) has to be changed.
(the 386+ FD{X}XMS is outdated compared with current HIMEM.EXE)
Bernd

---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel


[Freedos-kernel] False triggering of "VDISK detected" by fdxms.sys

2004-04-19 Thread Steve Gibson
Hi Folks,

Using the 2034 kernel and fdxms.sys, I have two systems where FDXMS.SYS 
refuses to load because it mistakenly detects that VDISK is present.



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel


[Freedos-kernel] FreeDOS Beta9 RC5 has been released

2004-04-19 Thread Bernd Blaauw
Hello list,

This 5th release candidate was intended to be a minor update to the FreeDOS Beta9 series, but has 
turned out to be a major release, much to my surprise. so far, both the special bootdisk and the 
packages have been updated, and the installation process has been has slightly tuned and made more 
reliable.

Features and important updated components of this release candidate:

* Completely rewritten readme files (so DO READ them!)
* Improved installation menu navigation
* Configurable NLS settings (codepages, keyboard layouts)
* Text-installer runs in case GUI installer or CWSDPMI fails (or select MONOCHROM 
screen)
* Memtest86+ v1.11 has been added to bootdisk (option 1, then option 2)
* Smart Boot Manager v3.7.1r1 has been added to bootdisk (option 1, then option 3) 
so you can
  boot from cd/dvd on any 386 or newer system.
* FreeDOS Kernel 2034, reduced memory usage (Bart Oldeman)
* EMM386 1.11, now including VCPI support (Tom Ehlert / Michael Devore)
* Mem 1.6 including /C option (Bart Oldeman)
* Keyb 2.0 Prerelease 1 (Aitor Santamaria Merino)
* DOSFSCHK working version for FAT32 (Imre Leber, patch by Lucho)
* UDMA 7.0 (final version by Lucho, no longer maintained)
* EDIT 0.8, fixing the 'expanding TABS' bug (Joe Cosentino)
* HTMLhelp 1.03, including ZIP support for saving disk space for the many 
helpfiles.
* Bootfix 1.4, bootsector analysis and dumping tool (Arkady V Belousov)
* MODE, new features & works better with DISPLAY  (Eric Auer)
* DEBUG, featuring FAT32 support (Paul Vojta) -->
This is a release candidate because it provides only the Base diskset and the corresponding sources 
for it.
After people working nearly 10 years on the FreeDOS project, the released software is almost ready 
for a 1.0 release. Therefore we ask you to help us add items to the FreeDOS 1.0 ToDo list and to 
resolve the remaining issues. The next Beta9 distribution will no longer be a release candidate, and 
will feature a diskette release.

Beta 9RC5 can be obtained in cdrom-format as a downloadable ISO image from Ibiblio in a few hours 
from now. No diskette release, but Steve Nickolas probably will release an updated ODIN
(One Disk INstall) release in both 720KB and 1440KB diskette image formats.

With kind regards,

Bernd Blaauw

---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel


Re: [Freedos-kernel] Re: [Freedos-devel] Recent Bugzilla entries

2004-04-19 Thread Aitor Santamaría Merino
Bernd Blaauw escribiÃ:

Arkady,
is the auto-loadhigh part of Cutemouse difficult to integrate into 
other programs?
I'm thinking about FreeCOM and KEYB. not DISPLAY, as that will become 
a driver file anyway.
Unless I am wrong, no big deal here, would be a question of creating a 
UMB MCB, and copy the resident code/data there.
The fact that it works depends greatly in the segment registers being 
used correctly. I have cleaned this up in this first rewrite version, 
but there's still something that I'd need before doing this.
First, the resident code is fully in assembler, EXCEPT for the return 
instructions. The resident procedures are of the form:
===
procedure XXX; assembler;
asm
...
end;
===
whenever I call them from other places, or store their addresses (in 
Pascal pointers are always far), I have to declare them far.
However, I have manually tried to place RET instructions and making 
calls using only offsets just to see how it feels, and I have noticed 
that it crashes.
So in order to get more control, I'd like to rewrite the whole of the 
resident part as a chunk in NASM and try to link. But this will not come 
soon in time.
BTW, as I don't want to waste any single byte and mess with linker/code 
placement  (I still ignore if {$L directive will link object code IN THE 
SAME PLACE where it appears), perhaps turning that all into assembler 
and creating other MCBs to place the resident stuff, will happen at the 
same time. No sooner than KEYB2 pre2.

Aitor

---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel


[Freedos-kernel] Re: [Freedos-devel] Recent Bugzilla entries

2004-04-19 Thread Bernd Blaauw
I'm kicking this back to kernel. No need to let it stay on devel-list

Arkady V.Belousov schreef:
Hi!

19-Апр-2004 15:13 [EMAIL PROTECTED] (Eric Auer) wrote to
[EMAIL PROTECTED]:
EA> In bug 1759, he also suggests that "No UMBs available" warning (when you
EA> use DEVICEHIGH) should be only displayed once - fixed in 2034?
 On the other side, this once warning may be missed - for example,
because next driver quickly scrolls screen or clears it.
a one time warning plus a 2second delay would be my choice.

in current case I get LOTS of warnings about no UMBs available. MSDOS is silent.
(and LH also does not warn, so why would DEVICEHIGH?)
DEVICEHIGH=HIMEM.EXE
DEVICEHIGH=EMM386.EXE
DEVICEHIGH=ATAPICDD.SYS /D:FDCD0001
DEVICEHIGH=NANSI.SYS
MEM /C now also works to show this.

 On the other side, I agreed - missing UMB may be easily detected later,
by amount of available memory, whereas config.sys may be common for
different configurations. So, this warning, at may taste, is completely
useless.
yes, Erwin Veermans on his NWDSK has to use different DEVICE and DEVICEHIGH lines
for the same driver, just because of this warning.
Arkady,
is the auto-loadhigh part of Cutemouse difficult to integrate into other programs?
I'm thinking about FreeCOM and KEYB. not DISPLAY, as that will become a driver file 
anyway.
FreeCOM can be loaded high using SHELLHIGH, but this SHELLHIGH is strangely enough 
unknown on
MSDOS 7.10. then use /LOW to keep FreeCOM loaded low.
SHSUCDX 2.1a also has an auto-loadhigh function.
anyone tried DOS=LOW,UMB and see if anything gets loaded high?
in my experience it does not enable UMBs.
Bernd

---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel