As far as I remember, NCACHE2 doesn't work with DOS versions later than 6.
---
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to
Thank you very much, Michael, for your analysis!
Why does MS-DOS work for some people? Two possibilities besides a
FreeDOS incompatibility: 1) the memory image is different and vital
parts don't get sniped out or 2) MS-DOS function 4ch is more aggressive
about recovering memory from a failed
I got the same result as Lucho. QV.EXE freeze when quit to DOS.
M$-DOS 7.10 (Win98 boot disk) OK, no freeze.
Hopefully our DOS extender guru Michael can help us with this...
If he can't reproduce it, it's hardware dependent - a NIGHTMARE!
---
And his personal homepage
http://www.stallman.org
have a lot of goodies and news.
He's doing 1000 things at once! An incredibly active man, including his
social-political activism.
http://www.savethe.org (linked to from his home page)
THEY try to ban every possible form of copying and moving
As a future time I may look at expanding VDS support to allow known
problematic network drivers in upper memory, so if you can send
something which demonstrates the problem, that would be good. The files
should provide a way to definitively detect that things are failing, if
a crash isn't
Hi Michael,
Sorry I didn't reply earlier but I had no Internet connection since
yesterday afternoon.
I've tried the Kaspersky antivirus program -- at least running it
without the AVP files -- and it runs and terminates as expected to DOS
prompt without problems.
But it fails here, as I wrote,
Hi Michael,
I think you have an older version of ZRDX and that a newer version fixes
a bug in their bind program or earlier extender versoin. Binding with
ZRXBIND is the only way I can get a crash with it. It fails,
incidentally, with no HIMEM or EMM386 loaded or with Microsoft HIMEM and
Hola Aitor,
However, if you make the change shell=winfile.exe in the adequate
section of SYSTEM.INI (that is, replace the Windows shell from Program
Manager to File Manager), then WinFile boots normally, and seems to work
well. Further, if you open ProgMan.exe, the dialog complaining about the
Hi Michael,
Anyone here taken a look at bug 1822 in Bugzilla about Kaspersky
anti-virus and downloaded the files? I would, but I'm rather allergic
to downloading unknown files from anonymous .ru domains, given their
overall reputation. The official Kapersky site doesn't seem to list
that
Hi Michael and Tom,
Lawless, in a word. .ru sites are infamous for hosting hacks, cracks,
phreaks, passwords, net redirects, phishing, and free versions of
commercial software -- noticeably more prevalent than in the Americas,
Oceania, or most of Europe. Given that I used to make a living off
Not to mention any kind of 'ism', better not try to invade other
people's mind ;-)
Exactly! But aren't we using FreeDOS to hide from the ism we live in
(that has NO MERCY)? Sure!
I'd much appreciate the idea of Open Source and Richard Stallman.
GNU is our God and RMS is His Prophet! Amen. If
# of Cylinders__:6296 6296 787
# of Heads__: 1616 128
# of Sectors/Track__: 636363
So BIOS uses some CHS translation mechanism here. What BIOS
brand/version/date you have?
LBA support Yes 3098.8MB of LBA addressable 3098.8MB in CHS mode
What a pity that your BIOS
I've Chinese system which run into problem but I never reported, because
it's stupid to spend time for that piece of customized software which
few of us will use.
Few of *us* here maybe, but how many millions of Chinese users use it? ;-)
---
BIOS setting is CHS (translation), FDISK shows FAT32 (not FAT32 L).
So, FAT32 LBA works but we have a problem with FAT32 CHS. Unfrtunately
I can't test this here.
The hard disk parameter is auto-detected by BIOS, I've no way to change
it (16xx cylinder). I've tried:
1) FreeDOS FDISK (delete and
What is the partition type - FAT32 LBA (a.k.a. FAT32X), or FAT32 CHS
(a.k.a. FAT32)? My successful tests were with FAT32 LBA partitions. I
didn't try FAT32 CHS.
BIOS setting is CHS (translation), FDISK shows FAT32 (not FAT32 L).
So, FAT32 LBA works but we have a problem with FAT32 CHS.
I try to FORMAT a Seagate hard disk with FORMAT 0.91r and got an error
bad sector, I think maybe hard disk have some physical problem. and I
zero fill it with Disk Wizard, and later I can format.
Later I repeat this action with another PC in office and got the same
error. This time even zero
Strange is when I do a FDISK delete partition, make a new FAT32
partition and format will report 'consecutive bad sector' error, I have
to boot Win98 (with F5) to format.
What is the partition type - FAT32 LBA (a.k.a. FAT32X), or FAT32 CHS
(a.k.a. FAT32)? My successful tests were with FAT32 LBA
Hola Aitor,
I remember you starting a thread complaining how lame MS-DOS is, and Tom
replying (and I agreeing) the improvements that MS introduced in DOS in
their version 2.0. The thread was fun, true, BUT a waste of bandwith and
time, in my opinion.
Because I don't remember this, it must have
Below is the correct function. I forgot the inversion. Sorry for my
mistake.
void delay(unsigned milliseconds) /* 1 - 1985 */
{
unsigned i;
for (i = 0; i = milliseconds * 33; i++)
{
while (inp(0x61 0x10) /* refresh bit toggles with each refresh
Below is the really correct function. I misplaced the inversion and
omitted the parentheses. Sorry again for my mistakes! To err is human, to
forgive divine!
void delay(unsigned milliseconds) /* 1 - 1985 */
{
unsigned i;
for (i = 0; i = milliseconds * 33; i++)
{
Hi Tom,
maybe because that's a *really* undocumented input bit ?
The RBIL documents it. PORTS.A, table 393 says about bit 4: toggles with
each refresh request.
I searched right now, but couldn't find it anywhere.
so let me ask: what kind of 'refresh' is that ?
DRAM refresh.
does this work on
use the timer ticks
Or just do
mov ax,0E07h
int 10h
or
mov al,7
int 29h
which always produces the loadest possible beep (because BIOS does it :-)
and end this thread, please.
Finita la comedia! ;-)
Lucho
Hello Bart and Tom,
Don't forget that FreeCOM is also supposed to be able to run over a
serial line via CTTY. In that case the beep should happen on the
terminal and not on the PC where FreeCOM actually runs.
So I vote for
putchar('\007');
no BIOS, no int29, no delay timing, no direct
Hello Jim,
Could you see about getting permission to release the source code for
this CHKDSK?
I'll see what I can do, but chances are small. Our department decided that
all graduate thesises are its valuable intellectual property not to be
released in whole or in part. I wonder how it was
Hello from Bulgaria, and big thanks to Alain for providing me with an
e-mail address for FreeDOS!
I'm back just to announce the availability of a freeware FAT32-enabled
CHKDSK written by some of our most gifted graduate students. It's at
http://linux.tu-varna.acad.bg/~lig/freedos/CHKDSK.ZIP
I
I seems that you have to hide you adress better ;-)
No, I just have to STOP ATTENDING THOSE FORUMS!!! :(
IS PAYING $$$ FOR ALL THOSE VIRUSES AND SPAM ENOUGH?
THIS IS MY *LAST* POST HERE, BECAUSE SOON MY E-MAIL
ADDRESS WILL BE VISIBLE BY EVERYONE IN MAIL-ARCHIVE.
I WILL NOW UNSUBSCRIBE FROM
Michael, I have such a PC but I haven't understood whether you have
uploaded the test version or not. If yes, please point me to the exact
URL, else please send me the binary to test at lucho m0nkey gawab
fullst0p com.
Thanks,
Lucho
---
This
On Tue, 06 Apr 2004 17:12:11 +0200, Bernd Blaauw wrote:
Michael, I have such a PC but I haven't understood whether you have
uploaded the test version or not. If yes, please point me to the exact
URL, else please send me the binary to test at lucho m0nkey gawab
fullst0p com.
On Tue, 06 Apr 2004 19:34:48 +0300, I wrote:
I don't see a binary dated 27 March, so I got the source dated 27 March
but it doesn't build. TC 2.01 gives some warnings which I corrected but
then TASM 5.3 complains about the // comments put in the intermediate
.ASM file by TC. I don't have the
Below are my quotes and after them, the corresponding explanations.
You've always been honest to me so I'll be honest to you, too.
I'm too busy/lazy/whatever to implement this, so here's an excuse:
Please redirect your request to FreeDOS-kernel mailing list ;-)
For the last 2 years Alain has
On Fri, 02 Apr 2004 14:15:25 -0300, Alain wrote:
Do you have it handy to send it back to me? I hava a dos version program
and I do have a rom-dos and I would like to test it.
Here it is, from my old archives (when I was a Linux man using ROM-DOS and
FreeDOS was DOS/C):
Can an application tell
On Wed, 31 Mar 2004 22:07:55 +0100 (BST), Bart Oldeman wrote:
Hmm. Sorry I didn't check out how dosfsck is compiled but perhaps you
should compile with the GCC
-Wall -Wstrict-prototypes
options.
-Wmissing-declarations
may also come in handy
-Wnested-externs
sometimes too but it depends on your
The TU-Varna server doesn't work now
Just began working so I put it at
http://linux.tu-varna.acad.bg/~lig/freedos/DOSFSCK.EXE (58 KB)
Happy testing! But please take into account that I don't maintain it!
Lucho
---
This SF.Net email is
On Thu, 01 Apr 2004 16:23:53 +0800, Johnson Lam wrote:
But VER /R of FreeCOM already does this! Typing VER /R gives:
FreeCom version 0.82 pl 3 XMS_Swap [Dec 10 2003 06:49:21]
DOS version 7.10
FreeDOS kernel version 1.1.33
Oh ... I don't know.
Hidden switch? :-)
It's documented, not hidden (type
On Thu, 1 Apr 2004 17:50:12 +0100 (BST), Bart Oldeman wrote:
So the result is: Ein Volk, ein Reich (Microsoft), ein Fhrer (William
Henry Gates III)! :-(
Hmm -- that won't stop you using MS Windows though...
User-Agent: Opera7.23/Win32 M2 build 3227
Yes, I use the weapon of the enemy (W2K3)
On Thu, 01 Apr 2004 15:39:22 -0300, Alain wrote:
There is also one other for DR-DOS and something (which I don't know)
for Datalife-ROM-DOS.
Right. I posted the ROM-DOS one at the kernel mailing list last year.
But specificaly for FreeDOS it is not enough because there are far too
many
I move this discussion to the place where it belongs - the kernel mailing
list.
On Thu, 1 Apr 2004 21:46:29 +0100 (BST), Bart Oldeman wrote:
This string can't be removed -- it's part of RBIL:
D-2133FF-
INT 21 - FreeDOS - GET DOS-C/FREEDOS KERNEL RELEASE
Oops! VolumeSeek() should be loff_t(loff_t offset) instead of off_t
VolumeSeek(off_t offset)! But there must be yet another bug, because
when I changed it, the bug was still there, although the code generated
for VolumeSeek() became correct. Will try to catch the other bug
tomorrow.
Caught it!
On Thu, 01 Apr 2004 13:41:33 +0800, Johnson Lam wrote:
Or improve FreeCOM's VER to show Kernel version also.
But VER /R of FreeCOM already does this! Typing VER /R gives:
FreeCom version 0.82 pl 3 XMS_Swap [Dec 10 2003 06:49:21]
DOS version 7.10
FreeDOS kernel version 1.1.33
Lucho
I agree with Alain. DOSFSCK 2.10 with fixed 2G bug will be the easiest
and the best solution.
Lucho
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo
On Mon, 29 Mar 2004 15:43:26 +0200, Bernd Blaauw wrote:
Luchezar Georgiev schreef:
I think that each OS has its own niche. Neiether Linux nor DOS can oust
each other. But try to fit a Linux in the BIOS flash ROM chip when you
have only several tens of kilobytes free there!
www.linuxbios.org
On Mon, 29 Mar 2004 00:56:48 +0200, Bernd Blaauw wrote:
crash if UDMA loaded high, but no VDS present // XMS-test should have
been done and succeeded.
UDMA checks if VDS are active and if so, uses them to lock the buffer
and obtain a physical address, else calculates the physical address
What version of TASM do you use? I haven't had LGDT problems with TASM
5.3 dated 30.V.2000.
AFAIK, latest DOS version of TASM was 4.1. 5.x is version of TASM for
Win32.
TASM 5.3 was released as a PE executable but then was converted to DOS
using WDOSX, so it now works under DOS! Undertunately,
On Thu, 25 Mar 2004 20:08:32 -0300, Alain wrote:
about fat32 testing: I believe a working DOSFSCK 2.10 just what is
needed (not what is whished for).
Actually, I agree! If Eric can say FreeDOS SMARTDRV is LBACACHE, why not
say FreeDOS SCANDISK is DOSFSCK? ;-) DOSFSCK is not a SCANDISK, but
On Fri, 26 Mar 2004 01:58:56 +0100, Aitor Santamara Merino wrote:
As far as I know, APPEND is considered dangerous and incompatible. It
had better stay missing.
Well, it is not aware of task switchers, it may have problems with
executing nested SHELLs, true. Many reasons why MS does NOT support
Thanks, Aitor!
1.0 todo's: http://fdos.org/ripcord/fdos_1_0/official/todos.htm
As far as I know, APPEND is considered dangerous and incompatible. It had
better stay missing.
I think that SCANDISK is the most important missing program. Whether to
borrow code for it from CHKDSK, DOSFSCK, both or
If we have a fat32 kernel, and chkdsk is only fat16 we cannot use it :(
We can, but only on FAT12 and FAT16 volumes.
But SCANDISK must support FAT32. That's why it had better use the DOSFSCK,
not CHKDSK engine.
---
This SF.Net email is
Yes, Bart, the show must go on! ;-)
The FreeDOS spec still states that we should be compatible with MSDOS
3.3.
Here is a quote from the spec
(http://fd-doc.sourceforge.net/spec/spec.html):
The MS-DOS 3.3 compatibility extends only to the FreeDOS kernel. FreeDOS
programs should be compatible
This proves nothing:
- you is liar?
- no.
OK, King of logic! ;) My logic is wrong but my assertion is right as
you'll see. Qui prodest?
the century of the downfall of empires... ;-G
Oh, Lucho, please, make less general purpose loud sentences.
OK. More specifically, the first empire to fall will
Hola Aitor!
I'd like to ask if someone has successfully compiled UPX/UCL.
I did this last year with DJGPP 3.02, and could try UPX 1.91 with DJGPP
3.33, but I don't think it's worth! See my post at
http://upx.sourceforge.net/phpBB/viewtopic.php?t=255 (quoted below).
Lucho
Posted: Wed May 14,
If the US or any country can drag someone into prison because of
stealing idea
They did this already. Remember the Adobe vs Elcomsoft (Dmitry Sklyarov)
case. And they do this not only for stealing ideas, but also for simple
disobedience (e.g. Slobodan Milosevic).
this country or the world will
On Sun, 21 Mar 2004 02:04:57 +0800, Johnson Lam wrote:
Today afternoon I met BAHCL and have a nice talk with him. He did really
afraid being sued because of a program that he only got no profit, no
praises, and sweating long working hours of thinking and debugging.
Sorry to hear that, and hope
On Thu, 18 Mar 2004 20:34:48 +0100, tom ehlert wrote:
You may be able to do this Real Soon Now (in the FSF's sense, which
means some months ;-)
unlikely. changing the license (from GPL2 to GPL3) requires written
consent from all contributors ;)
;) ;) ;)
But I didn't mean that... ;-)
Lucho
On Thu, 18 Mar 2004 18:35:30 -0300, Alain wrote:
Following SCO example, if we do that, _every_ FreeDOS user could be
sued. That would be catastrophic.
Wow! Did I hear right? Do you say this seriously? Who do you think could
sue us, interestingly? And why would he do that? What we did wrong?
On Thu, 18 Mar 2004 16:12:41 +0100, tom ehlert wrote:
Or do you mean Anton Zinoviev, since he wrote several files from
scratch?
several ? and I will immediately remove the BG keyboard from MKEYB,
should he ask me.
As an active Linux developer he probably doesn't care, and even if it does
this,
On Thu, 18 Mar 2004 17:42:52 +0100, tom ehlert wrote:
and that's the point where it hurts: that I can't exepack KERNEL.SYS and
FREECOM.COM with aPack to save some Kbyte
You may be able to do this Real Soon Now (in the FSF's sense, which
means some months ;-)
Those tiny 200 bytes provoked the
On Wed, 17 Mar 2004 10:54:16 +0100, tom ehlert wrote:
MKEYB 0.40 released
website http://www.drivesnapshot.de/freedos/mkeyb.htm
download http://www.drivesnapshot.de/freedos/mkeyb.zip
changes:
now uses APACK for 200 byte smaller executable
licensing changed to allow distribution of APACK'ed
Today, Markus Franz Xaver Johannes Oberhumer launched his new site at last
(after NRV marsed)!
http://www.oberhumer.com/company/partners.php
Here is the explanation why NRV isn't included in UPX. This was an old
hypothesis of mine, but it's now over-confirmed. He just had signed NDAs
with
Do you remember the executable compression thread started here by the
GNU GPL guru Dave Turner? Here is what I found at his site
(http://web.novalis.org/history-of-fsm/slide-47.html):
Sept 3, 2003 Free Software Licensing in Context GPL version 3
A new version of the GPL is coming
On Sun, 14 Mar 2004 21:52:29 -0600, Michael Devore wrote:
total(available) EMS 6(5) pages = 96(80) kByte
I'm going to pump up the default EMS allocated by 96K for NOEMS, which
should always leave at least a little bit for VCPI and give more for EMS
internal tables with lots of RAM, like you
On Wed, 10 Mar 2004 14:54:58 -0300, Alain Mouette wrote:
Only one program is missing and that is a Scan-Disk (written as 2 words)
Afraid of the M1CR0$0FT police? ;-) Let's swap the words then and call it
DISKSCAN!
utility for Fat32. For what I kow, DOSFSCK is working and need only a
small
I got your photo, sailormoon otaku :-)
Is this is some mixed English-Japanese language? :)
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies.
On Mon, 08 Mar 2004 10:55:29 +0800, Johnson Lam wrote:
This mean I need to debug.
The following is the source code of freedos/frame.html
html
head
frameset cols=220,*
body bgcolor=#ff text=#00
titleOld Song/title
/head
body
frame src=toolbar.html scrolling=auto name=bar frameborder=no
On Wed, 03 Mar 2004 18:16:40 +0100, Aitor Santamari'a Merino wrote:
Most is described in books such as Undocumented DOS.
Would be good to read, but not available here :-(
Of those many undocumented books series by A. Schulmann, only UndocDOS was available in Spain (under a bad translation, btw),
On Thu, 26 Feb 2004 02:29:49 +0100 (MET), Eric Auer wrote:
I think chances for WDOSX are not too bad.
They're zero. See below why.
Where can I find it???
http://michael.tippach.bei.t-online.de/wdosx/
Not sure what not relocateable means here.
It means that this is a fixed executable, which
Yet another 3-letter maniac's proposal ;-)
DOS\BIN executable files
DOS\LSM linux software map files
DOS\HLP help files
DOS\MAN manuals and other documentation
DOS\NLS national language support
DOS\SRC source code, divided into project subdirectories
I'd divide *only* SRC into project
LG I'd divide *only* SRC into project subdirectories. BIN, INF, HLP, MAN and
LG NLS better be common for *all* projects, as they usually contain only a
LG single file per project (with some exceptions).
_Not_ agreed - many distributives contains similar files (readme,
what.new, etc.), so MAN
On Sun, 22 Feb 2004 16:37:47 -0600, Jim Hall wrote:
Okay, we can stop the discussion now. I've gotten *lots* of email asking to keep UDMA in 'base', and none yet to say it should be in 'util'.
Consider UDMA a new resident of 'base'. :-)
Thanks, Aitor, Bernd, Erwin, Jim, Johnson, Steve, and all
Hi BAHCL (may I know at least your first name? ;-) Because you use Yahoo, my mail server was putting all your messages into its bulk folder, until I found out this and downloaded them today!
Usually there are people working as system operator
and system coordinator to make things go as smooth as
On Mon, 16 Feb 2004 15:32:27 -0600, Jim Hall wrote:
We've actually addressed this issue before. Some years ago, the source code to MS-DOS was leaked. For a while, I would get about an email a week from people (who probably thought they were being helpful) asking if I wanted access to the
Hello,
Let me remind that the first 720 KB ODIN image I uploaded at http://linux.tu-varna.acad.bg/~lig/freedos/ODIN.720 wouldn't work on 8086/88 processors but required at least a NEC V20 or 80186/188 because I forgot the --8086 UPX option when compressing the files there. So I re-created it,
Hola,
http://community.borland.com/museum had the compilers for free last I checked --;
I've download tc201. Can you please send me a few lines about how to compile?
Or should I need to setup tc201 first? (extracted in disk 1,2,3 directory).
I don't think that users should be forced to compile
On Wed, 11 Feb 2004 12:59:27 + (GMT), Bart Oldeman wrote:
it does not allow you to modify the stub. That's the main point.
If this wasn't required by the GPL, why would one want to do that? That stub is very short (between 133 and 340 bytes long) and is so heavily optimised that hardly anyone
Hello,
[...] You could call the unpacking stub part of what is added due
to the compilation process. Or you could open the sources of the
(usually very short) unpacking stub. In either case you do not need
to open the sources of the executable packer itself.
Joergen wrote that he'd gladly open
Hi,
http://fd-odin.dosius.com
disk image and source zips.
Thanks - just for Power Users: no install, no config, no autoexec, no menus, not anything but pure content ;-) One note from an Easterner for whom size STILL matters - if you format UNCONDITIONALLY a diskette, then put all the files there,
On Wed, 4 Feb 2004 03:20:41 +0300 (MSK), Arkady V.Belousov wrote:
I don't know how organized the Watcom RTL sources,
but, probably, there are more common files. In this case, to make
executables smaller, there remains only one way: instead .obj compiler
should generate .lib files, where each
On Tue, 3 Feb 2004 05:06:41 +0300 (MSK), Arkady V.Belousov [EMAIL PROTECTED] wrote:
But there remains unrecoverable errors, because Watcom doesn't knows
register pseudo-variables (_AX, etc) and __emit__. Unforunately, there are
places, where inline asm is required. Fortunately, Watcom knows
Hi,
Tested Imre Leber's dosfsck(8) 2.10 port for DOS (at http://users.pandora.be/imre/FreeDOS/) and it works for me on most disks, except on diskettes (hangs up until the diskette is removed, then says Read 32 bytes at n:No Error) and on large FAT32 drives (says Seek to nnn:No Error).
78 matches
Mail list logo
