Michael Devore schreef:
If you are using RAM without any parameters, EMM386 should not behave
any differently than if it didn't exist. Standard UMB area scan
occurs whether RAM is there or not. Only the optional range with RAM
makes a difference, changing the default scan area size. And if
Eric Auer schreef:
PS Bernd: Tell people to abort on the WHICHFAT critical error message. Then
unformatted is reported as 0, and FAT12/16/32 are all reported properly.
However, the kernel has to be fixed - there should be no interactive critical
error message when detecting an unformatted drive at
tom ehlert schreef:
however I still would prefer arkady to recompile emm386
and tell us if that works, instead of using mental input bandwidth of
all people subscribed to this list.
didn't you use some commercial compiler? Eric didn't have it, and
probably Arkady neither.
compiling is
Eric Auer schreef:
This also needs a test whether area is writeable...
I have been able to include 4KB blocks of all-zeroes or all-FF's in VMware.
X=TEST only picks the all-FF's (Free, available).
Autoscan also picks the 'all-zeroes'
-PROM (AA55 signature)
This allows skipping the whole
Who is mantainer? Kenneth Davis impants changes from floppy.asm and
promise to review dsk.c. After this - no news from he. Even very small
patches (as last one for int2f.asm and entry.asm) is waiting.
then don't submit your patches, but write own version as you do now.
after you're done,
Eric Auer schreef:
Hi Bernd! Nice that the new distro is delayed, maybe
some things can get fixed in the next 2 weeks..
Hi Eric, you're not away that long, I see. slightly information addicted
like I am
(I'm not even that much internet addicted, but it just contains a lot of
info).
Arkady V.Belousov wrote:
Hi!
Arkady, I'll try to compile your kernel tonight, as I experienced some
hardware upgrade glitches the last 2 days.
as someone asked (I lost about 35 emails) : Lucho's site is at:
http://linux.tu-varna.acad.bg/~lig/
it contains the Romdsk stuff and the UDMA DOS-driver.
Arkady V.Belousov schreef:
- when I load EMM386 over MS-HIMEM 3.95 (from Win98), then FreeCOM 0.82 pl
3 XMS_Swap [Dec 10 2003... after program run says:
FreeCOM: XMSSwap_In: XMS copy error
Cannot terminate permanent FreeCOM instance
System halted ... reboot ot power of now
which program do you
Aitor Santamaría Merino wrote:
I have done a couple of testings with /X:ON and DIR
FD-APPEND + NT/CMD.EXE is NOT affected
MS-APPEND/NT + FreeCOM is AFFECTED
and the COMMAND.COM on WinNT (at least Win2000 and XP have both a cmd.exe and
a command.com)?
I'll retest FreeCOM behaviour, but
Erwin Veermans wrote:
Yep, the copy . c:-failure (heap corruption) which seemed to have
been present in freecom for a long time has been fixed already by Tom
by his 1.129-fix (03-05-2004). In fact it was discussed already in
Bugzilla #556. Both the q and r revisions of 0.82pl3 carry the fix.
Erwin
http://linux.tu-varna.acad.bg/~lig/freedos/DOSFSCK.EXE
Eric, I don't know if Lucho had a patch file to DOSFSCK 2.10
see below for the patch as Lucho sent it.
no idea if ROMDSK or ROMDOS already work with BOchs for example.
Would make testing a lot easier and safer.
now what was this doing on
Hello. My company processes (removes microsoft information) and resells
1,000 - 1,500 major-label PCs a month. The OEM would like us to add
FreeDOS licenses to these PCs.
just the license?
is this the MS all computers must be delivered with an OS requirement?
what's the current wiping process?
Erwin Veermans schreef:
A well known alternative for '*.*' is to use '.' with 'copy', like: 'copy . c:'
This works fine with MsDOS and DrDOS (OpenDOS) but fails
on FreeDOS with every kernel (2026b - 2035) and freecom
(0.82pl1 - 0.82pl3k) I tried (clean boot, no himem/emm386).
This dot-shortcut is
Eric Auer schreef:
Hi, who is maintaining TDSK right now? I found that the LSM database
still listed a very old contact address (Jim removed that now). But I
think others have continued to work on TDSK after Ciri, does anybody
know if and who is maintaining TDSK today?
Eric
TurboDisk was handed
[EMAIL PROTECTED] schreef:
Hi,
I am hereby, finaly releasing a new version of defrag. This version should
fix all known bugs, so it should be ready for FreeDOS version 1.0. The speed
is still not optimal, I optimized some stuff here and there and I added
a message on start up to install an XMS
Eric Auer schreef:
Hi, I would vote against meetup.com ... just use good old IRC chat :-).
If I have enough spare time I can try to release the final Beta9
version, which should add diskette installation support and a slightly
tuned installation (Fdisk more in the beginning, no need to load
on it. Is it secure?
yes, it's not easy for others to gain access to your system from the internet or
network.
But as always, any user that can access the physical machine can also try to hack it.
I hate to be a Dum Dum but I just have to ask.
questions welcome.
thanks
Marshall
Bernd Blaauw
Eric Auer wrote:
Hi!
I recommend to move this discussion to freedos-devel, with a
nice subject line.
So here some information about UPX:
how easy is it to prepare DISPLAY for COM2EXE as Arkady suggests?
still, why would LH not abort on MSDOS but abort on freedos kernel?
FreeCOM is being used as
Eric Auer schreef:
Or compose some somehow bigger news item text. I can post a news item myself
BUT I would like to wait with that until I get a) some yes, it works feedback
and b) mail from people who have put collections of compressed CPI files on
some homepage. Please do not send me files by
Joe Cosentino schreef:
Hi all,
Here's the next release of Edit, version 0.81. I've gotten a lot of bugs/enhancements/etc...so here's the list and my reaction to some of them:
Anyway, you can download Edit 0.81 from my website at http://www.geocities.com/xsaintx69/freedos/
Thanks,
Joe
hello
Johnson Lam schreef:
On Tue, 27 Apr 2004 21:28:19 -0500, you wrote:
Hi,
That's why I'd like to see the feedback conduit of Bugzilla -- and Tracker if it is judged worthy of support -- made more attractive to the casual FreeDOS users.
I feel the idea of Bugzilla is good but it's terrible
Eric Auer schreef:
Hi, I found that a very small way to decompress CPI files would
be using UPX to compress them and then patch the decompression process.
Here is a sketch. I think this should work with both open source and NRV
versions of UPX.
Same thing as making an EXE non-decompressable by
Hi,
Anyone willing to translate strings can have a look at
http://fdos.org/ripcord/beta9rc5/addon/strings.zip
for Italian I recommend to start all over, since the italian.lng file is very small, and thus
incomplete.
copy default.lng italian.lng
edit italian.lng (now translate things)
fixstrs
Johnson Lam schreef:
I got the same problem when trying MSCLIENT, it does work under
FDXXMS+UMBPCI (try it), but fail with HIMEM+EMM386. I'm quite sure the
memory manager and hardware not so compatible especially Network
Interface Card.
try HIMEM + UMBPCI (there's even a 3.57beta7 version at the
help-files are already collected in a zipfile, Rob worked on that.
I suggested compressing the CPI-files to Eric using Gzip,
but that would add Zlib to MODE.
Eric likes another less efficient but smaller to implement compression
algorythm/program.
he said it reduces CPI from 58 (60) to 19KB
david lowe schreef:
I want to know if whether I can install from a floppy or if I have to
burn the files on a CD go from there.
usually from cd.
Another option is to ask me to put all FreeDOS files in a single ZIP file.
then download it, and unpack. Now there's your FreeDOS.
only thing missing
Michael,
how does that MAX work in HIMEM64?
it keeps complaining about /MAX:4000 ignored
I'm trying to reduce memory enough to not let the XMS-version of FreeCOM load in extended memory.
DEVICE=A:\DRIVER\HIMEM64.EXE /MAX:4000
;DEVICE=A:\DRIVER\EMM386.EXE X=A000-
SHELL=A:\COMMAND.COM A:\
There's definitely a weirdness going on with EMS, but not all EMS, since other applications are using it okay. May have to quick patch EMM386 if I can find it.
note that tdsk up to and including 2.3x series has sourcecode.
for problems with tdsk 2.4x series you have to contact Matthias Paul.
he's
I already have a wishlist which can easily turn into a errata-list,
including reproduction tools/batchfiles.
my bugs are mainly trivial enhancements (don't mean trivial code changes, btw),
so it can wait.
I too like Bugzilla to be as empty as possible, but that means me posting patches
and I'm not
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
Eric Auer schreef:
Hi, while MS Win98 MEM could be called a standard, I do not agree with:
b7ff81920 DOS system code
9fff65536 DOS system code
wait until 1.6 is released.
---
This SF.Net email is sponsored
read
http://www.freedos.org/freedos/news/news.cgi?q=fa=html/1695.html
Bernd Blaauw
Bernd
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo
Upper value should be 4194303, which is (4G / 1024) - 1. Not tested nearly that high.
what happens for a too high value: ignored, or set to that (4G/1024 -1) value?
(basically same effect I guess..)
so /METHOD: ties the disk you use HIMEM on in worst case to a single computer system.
I wish I
Bart Oldeman schreef:
- check_name() uppercases MCB.name. As result, instead win386 we get
WIN386.
well WIN386 doesn't run on FreeDOS so that's kind of a non issue.
CLONE or replacement of a MSDOS program?
if replacement, it should act as MS MEM, no matter which platform.
preferrably
hmm. please run FD mem /f. Otherwise it's difficult to see. This doesn't
occur for me. As it's exactly 80K there may be a hole in your UMBs
somewhere -- stupidly I missed that case. Won't be difficult to fix.
Bart
DEVICE=EMM386.EXE I=B000-B7FF I=DC00-EBFF /VERBOSE
MEM /F (MS-MEM, in Dutch, from
Florian Xaver schreef:
Hi!
Just tested the combination. Himem64.exe works perfect (seems so). But
when i am using emm386.exe, DUSE (USB driver for extern HDs, CDs etc.)
only writes: DOS is in protected mode and exits.
In the User Guide of DUSE there isn't wrote any incompatiblity with
Arkady V.Belousov schreef:
Hi!
Question: by default, only CON device have bits stdin and stdout
(mask 0x3 in attribute word). What happen if I use CTTY NUL - is this
equal to plain redirecting to NUL or shell sets stdin+stdout bits in
attribute word (INT 21/4401, as I understand)?
input is
Johnson Lam schreef:
perhaps SYS CONFIG file can show the kernel version if file is a FreeDOS kernel.
I remember no version information when SYS. I didn't try SYS CONFIG.
Is it necessary to show version during SYS? My opinion is a bit more
information harmless.
might be a possible option.
SYS
Alain schreef:
Ok, but:
1) never dreamed of typing VER /R or VER /? _this extended version
should be the dafault_
that may be not so compatible to batchfiles etc.
VER /R is an ancient trick.
2) Kernel version only by numbers is not enough, there are too many
variants that show only in the
Aitor,
I really could use the keyboard layouts and the KEYB executable by now,
for testing purposes. looks like KEYB cannot look into subdirectories,
and thus the need for the PUSHD/POPD you see below:
I'm not sure what KEYB does exactly for locating the layout file:
1)look in current directory?
Johnson Lam schreef:
If DOSFSCK can do the job similar or better than SCANDISK, then we
don't need to insist on the name. For me, I think using the name
DOSFSCK is better because it's NOT a direct replacement of SCANDISK.
problem is DOSFSCK cannot do this yet. it is broken for at least FAT32.
that's nice.
So VDS is required when EMS is served,
not when VCPI and/or UMBs are provided.
NOEMS and EMS settings use different blockdevice-names:
one more optimizing thing for me then:
@echo off
rem load UDMA from commandline using DEVLOAD program. /H = DEVICEHIGH behaviour.
rem try NOEMS first,
Hi Michael,
Not yet, looks like it should be. I'll see about it, read what MS docs say about the option. Should be a reasonably quick add, since it's awfully close to NOEMS in a lot of behaviors.
suggested using FRAME=NONE to Erwin, since he needs to limit VCPI to 2MB, but NOEMS makes 32MB on
301 - 343 of 343 matches
Mail list logo
