> the FreeDOS kernel is seriously slower then MSDOS when doing
> larger copy/xcopy operations.
> the cause: the disk I/O code avoids transfers that cross a 64K
> boundary, and splits these transfers into 3 (smaller) transfers.
> this was needed for floppy controllers in the 1980's, but is
if exist K:\NUL echo K: is present
is broken in kernel 2042
the bug is caused by a change in TrueName(), where code was changed
from
cdsEntry = get_cds(result);
if (cdsEntry == NULL)
return DE_PATHNOTFND;
to
dhp = IsDevice(src);
cdsEntry = get_cds(result);
if (cdsEntry
Hi,
> Was using FreeDOS 1.1 2040 kernel? previously and could check for
> drive or directory existence with the NUL device:
> If exist c:\nul echo C: exists
> If exist c:\mydir\nul echo C:\mydir exists
> This behavior is broken with 2042, no longer being able to identify if a
> drive/dir
>>From the point of view of protecting this system from counterfeiting &
> unauthorised access, is it possible to interrupt processing config.sys? I
> had read about pressing F5 to bypass config.sys and autoexec.bat. Also that
> this can be disabled in config.sys.
modify kernel.sys by using
sys
the problem, brought up by Bret:
during config.sys processing,
INSTALL= \freedos\MEM.EXE /F
will report ~24 K used at 99f0:0
however the kernel will crash if memory below this is overwritten.
source for the bug:
CONFIG.C, DoInstall() sets up a memory arena, and releases memory
below the
> On Feb 5, 2016 11:04 AM, "Tom Ehlert" <t...@drivesnapshot.de> wrote:
> Bret,
>
>> Eric/Tom:
>
>> I used to use INTERxxx a lot many years ago using the special
>> parallel cables designed for that purpose (I think I still have a
>> cou
> I wanted to ask: to what degree does FreeDOS implement the redirector
> interface? Are there any known incompatibilities?
it should right work.
all known redirectors
CD/DVD drivers
MS Lan Manager
NTFSDOS
NTFS4DOS
VMSMOUNT (with source)
for DOS work without (known) problems
>
Sorry for the link I haven't used thus machine to send emails in a long
time. The antivirus tags it with it. I had suspected that I wouldn't
be able to kernel merge, but it's nice to have thoughts. The multiuser
will have to wait whilst I wait on the response from Caldera, They have
an
I am interested in writing a new driver, one that would allow you to
boot and run dos on a EXT3 partition.
booting from EXT3 would require to make EXT3 part of the kernel.
not going to happen.
otoh there is virtually no disadvantage to have a loadable TSR to make
EXT3 available as a
I am an E.E./Comp. Sci. student, but I want to contribute to the FreeDOS
Kernel. Would it be fine if I began setting up a multiuser/multitasking
system like Digital Research's DOS 5, and begin the work to get Forth
into the kernel?
the kernel is definitively not the right place
to
I'm not sure how you can say the FreeDOS project isn't interested in a BC5
kernel.
because I was around when the kernel was ported to MSVC, BC5, OW (in
that order)
The BC5 makefiles I found in the kernel sources I didn't write.
Bart last worked on them 9 years ago.
right. an since OW became
Kernels with FAT32:
086: 68358 bytes
186: 67180 bytes (286 same)
386: 66044 bytes
486: 65948 bytes (586 and 686 same)
It is interesting that even 186 instructions do make a
quite big difference and that there is a difference at
all between 386 and 486. With 186, you get pusha and
What's the difference between wcc wcc386?
code generation for 16 bit (DOS) or 32 bit (windows)
Does wcc386 generate code that could be used in the kernel?
no
Big wins could be had on 586 with FPU memcpy 64-bit versus the 16-bit asm
in the kernel now and possibly the string functions.
I use the Kernel 2041 and found follow strange:
If I press the F8 key for singlestepping and then the ESC key to skip a
command, the
singlestepping-process of the FDCONFIG.SYS is skipped.
I implemented it this way because AFAICT MSDOS 6.2 behaves this way
Under MS-DOS the ESC key skips
Dear PerditionC,
UBYTE DiskTransferBuffer[MAX_SEC_SIZE];
wastes 3,5 KB low memory for *everybody*, not only when it's needed.
regarding how much time we have spend until we had 64 byte free
I think this is a bad idea
please see my previous messages, I know exactly how much space
Dear PerditionC,
UBYTE DiskTransferBuffer[MAX_SEC_SIZE];
wastes 3,5 KB low memory for *everybody*, not only when it's needed.
regarding how much time we have spend until we had 64 byte free
I think this is a bad idea
I also think that these experiments should NOT be in the stable
-d2d-c2
___
Freedos-kernel mailing list
Freedos-kernel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Mit freundlichen Grüßen/Kind regards
Tom Ehlert
+49-241-79886
to write code, not emails ;)
Mit freundlichen Grüßen/Kind regards
Tom Ehlert
+49-241-79886
--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application
More tests: http://jafile.com/uploads/dos386/perftest.txt
unless dos386 describes what program(s) he used on what hardware
to produce these results, the data are useless :(
...you can try first writing some dummy data at where the file
will end, then close it and re-open (without truncate of
Hallo Herr Ibidem,
am 1. April 2011 um 07:56 schrieben Sie:
I tried building svn revision 1560 with Turbo C 2 and a 16-bit nasm
0.9x (FAT32/186). It started building, but then when build.bat hit
SYS, I got this:
Error sys.c 629: Expression syntax in function initOptions
I REM'd out SYS
of course you are right. but maybe you are missing the point why the
original author (m2) wrote it exactly as it is: to save precious 2 bytes in
the boot sector code
Tom
am 6. Dezember 2009 um 00:32 schrieben Sie:
Hi,
the LBA detection of the FAT12/FAT16 boot sectors (both for the FreeDOS
b) why there isn't a 386-fat32 binary available (hardly anyone even
knows where he might see a real 8086 machine), and the 386 resident code is
~1,5 KB smaller
Point out the file(s) that were missed and I'll do an update.
IMO the most useful kernel configuratiion is FAT32, compiled for 386
The kernel developers have just finished up 2039 for release a
few days ago (mostly bugfixes), so you can download it at ibiblio (
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/kernel/2039/
or at sourceforge (
http://sourceforge.net/projects/freedos )
just wondering, why
a) this
The FAR printf is probably good for 16-bit builds with DEBUG defined.
However, there are at least two potential issues (NOT YET VERIFIED).
1. 386 (or higher) builds might fail on a FAR value, as a 32-bit FAR is past
4GB. I don't know how the compilers treat FAR in these builds.
exactly as the
* Windows 3.1x support
seriously: is ANYBODY using Windows 3.x ?
IMHO Windows 3.x is 100% obsolete, so why would anybody want windows
3.x support ?
WfW support in stable, these might be handy.
Windows for Workgroups , which is a flavor of Microsoft Windows 3.11
WfW support will probably
It won't help FreeDOS of course because it still uses fnodes for these
things instead of SFTs.
Those are ancient relics that should be done away with. There is no
need for them anymore. I'd like to put that high on the priority list
for kernel development.
in theory you are right. in
- int 21.1c should report invalid drives via AL (keep other regs?)
News here: DR-DOS modifies BX/CX/DX but not DS for inv drives.
/* Get Drive Data */
case 0x1c:
{
BYTE FAR *p;
if (p = FatGetDrvData(lr.DL, lr.AL,
Hi Eric,
how about compiling this for Christian ?
not everybody likes to download watcom, find out how to get kernel
sources compiled ...
and after he verified this private version, may be even put it on
ibiblio to be used by others ?
Tom
Hopefully someone can found the bug and fix it, my pathetic knowledge
forbid me to help.
to fix any bug, it must be reproduced first.
As noone has ghost 5, 'the bug' can't be reproduced, and so can't be fixed.
end of story.
Tom
1658 Ghost 5.1 fails: Needs somebody with Ghost 5.1 to fix
Maybe true, but I do not have ANY version of Ghost to test :-(
If a newer version of Ghost works, then we could indeed set
the bug status to wontfix and mention that newer versions
do work fine. Or we could lower bug priority to
came much later ;)
Mit freundlichen Grüßen/Kind regards
Tom Ehlert
+49-241-79886
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go
NOTE that both versions have a typo: ... the any key ...
It's not a typo! Damnit! Still haven't found the any key?
see http://www.computergear.com/pressanykey4.html
and http://www.gadgetizer.com/2006/04/03/any-key-mistery-solved/
or just google for the any key ;)
Tom
/freedos-kernel
Mit freundlichen Grüßen / Kind regards,
Tom Ehlert
+49-241-79886
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits
- int 2f.4a00.cx=0 the kernel has to call this before it displays
the Insert diskette for drive B: (or A:...) message, to let
Win3 and the like show a GUI dialog instead of the message, DOS 5.0
seems to have been lost; should be
STATIC WORD play_dj(ddt * pddt)
{
/* play the DJ ... */
possible bugs introduced
by some experimental feature ;)
Mit freundlichen Grüßen / Kind regards,
Tom Ehlert
+49-241-79886
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX
Hello Kenneth,
The main issue with FreeCom would be the location of its resources
changing.
under normal circumstances, FreeCom-xmsswap will have it's resources
loaded at startup and touch them never again.
Tom
---
This SF.Net email is
Hello Eric,
While we are at it, I would suggest a new category not planned at all
unless you tell us why it is useful or alternatively send us patches
for the list: http://fdos.org/ripcord/fdos_1_0/official/post.htm
Candidates are: drivparm / driver sys / 3rd floppy support (kernel, sys...),
Hello Eric,
Comments about useful sector sizes would be welcome:
Smaller (64, 128, 256), normal 512, Bigger (1024, 2048, others).
512.
Thanks for your comments! Trying to wake up the kernel list a bit :-)).
add code to support dynamic disks.
Tom
Hello Geraldo,
is possible to implement a virtualfilesystem layer on
freedos kernel?
it has already: the network redirector interface.
what do you think about create a hardware abstraction layer
on freedos kernel?
it is interesting to make freedos portable to others
architectures
it has
Hello Alain,
Tuesday, January 11, 2005, 1:24:48 PM, you wrote:
Arkady V.Belousov escreveu:
Hi!
4--2005 19:05 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
Fix divide error message text
+++ entry.asm 4 Jan 2005 19:05:08 - 1.27.2.2
-; print a message
/listinfo/freedos-kernel
--
Kind regards,
Tom Ehlert
mailto:[EMAIL PROTECTED]
+49-241-79886
---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE
Hello Arkady,
Small optimization: because BC doesn't knows, that exit() doesn't
BO I don't think optimizing exeflat.exe's size is very important though ;)
Sure. :) But why not make more optimal code from scratch in any case,
without thinking will this code often used?
And why not
Hi Bart,
good to see you alive and around :)
http://freedos.sourceforge.net/kernel/exeflat.c
(the file is smaller than the diff would be)
there are probably a couple of changes to makefiles batches ?
To use it you need to change the makefile to remove the explicit UPX call:
this call is
This is a forwarded message
From: Jose Antonio Senna
Subject: FreeDOS kernel disk routines
===8==Original message text===
Excuse me for sending this directly to you, but I am still unable to post
on Freedos lists.
I do not know who (if anyone) mantains the FreeDOS
Hello Eric,
Hi, Steve reports that while things were fine in kernels
2030 ... 2033 (both with and without FAT32 support), kernel
2034 WITH FAT32 support and all 2035 kernels fail to read
the (fd) config sys file when booting from floppy.
*ALL* kernels 2023..2035BTom boot from 1.44 floppy,
Hello Eric,
Hi, I exchanged some mails with Udo from DR DOS improvement project,
and the conclusion might be that FreeDOS is not missing much for 386Enh
compatibility - it only has one thing too much: fnodes.
From what follows, it real seems to be easy to make FreeDOS Win3.1
compatible.
So
Hi Jeffrey,
actually the kernel tries to finish CD harddisk emulation
before booting from HD (main.c, EmulatedDriveStatus)
unfortunately this doesn't seem to work (in your case, with your CD
burning software,...)
tom
---
This SF.net email
Hello Eric,
- Tom has added only the best few lines of the Lucho / Arkady patches,
those which OBVIOUSLY fix bugs, but will have missed several bugfixes
which were hidden between optimizations
that might have happened.
But for sure I missed some bew bugs hidden between optimizations.
-
Hello Luchezar,
Do you mean
http://www.mail-archive.com/[EMAIL PROTECTED]/msg01070.html
yes
(It doesn't contain other comments but those in the patch.) If you
confirm, I can apply it.
yes.
it happens if a int24 handler returns to itself directly, instead of the
'normal' way to return to
Hello Luchezar,
D:==second disk? Second disk is a 81h value.
Only 0 and 80 are used by MS-DOS. All other values are FreeDOS
extensions ;-)
are you SURE ?
I remember a BIOS that had the option to boot from 2'nd drive.
this only makes sense if DOS then boots from 0x81.
tom
Hello Luchezar,
and removes (parts? of) tom's patch.
As you wrote youself, it's better to have the whole patch than parts of
it. And even better is to solve entirely the problem which this kludge
solves partially. But we don't know the problem :-(
at least I know the problem - and
Hello Luchezar,
In FreeDOS 2035a, NSSI crashed.
In the newest unstable kernel, NSSI works excellent!
Get NSSI at http://www.navsoft.cz
Thanks for the information! Unfortunately if UDMA or CD-ROM driver is
loaded, it hangs at the checking memory for viruses stage under the
unstable CVS
In FreeDOS 2035a, NSSI crashed.
as it works for me (a different 2035a), could you
give some details (like config.sys).
in particular: does it crash with an empty config.sys ?
tom
In the newest unstable kernel, NSSI works excellent!
Get NSSI at http://www.navsoft.cz
Interon
--
Best regards,
Tom Ehlert
mailto:[EMAIL PROTECTED]
+49-241-79886
---
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink Toner - Free
Hello Luchezar,
Not only Bulgarians. 3/4 of the world thinks so. And many Americans and
Germans too, by the way.
there is a german saying 'hey guys - eat shit! Billions of flies can't
be wrong'
So we're just billions of flies to you. Very well :) Otherwise it's a
great anti-fashion
Hello Aitor,
Yes, but as I mentioned, the problem is that, how do we get collating
tables, etc for other countries than US and Germany? We could rely on
user's efforts to create those tables, but this can be quite laborious
(provided that, for copyright issues, the COUNTRY.SYS of the
Hello Luchezar,
It's not worth a penny because it can be freely downloaded from Vietnam
(I posted the URL here ;-)
I know bulgarians think that way.
Not only Bulgarians. 3/4 of the world thinks so. And many Americans and
Germans too, by the way.
there is a german saying
'hey guys - eat
Hello Luchezar,
Hallo Eric,
does FreeDOS already support int 2f.122f, set DOS version number?
Now it does - see patch below ;-)
according to RBIL:
INT 2F U - DOS 4.x internal - SET DOS VERSION NUMBER TO RETURN
AX = 122Fh
DX = DOS version number (h = return true DOS
Hello Luchezar,
I use IOCTL every day and that's how I found that the XMSDSK lock bug that
prevented SCANDISK from checking the XMSDSK drive had come back as Arkady
moved the lock check too low. Without anger, I wrote a patch for this, he
accepted it with some minor changes, and - voila!
Hello Luchezar,
or call the 'optimized' kernel keUNSTABLExxx or keARxxx, as the main
stream kernel should concentrate on FIXING bugs, rather then introducing
new ones.
100% agreed. Since I use unstable kernel every day in practice, I think
it has no more bugs than the stable one.
that you
Remember that Steve Gibson went round trip back to FreeDOS after
evaluating several other DOSes so this means that FreeDOS can't be that
bad :)
a) other DOS's were just too expensive
b) his problems seem to have been entirely related to the 2033 kernel
default stacksize of 128 byte
c) he
Hello Luchezar,
OK, long live the holy conservatism that saves the FreeDOS world
from the Arkadifying hell ;-G By
100% agreed
tom
---
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal
Hello Luchezar,
I didn't know that there are TWO kernel builds called 2035a... Perhaps you
should call yours 2035b where b = Bart (a = Arkady ;-)
or call the 'optimized' kernel keUNSTABLExxx or keARxxx,
as the main stream kernel should concentrate on FIXING bugs, rather then
introducing new
Hello Arkady,
For drives beyond lastdrive, get_cds result protects from crashes,
but in between, access to unformatted disks returns nonsense for
int 21.36 and even crashes while trying to do critical error dialog
te really ?
te please provide exact code sequence where it DOES return
Hello Arkady,
- may/should be `static dmatch Dmatch;' in fcbfns.c moved to stack in the
FcbFindFirstNext() (as in other functions in fcbfns.c)?
I' abolutely NOT sure about that.
you are right - it doesn't seem to make much sense.
I have some dark memory, that I changed that (back in the
Hello Eric,
EA LBA_Transfer should call the appropriate int 2f.xx function before
EA calling play_dj - or play_dj should call it itself: This allows
EA GUIs to return okay, notified, please suppress DJ text message.
INT 2F CU - DOS 5+ - FLOPPY-DISK LOGICAL DRIVE CHANGE NOTIFICATION
Hello Arkady,
Some times I report about bugs in SYS. Unfortunately, these reports was
completely ignored. (tom, what about discussion?)
to make one thing clear - once and for all time:
you post about 10 changes to this list - do you really expect that
everyone reads, tries to understand,
Hello Eric,
DosGetFree (FatGetDrvData int 21.1c/21.36) can crash, maybe because of
a NULL navc pointer.
If so, please submit some code to make the kernel crash.
if not, shut up.
I wonder if it is really desirable that the
current implementation fakes bigger cluster sizes to allow
- BREAKS FreeCOM and possibly also FDAPMs Am I run from INSTALL=?
1. MS-DOS-style mean two \0 and 2035a produces two \0.
EA So Arkady has optimized away 4 wasted bytes in environment,
6.
PLONK.
tom
---
This SF.Net email is
steffen)
put MSDOS + current distributed FreeCOM on floppy.
boot, and say F5 (skip everything)
and you'll have a load complaining FreeCOM,
although it definitively gets it's startup path.
Arkady)
it's a plain dull idiotic mathematicians braindead idea
to 'improve' freedos kernel, but break
Hi Bart,
In any case, I appreciate that a bug was found in ludivmul.inc
so do I
What I don't like is that the fix from Arkady (for the 1000th time...)
does 3 things at the same time -- formatting, fixing, and optimizing.
neither do I like that.
This makes it impossible to see where things
My dear Mr. Belousov,
_I_ _report_ bug in FreeCOM. If now FreeDOS is closer to MS-DOS and
FreeCOM now incorrectly works in both under MS-DOS and FreeDOS (with empty
environment), who wrong?
do you really think a new kernel that breaks all installed FreeCOM's
in the wild is an improvement
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
--
Best regards,
Tom Ehlert
mailto:[EMAIL PROTECTED]
+49-241-79886
Hello Eric,
I am sure 2035a fixes several bugs of 2035
found the ret_ah bug. if that has real world implications is unknown.
found the Ulong 32%32 bug - impressive, but 100% irrelevant to the
kernel as all real world use will work 100% ok.
claims to have found a bug in umb_link code for a001:
Hello Arkady,
As I already answer here, to fix bug with MOVE should be prevent moving for
directories.
te msdos CAN move directories,
If you reread my posts here (or in freedos-dev?), then you find my
letter, where I already show (with help of debug scripts), that this is
_not so_.
Hello Bernd,
be prepared to defend yourself against Tom's and Lucho's comments. I
believe it's called peer review.
in theory - yes.
in praxis - here are the reasons why
you won't see a peer review by me
I started a new branch of the kernel,
I'll not use any arkady kernel for
Hello Arkady,
just an example why I will NOT peer review anything:
just comparing old and new FLOPPY.ASM:
about every 2'nd line has changed - with no useful purpose.
sometimes - if nothing else was changed - 2 lines were simply
switched. empty lines inserted or removed. trivial comment
changes.
Hello Arkady,
where the hell are thge sources for these changes ??
config.c
- config now parsed in 5 passes:
that's fine IF config.c fit's into buffers or you boot from disk.
else (if boot from floppy) that might become *SLOW*
- screen now cleared (white on black)
well - I IMPLEMENTED THE
INTHNDLR.C, 428
if (lr.AH != 0x59)
CritErrCode = SUCCESS;
}
/* Clear carry by default for these functions */
+ /* see PATCH TE 5 jul 04 explanation at end */
+ if (ErrorMode lr.AH 0x0c lr.AH != 0x30 lr.AH != 0x59)
+ {
+ ErrorMode = 0;
+
Hello Eric,
AND I ABSOLUTELY HATE IT IF OTHER ASSHOLES COMPLETELY CHANGE THE
BEHAVIOUR INTO A WIN95 GUI LIKE BEHAVIOUR.
Pretty asshole-style behaviour to insult each other on the list, mister!
as I said - I implemented it first place;
now someone simply starts to chage THE BEHAVIOUR to his
Hello Arkady,
In kernel often used constructions, similar to next:
if (get_cds(drv ? drv - 1 : default_drive) == NULL)
in which case 'often' is 2
so I think you are wasting our time.
bye
---
This SF.Net email sponsored
Hello Arkady,
In kernel often used constructions, similar to next:
if (get_cds(drv ? drv - 1 : default_drive) == NULL)
te in which case 'often' is 2
Ok, 2. But non-zero. In any case there will be useful to introduce
get_cds1(), which will call get_cds(drv ? drv - 1 :
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
--
Best regards,
Tom Ehlert
mailto:[EMAIL PROTECTED]
+49-241-79886
---
This SF.Net email sponsored by Black Hat
technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
--
Best regards,
Tom Ehlert
mailto:[EMAIL
Hello Arkady,
Eric Auer suggests, that VERSION= should change os_setver_m*, not
os_m*. What you think? Is there is bug in current FD and Eric's suggestion
is patch for this?
seems to be a bug indeed. seems noone is using
version=X.Y ;)
tom
RANTMODE
I'M HIGHLY DISAPPOINTED TO FIND THAT SOME FORMERLY
WORKING CODE DOESN'T WORK ANYMORE;
I'M IN PARTICULAR DISAPPOINTED AS
THIS CODE WAS ONLY CHANGED TO SAVE SOME 20 BYTE OF
INIT CODE. WELL - THIS SAVES 20 BYTE, BUT COSTED
ME A MONTH TO DISCOVER - AND AN ADDITIONAL HOUR TO FIX.
TO ALL
Hello Arkady,
I found another bug:
- when fl_lba_ReadWrite() converted to ASMPASCAL (and `ret' replaced by `ret
8'), ret_AH remains as label for this tail (whereas other functions use
plain `ret').
then remove the label, compile, and see what happens :((
tom
Hello Arkady,
In above case at first glance I don't see possibilities to break
integrity ([] have top most priority over other operations), but this not
mean, that such case can't be constructed by some smart man, which knows
language even better.
another 10 points to get plonked.
Hello Bart,
if (GetBiosTime() - startTime (unsigned)timeout * 18)
break;
Menu timeout set at 10 seconds. Boot kernel with menu at 23:59:55.
Timer expires at 00:00:00 (0-1.5M = very large number)
and that's exactly the wanted behaviour.
instead of 00:00:05.
but it times out,
Hello Eric,
BC xx wouldn't have worked
after my HMA additions.
I hope you make that clear somewhere. Otherwise, people try to use BC...
I was talking about history; at these times it simply couldn't compile
with any BC.
It would be helpful to have some port MASM -- NASM document.
Two
XYZ=TRUE in config.sys?
THIS WAS INTENDED NOT TO BE DOCUMENTED. THANKS FOR AMKIING IT PUBLIC.
no kind regards
tom
---
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson Lucent use to
Hello Aitor,
If I understood Eric's point, it might be UPX fault, as it would fail
whenever it tries to enlarge the UMB as required by the uncompressed
program and silently fails. So I may have to provide uncompressed 64KB
DISPLAY.COM in the next release (last before DISPLAY.SYS).
make an
Hello Michael,
Hi, I would like to spread some fear, uncertainity and distrust
about EBDA movement!
MD Can you give the exact syntax on using that in CONFIG.SYS.
MD Is it a bare SWITCHES=/E line on its own?
Yes, it's a bare
switches=/E
I had to discover this this morning, too, as running
Hello Arkady,
AVB Why? To make code more portable between assemblers.
ROTFL
tom
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn
Hello Arkady,
AVB Why? To make code more portable between assemblers.
te ROTFL
AVB ?
Rolling On The Floor Laughing
you really can't keep things untouched?
I would really HATE the kernels assembly sources converted into
GMOUSE cryptographic sources.
tom
Hello Arkady,
AVB PS4: repeat for my previous question: why to duplicate clean and
AVB clobber? Another one: who make files status.me, *.cod, *.las?
*.cod are generated by MSC, if compiled with 'generate assembly
listing with source' (very handy when debugging)
tom
Hello Arkady,
AVB I test batch and make files both under OW12 and BC31
would be great if you ewoild test them with TV 2.01 also (this is a
reference compiler, BC31 not)
btw: there is absolutely no need to mess with them - they usually
work.
tom
Hello Arkady,
AVB Then rename add_far into normalize_ptr and remove misleading.
noone is going to rename functions because you don't like the names.
AVB Also,
AVB I may offer next code to always perform normalization:
It's there for some specific purpose.
AVB (BTW, is protection
AVB from
AVB 1. In kernel present editing code.
yes.
AVB 2. If code presented in command.com, how this affects other programs (say,
AVBDEBUG)?
command.com implements it's own doswedit-style input editor.
it doesn't affect other programs (it's not exported)
tom
Hello Luchezar,
LG Maybe later I could try it too... but first I must learn
LG Bochs!
try
DEVICE=C:\NUMEGA\S-ICE.EXE /TRA 30 /SYM 400
DEVICE=C:\system\himem.sys /TESTMEM:OFF
DEVICE=C:\NUMEGA\umb.sys
...
installhigh=
UMB.SYS is the s-ice UMB provider,
1 - 100 of 102 matches
Mail list logo
