Re: [Freedos-devel] FreeDOS need clean up!

Hi Johnson, > >Our kernel is only ca 40 kilobytes on disk, which is quite small. > I don't believe it's already optimized to zero excess code I know, some people would say "hey we can make it 39 kilobyte and gain 1 kilobyte of free HMA space". But only very few apps use the HMA, so I generally a

Re: [Freedos-devel] A Poll of sorts

Hi Johnson, > >And adding complex filesystems such as ext2, ext3, or ntfs to the > >FreeDOS kernel will certainly not make it smaller, probably more like > >100% bigger. So you need a driver indeed, and some exist, but that > >won't enable booting. > > Is it able to let DOS call "external support

Re: [Freedos-devel] DEBUG v1.07

> http://www.japheth.de/Download/debug107.zip > contains FreeDOS Debug v1.07, a bugfix release. 1.07 [3 November 2007] bugfix: entering ranges with upper bound was refused. bugfix: if help cmd waited for a keypress, it displayed garbage if cpu was in protected-mode and CWSDPMI

[Freedos-devel] simple freedos 1.1 installer please / 1.0 overview

Hi and merry xmas to everybody :-) I have been trying to understand the installer batch files, but they turned out to be too complex... What I did find out is that there are many variables: Autoexec: DEBUG NLSPATH dircmd lang config PATH cputype ... plus runs GETARGS > temp bat and then calls th

Re: [Freedos-devel] simple freedos 1.1 installer please / 1.0 overview

Hi Oleg, > > distros if wanted. You cannot boot from CD on pre-386 anyway. Most BIOSes only introduce CDROM boot late in the 486 days... There is Smart Boot Manager which can be booted from diskette to boot from cdrom, and there is SHSUCDHD which can mount the CDROM ISO from disk even if you hav

Re: [Freedos-devel] simple freedos 1.1 installer please / 1.0 overview

Hi Oleg, > What do you propose? Do not install sources at all? I propose to have screens where the user can toggle checkboxes for each source package, but have none of them set to "yes" by default. Actually it would be nice if TEXTINST had a button for "set all to yes" and "set all to no" in the

Re: [Freedos-devel] simple freedos 1.1 installer please / 1.0 overview

Hi again, > > IMHO i18n should be done by _POST_install_ scripts... > I agree with Eric here; this would discourage > people who can't read english. You misunderstood me. I think it is nice that the installer can do the font and keyboard setting for you. But I think it is not good that there are

Re: [Freedos-devel] New Mouse Driver Development...

Hi there :-) > Hello everybody! CuteMouse project is dead; I can develop new mouse > driver for the FreeDOS project. This driver, named "FreeMouse", I > started today. Please reply to me, I want that you help me writing Well maybe you did not wait long enough for a reply from Nagy Daniel: Curren

Re: [Freedos-devel] CuteMouse v2.1 does not work on DELL Inspiron 1501...

Hi! (I would say "Hi NAME" but I cannot type Cyrillic, please suggest a spelling for your name in Latin...) > Hello all. New CuteMouse v2.1 is not work on the my notebook DELL > Inspiron 1501. In this notebook, mouse (touchpad) has detected as "PS/2 > mouse" and properly work with Microsoft Mous

Re: [Freedos-devel] New Mouse Driver Development...

Hi Arkady, thanks for the feedback :-) > EA> Current CuteMouse 2.1 development is done by me :-) . > > And how progress so far? (I was missing half of year, so I miss > latest news). Unfortunately, you did not miss much. But at least CuteMouse is still maintained, and people still get support w

Re: [Freedos-devel] New Mouse Driver Development...

Hi Alain, > IMHO the default should be off, but the code should remain > there. For Genius? Agreed. Probably would be harder to remove it ;-) > it would be logical that *these* programs have instructions > to activate [the wheel]. You mean have docs to instruct the user how to activate it when

Re: [Freedos-devel] New Mouse Driver Development...

Hi Arkady, > I not seen your edition yet, so I not have any ideas. :) It is on www.coli.uni-saarland.de/~eric/ctmouse21b3.zip Your points about the macros are okay :-) > "is empty or attached mouse in Mouse Systems mode". :) And Genius > mice are long ago based on Logitech protocol. Whic

Re: [Freedos-devel] New Mouse Driver Development...

Hi Flox, > > In short, the wheel stuff is > > less foolproof than the protocol without wheel, and as 95% of > > the DOS apps do not use the wheel anyway, > Yes, but 3 apps that are important: 4DOS, Arachne (but it needs > its own ctmouse??) and Mpxplay. Then users of those apps will have to li

Re: [Freedos-devel] FreeDOS reads DVD discs

Hi HCL, > I found it in the Australian PC magazine (APC) DVD and > modified it in my desktop that works well. Ah nice! I wonder whether we could get a copy of whatever they write about us so we can put it on our press coverage corner on our homepage? > I don't know if this feature has been docu

Re: [Freedos-devel] New Mouse Driver Development...

Hi again, > >> EA> has an option /Y ignore Mouse Systems, and most people > >> I myself always use /y - I not like and not use mouse systems > >> mice, whereas I prefer not remain in my RAM useless code stubs. > EA> So you agree to make /y the default :-) > No. I just express my own preference,

Re: [Freedos-devel] New Mouse Driver Development...

Hi Arkady, you are right, disabling the wheel only helps compatibility in the PS2 case. But as said, I assumed that wheel usage in DOS is rare, so /O (OPT_noWheel) affects both PS2 and COM at the moment even though COM wheels seem to be no real risk for compatibility... Would be easy to change :-

Re: [Freedos-devel] New Mouse Driver Development...

Hi Alain (including a reply for Ladislav), L> If you by default disable the wheel (and I think it is not good L> idea) you definitely must write some mouse tool which can detect L> mouse. It is necessary for FreeDOS installers. Installer calls L> this tool and found whether mouse has or hasn't th

Re: [Freedos-devel] New Mouse Driver Development...

Hi! > "Want"? Capturing first port is usually safe and not hurt, there only > one drawback - extra stub in memory. COM port mice are the exception now, so allowing MSys mode means that a mouse driver is loaded at a place where no mouse exists (and no mouse will be connected to the COM port later

Re: [Freedos-devel] New Mouse Driver Development...

Hi Arkady, > /3 - force 3-button mode (for Microsoft and PS/2 mice only) > force wheel support (for PS/2 mice) > BTW, /3 option was used to force middle button support through L+R > extension. Now there remains only option. If /3 has no effect now, it should be removed from

Re: [Freedos-devel] New Mouse Driver Development...

Hi! > >> /3 - force 3-button mode (for Microsoft and PS/2 mice only) > >> force wheel support (for PS/2 mice) > >> BTW, /3 option was used to force middle button support through L+R > It has effect - without it, PS2 handler will not return info about 3rd Well but then /3 onl

Re: [Freedos-devel] FreeDOS directory standard (1.1?)

Hi! > LIB for libraries. We never really defined a "lib" before because > FreeDOS doesn't support the shared-library model... I would put those in BIN if dynamic and in SOURCE if used to compile > INCLUDE would be a good place for any *.h files that are associated > with the libraries in LIB. B

Re: [Freedos-devel] FreeDOS directory standard (1.1?)

Hi! I assume you mean "APP" is the name of the app, so it is different for each package / app? > APP\BINARY No - one binary directory for all apps. Otherwise you would have a very long PATH. Linux and Windows also have only a few binary directories and put all apps in those few directories. >

Re: [Freedos-devel] FreeDOS directory standard (1.1?)

Hi Aitor! > A third option would be: ok, make both LIB and their H files under > SOURCE, but at least, allow to define some standard path as: > > SOURCE\LIB > SOURCE\INC > > for that. That would be a good idea. Then every source/name_of_app/something can refer to libs as ../lib/something and t

Re: [Freedos-devel] FreeDOS directory standard (1.1?)

Hi Antony, > In FreeDOS 1.1 (or whatever) once the directories are finalized, a > system variable can be declared in the OS (at the master environment > level) like in Windows NT/2000/XP called SYSTEMROOT. On my Windows > machine it's C:\WINDOWS. For FreeDOS it can be C:\FDOS. Then the other Thi

Re: [Freedos-devel] Installed Application Database Hypothesis

Hi Antony (please use plain text mail without html!), > Implementing an Installed Application Database along with an associated > install API would make installing applications easier (perhaps somewhat > akin to Windows). There is not an API but a tool. We do have that tool. It does have an inst

Re: [Freedos-devel] Curious MS-COPY behaviour

Hi, > >http://support.microsoft.com/kb/69581 > >how could one interpretate that +,, ? Actually our COPY neither supports appending to a file yet (quite annoying), even though it does support concatenating some files to create a new file. Nor does it support using , placeholders to pass empty pa

Re: [Freedos-devel] FreeDOS' Help: Russian translation

Hi Oleg, > Does anybody work on Russian translation of FreeDOS html Help? > And, if not, could I help with translation? Before you can translate the help, it has to exist. Fritz has been working on a big htmlhelp update in the last months. It will also include a German translation. Please contac

Re: [Freedos-devel] FreeDOS bugzilla

Hi Jim, > There's a dump of the MySQL database on www.freedos.org... I had guessed / feared that ;-) So now I spent half of the night installing MySQL (because SF uses it) and PosgreSQL (because I use it) and DDL-UTILS (which convert between many databases and XML) on my PC, failing with the lat

[Freedos-devel] FreeDOS bugzilla conversion to sourceforge trackers

Hi Jim, I now downloaded the "binary zip" from db.apache.org/ddlutils/ which luckily installs A LOT easier than the source edition... Also needed 2 extra JARs: mysql-connector-java-5.0.8-bin.jar and postgresql-8.2-507.jdbc4.jar - for obvious reasons :-). A few fixes were needed to get the ddl u

Re: [Freedos-devel] Fresh ClamAV/DJGPP Port

Hi! > > Should a recent virus database be included in the package, or > > should this be left to the user to download? > > I think yes - because not everybody has internet under DOS. I think there should be downloads with and without virus list, as people with slow internet will prefer the down

Re: [Freedos-devel] FreeDOS bugzilla

Hi Aitor, > If there was an option to dump current bugzilla info to a file or > something like that, before losing it completely, I'd do it that too > (in case you guys are thinking of taking bugzilla down some time). I already downloaded our bugzilla bug database and converted it from a mysql d

Re: [Freedos-devel] FreeDOS bugzilla

Hi Jim, > Since you mentioned tassilo's hosting offer: why did *you* promise > that *I* would pay for the server hosting? Several times, I asked I never did promise that. > you to cc me on your conversations with tassilo on this topic, but > you chose to keep me out of the loop. Now I find out

Re: [Freedos-devel] FreeDOS bugzilla

Hi Aitor, > > Since Eric and tassilo have identified the free web hosting for > > FreeDOS bugzilla, and since Eric has volunteered to install the new > > FreeDOS bugzilla, migrate the existing data, and do any ongoing > > maintenance - so I think we have a winner! :-) Well as we only migrate fro

Re: [Freedos-devel] freecom & kernel

Hi Oleg, > I want to put FreeCOM and the kernel into a ROM. Of course, both need > recompilation... What is minimal size of freecom and kernel I can reach? Typical kernels are somewhat above 40 kB, but RayeR has made slightly lighter versions for his RomOS :-). As for FreeCOM, typical sizes star

[Freedos-devel] Announce: fat32 undelete, need guinea pigs, contributions

Hi again, after all the discussion about people being interested in having a fat32 undelete but nobody who would actually write one, I finally added the changes which outlined in an earlier mail myself. The result is available online: www.coli.uni-saarland.de/~eric/stuff/soft/undelete32beta.zip

Re: [Freedos-devel] Directory structure

Hi! > One of the design goals of FreeDos is MSDOS back compatibility. > I think all the OS base files must be in the dir c:\dos, there is where > the old MS-DOS programs and user will look for an aplication. You can always copy the contents of c:\fdos\bin there, and adjust your PATH setting... H

Re: [Freedos-devel] QUERY: freeDOS source

Hi Andrew, > Is freedos a reverse engineering of MS-DOS... No. It is a program written based on the documentation about what MS DOS does for you, how it interacts with DOS software and drivers. At the moment, the FreeDOS kernel behaves a lot like MS DOS even as far as some quite exotic things ar

Re: [Freedos-devel] FileSystem Suggestion

Hi again, > /config/boot > /floppy > /hdd ... I assume you mean /config/boot/floppy and so on: In DOS, configuration is stored in config sys, in autoexec bat, and possibly in configuration files for the drivers you load, but that depends on which drivers you load and who made

Re: [Freedos-devel] about Directory Structure

Hi Neagu, > The reason I did consider this Directory Structure better is because > I think the purpose of FreeDOS is to develop in time not to remain > in this way. Yes but it fixes a non existing problem... At most, it makes the directory structure match your taste, while tastes often differ...

Re: [Freedos-devel] How to create alternative shell

Hi Marco, > I would like to write an alternative interpreter command > to replace command.com/Freecom. That can be as easy or as hard as you want. > I have basic programming knowledge. Good. > I'm clear that I must to provide a replacement > for all internal commands. No. Almost any program

Re: [Freedos-devel] How to create alternative shell

Some added comments... > Secondly, if you know about BNF, lex and yacc Those are about parsing. In other words, they are about how you decide what a STRING like "copy *.txt *.com x: /z" wants to TELL your shell ;-). > What programming language you use is entirely up to you - though I doubt that

Re: [Freedos-devel] Fwd: freedos defrag methods

Hi! > I tried to defragment my 10Gb fat32 hdd. I choose quick try. > terminates: the working the disk map appears not fragmented. > I quit and exit, then restarting defrag: the map is the same > as before quick try. Because quick try only takes care that each file consists of only ONE area on th

Re: [Freedos-devel] Fwd: freedos defrag methods (OT)

Hi! > For this it is very sad that FreeDOS does not use the LEAN file system > (http://freedos-32.sourceforge.net/doc/lean.html) instead. That has back > pointers for pretty much everything and would as a consequence be much > faster. A lean ad ;-). But you can just as well build data structures

[Freedos-devel] compressed FAT filesystems (was: defrag methods)

Hi! > Maybe with adding compression it could make a replacement for > doublespace? (running it through the network redirector obviously) Nope, doublespace compresses the actual data on your disk, not the space which is free anyway ;-). I think it would be nice to have a driver for one of those f

Re: [Freedos-devel] Fwd: freedos defrag methods (OT)

Hi Imre, nice explanation, thanks :-). > Here are the numbers for the data structures used by defrag, > when calculated for FAT32. You mean for a worst case FAT32 filesystem with 2^28 (256M) clusters where the FAT on disk is also 1 GB per copy... > Cluster movable map: 32 MB (fat size * 1 bit)

Re: [Freedos-devel] compressed FAT filesystems

Hi Imre, > Which free/open compressed embedded filesystems would that be? Browsing wikipedia a bit gives me quite a few READONLY free and open source compressed filesystems, several of which are useful for embedded systems. For writeability, you would typically have to alloc new space in your fi

Re: [Freedos-devel] compressed FAT filesystems

Hi Imre, > Does the fact that all this runs on linux slip your mind > (like in no way interesting for the stated purpose). Some of the filesystems claim to be implemented in only 4 kilobytes of code. Which is a lot smaller than the FAT engine in the FreeDOS kernel, for example. If you made a va

Re: [Freedos-devel] compressed FAT filesystems

Hoi Imre, > You did however make the very valid point that implementing a > compressed file system is not so easy as one might think. Luckily the task gets a lot easier if the filesystem will be readonly (tool to create it, driver to read it). And such a filesystem is still pretty useful :-).

Re: [Freedos-devel] some DJGPP help asked.

Hi Robert, Bernd, > > - cannot compile anything later than 2.01.01a11 (very latest is > > 2.01.01a38). Either makefile broke or something else? > > "cannot compile" is a very bad error description. > Please reveal more details! Indeed. You may have to set your screen to show more lines or use RE

Re: [Freedos-devel] compressed FAT filesystems

Hi Antony, for now, I would not recommend to try to clone any MS compressed filesystem. Remember that they themselves have had licensing issues with their own compressed filesystem. One thing which makes doublespace and co complex is their ability to WRITE to the filesystem while it is mounted /

Re: [Freedos-devel] compressed FAT filesystems

Hi Antony, (please switch from HTML to plain text mail...) > I would think that the information contained in the MS-DOS 6 > Programmers reference is free of any restrictions related to > that lawsuit. (I assume you mean the one which forced MS to go DOS 6.2 to 6.22 and replace a bad license comp

Re: [Freedos-devel] compressed FAT filesystems

> Stored in reverse order, with the short file name after the long > one, yeah that's realy got to make speed. Dear Imre, the MS algorithm is really a LITTLE bit more advanced than a linear read of the directory. Try to find and read the patents. Eric -

Re: [Freedos-devel] compressed FAT filesystems

Hi Imre, > Well, I think that a seperate partition with a compressed file > system and a block driver would be the best option. I agree about the block driver, but I believe a file would be more flexible than a partition. Once you compress a partition, you would otherwise have to shrink it to ma

Re: [Freedos-devel] (no subject)

Hi Someone, > You are not allowed to read this mail below this line. I am not > responsible for any content. ... > I am a fan of your project! Somewhere on your homepage it writes > there is no 100 % compatibility with MS-DOS because there are some > undocumented functions. ... > Maybe you are al

Re: [Freedos-devel] lbacache stack space too small

Hi Kevin, (sorry everybody for the long mail :-p Otoh, Kevin keeps CCing the mailing list - and Alain thinks always CCing the list is a good way to let people know that DOS is alive. oh well... ;-)) > > Hmmm I thought Bochs already uses a LGPL BIOS...? :-) > > Yes - I am working on the bochs bio

Re: [Freedos-devel] lbacache stack space too small

Hi Kevin, > Bochs bios is compiled with "bcc" and "as86". I've ported it to "gcc" > and "gas". I did convert most of the assembler to C code. > SF.net/mailarchive/forum.php?thread_name=20080222155930.GA7310%40double.lan&forum_name=bochs-developers Hmm thats a long page but I do not see the why

Re: [Freedos-devel] Creating packages

Hi Robert, > Of course, all have documentation in standard man pages. ;-) That is not standard, that is Unix ;-) > AFAIK FreeDOS doesn't come with a man page reader. So what's > the best method to make documentation accessible to DOS users? We have the HTMLHELP system. You should contact Fritz

Re: [Freedos-devel] Creating packages

> Is fritz.mueller [at] mail.com still valid? Yes, but why not ask off-list? > What zip contents? HTMLHELP can show HTML pages directly while they are still in a ZIP. But of course you can override by putting unzipped HTMLs on disk. > > be okay to have the ASCII version in doc/PACKAGENAME/*.tx

Re: [Freedos-devel] Floppy with Freedos + Euphoria Language

Hi Marco, > I'm sure Euphoria is the best interpreted > language available for DOS today... How about Perl (bloated) or Reginarexx for example? ;-) > is under active development, and is really > cross platform DOS/Win/Linux. The others are also cross platform but I do not know how active their

Re: [Freedos-devel] USB driver

Hi Marco, > There is someone working on a free USB driver? > This is really needed piece of software. USB-what driver? Saying USB driver is similar to saying "driver for things running on electricity". > I have look for some documentation about in the net, > but is a very complex to me. I hope

Re: [Freedos-devel] USB driver

Hi Tom, Marco, > > That I have in mind is mass storage, mainly flash memory stick... > > Boot from cd-rom is OK as emergency tool but is a static > > system where you can't save your preferences or documents, > > will be better to have a portable USB system able boot on real > > or virtual machin

Re: [Freedos-devel] Willing to help

Hi! > just an idea came to my mind: you could make a freash port of those > common Unix utilities... IMHO it would be most welcome. I doubt that - disk space is not an issue today and MANY Unix utilities have been ported to DOS using DJGPP, the GNU C (gcc/g++) and LIBC for DOS, 32bit style :-).

Re: [Freedos-devel] dir bug?

Hi Marco, > On ms-dos 6.22 using dir * is the same as use dir *.* > On Freedos dir * is the same as dir *. Maybe related to a FreeCOM command.com issue: MS DOS command.com has some extra handling for "implicit wildcards", see Bugzilla: http://bugzilla.freedos.org/cgi-bin/bugzilla/show_bug.cgi?i

Re: [Freedos-devel] Willing to help

Hi! > ...write code to support it. We could use a compatible > Backup/Restore that is under the GNU GPL or a similar > free-for-everyone license. The FreeCOM project has been idle for a > long time, and needs a maintainer to update it. There have been > various requests for the kernel that need f

Re: [Freedos-devel] freecom Re: dir bug?

Hi Marco, > we agree that DOS/Windows command translate "dir *" to "dir *.*" Yes. I was wrong when I closed bug 1690 as "duplicate" of another bug several years ago. Please add your information to that bug and re-open it: http://bugzilla.freedos.org/cgi-bin/bugzilla/show_bug.cgi?id=1690 > The

Re: [Freedos-devel] JWasm

Hi! > JWasm is available, a Masm v6 compatible Assembler, Open Source: > http://www.japheth.de/JWasm.html Nice, how masm compatible is it? And how wasm compatible is it? What are the requirements, is a 386 without FPU enough...? Are a few megabytes of RAM enough? Other relevant details? > It's

Re: [Freedos-devel] JWasm - possibly free MASM

Hi all, Lucho told me that DOS LINK and Win32 MASM are online on the MS homepage. While the license is worse than the JWasm one (eg no 8.0 commercial use) it can still be interesting for comparing MASM to JWASM... Enjoy :-) LINK for DOS is here: >> ftp://ftp.microsoft.com/Softlib/MSLFILES/LNK563

Re: [Freedos-devel] USB driver

Hi :-) > This may be help in developping free dos usb drivers.. > http://libusb.wiki.sourceforge.net/ Talking about that, using DLL/DPMI-ish JLM drivers for JEMM386 seems to support easy use of either ASM or C, which might give interesting possibilities for example for porting the Linux Synaptic

Re: [Freedos-devel] UDMA drivers, please report usage...

Hi! > > stop top-replying, but use inline-replying from now on. > I participate in some lists where the rule is top replying... > Some people think it is better because it is faster to read bigger > quantity of messages :) I personally suggest inline replying combined with shortening quotes. Of

[Freedos-devel] boot drive partition and geometry questions

Hi, does anybody remember in which situations the MBR or whatever else calls the FreeDOS boot sector fails to pass the drive number in DL? Because at the moment, FreeDOS defaults to ignoring DL and using the value in the boot sector, unless that value is 255. I hear that only some CDROM boot BIOS

Re: [Freedos-devel] boot drive partition and geometry questions

Hi again, news about boot sector properties: - our FAT32 boot sectors always trust DL, so the code in SYS which says "if A:/B: set 0, else set 0xff" should be changed to "if A:/B: set 0, else set 0x80" to make the boot sector look nicer to disk tools, right? And makebootfat and my tool s

Re: [Freedos-devel] boot drive partition and geometry questions

Hi Alain, > > - the FAT12 / FAT16 boot sectors are too stuffed to > > check int13.8 for real geometry, but we could say > > that LBA is often supported - then we get to my > > suggestion "allow LBA even for A: if FAT16"... :-). > > When you use LBA, wrong CHS geometry is irrelevant. > > T

Re: [Freedos-devel] A call to action - FreeDOS 1.1

Hi Jim, hi everybody, > I'd like to see us continue that with a FreeDOS 1.1. I agree :-) > 1. FDUPDATE (FreeDOS Updater.) > Mateusz's excellent update utility can help to keep your system > current with the latest releases of FreeDOS packages... Even more useful is the fact that the collection

Re: [Freedos-devel] A call to action - FreeDOS 1.1

Changing the highlighting to make clear what iw2evk said and what Jim said... ;-) Some own comments: We can/did use spfdisk and xfdisk, and I agree that a separate "personal use" ISO could be made which has some packages already included which would otherwise have to be downloaded during install:

Re: [Freedos-devel] USB-Stick

Hi Jim, > > btw: I have a USB-Stick with installed kernel of FreeDOS... > > Is it possible (I think) to write an 128MB image onto a 1GB... > Yes, this is possible. You just wouldn't use the remaining space on > the USB fob. Or as you mention, you'd have to expand the partition > later using a di

Re: [Freedos-devel] A call to action - FreeDOS 1.1

Hi David, > > 3. An optional floppy-only "Base" install. > > This could be a 1.44MB emergency boot floppy image (like BALDER... > > [or] multi-floppy (3 disks?) install of everything from "Base"... > I vote for this one. I appreciate the "official" FreeDOS install CD, > and have used it lots.

Re: [Freedos-devel] A call to action - FreeDOS 1.1

Hi Marco! > - Emergency / Base floppy distribution is OK, I agree with max > 3 diskettes base system... really crazy to manage +100 floppies > distribution but if you insist... Indeed ;-) > - Version number. What version number return s Int21h Functions 30h and > 3306h? Some programs refuse t

Re: [Freedos-devel] A call to action - FreeDOS 1.1 (fwd)

I think this accidentally went to the owners instead of the list... > Date: Mon, 28 Jul 2008 11:02:04 -0430 > From: Marco Achury <[EMAIL PROTECTED]> > Subject: Re: [Freedos-devel] A call to action - FreeDOS 1.1 My comments about: For next release: - Emergency / Base floppy distribution is OK,

Re: [Freedos-devel] A call to action - FreeDOS 1.1

Hi Tom, HPA, > problem is, that the freedos stuff (both MBR and boot sector) does > not know about 'DS:SI information in memory', and ignore it It was easy to add to the FAT32 LBA boot sector, but I have not uploaded the patch as I was waiting for comments: http://pastebin.com/m1d0f7dc5 It wou

Re: [Freedos-devel] Black text on white

Hi Matt, > using black text on white backgrounds, rather than the usual reverse To do that, you can load NANSI and set your prompt to prompt $E[0;7;5m$P$G this means "send black on white ANSI escape sequence then show the current drive and path and then a > sign". It will probably not work for

Re: [Freedos-devel] Getting rid of kitten

Hi Gregory, the problem is not that KITTEN is worse than CATGETS, the problem is that your kitten seems to be too old. You say "I want to switch to catgets because catgets uses LANG and NLSPATH". That reasoning is odd if you ask me - KITTEN uses LANG and NLSPATH as well! :-) > I was playing aro

Re: [Freedos-devel] Getting rid of kitten

Hi! > I doubt Jim would mind very much. :-) He says on his page > that Kitten is not currently > maintained, so he would probably be happy for someone to take this on > and provide some updates. But that's just a guess - you might try > emailing him. ;-) Well the

Re: [Freedos-devel] Getting rid of kitten

Hi! Given your description it definitely makes sense to keep all those features in catgets - it is good that kitten is smaller than that :-) Of course for being portable to Unix, catgets can be useful. Yet I never saw any % escape in and i18n setting on a Linux yet, so most people would not even

Re: [Freedos-devel] Getting rid of kitten

Hi Gregory, > be easier if I started from scratch because I had a lot of low-hanging > fruit to throw in. Seeing that MS-DOS was vaguely Unix... Otherwise, > we would have a half-assed implementation, and nobody wants that. Well in that case you probably want a DJGPP style port of the original c

Re: [Freedos-devel] Disk size limit

Hi! Indeed, it is always a very good idea to have a look at the FAQ first when you ask a FreeDOS question which is "popular to ask" :-) > http://fd-doc.sourceforge.net/faq/cgi-bin/viewfaq.cgi?faq=Installing_FreeDOS/122 Nice FAQ but got a bit off topic ;-) Size limits are 2 gb for compatible fat

[Freedos-devel] chkdsk 0.9.1 fails for disks without subdirectories

Hi, Fritz found a bug in chkdsk 0.9.1 and it seems that the absence of subdirectories triggers the bug. Details: - at some point, CreateFastTreeMap creates a map / bitfield - CompressFastTreeMap calls ConvertTreeMaps and that collects no entries (either the initial list is empty or all entries

Re: [Freedos-devel] Minor proposal for FreeDOS 1.1

Hi! > Upon boot FreeDOS 1.0 AUTOEXEC.BAT prints "type HELP to get support..." > and "Welcome to FreeDOS". Please also echo two lines for aliases > "reboot" and "halt"... That is not needed. You can switch off a FreeDOS PC at any time without causing problems. Of course you should wait until your

Re: [Freedos-devel] Minor proposal for FreeDOS 1.1

Hi! > > That is not needed. You can switch off a FreeDOS PC at any time > OK, but how should a newbie know this? That is how DOS works. Always has. > He's probably constantly looking > for some kind of "Start" button to shutdown. ;-) Next you will ask me to add a Start menu and explorer the n

Re: [Freedos-devel] Minor proposal for FreeDOS 1.1

Hi Robert, > > > OK, but how should a newbie know this? [that you can switch off a DOS PC without doing a shutdown first] > > That is how DOS works. Always has. > *I* know, but I'm talking about a newbie trying FreeDOS > in QEMU or another VM. Why does the newbie use DOS when he has no idea wh

Re: [Freedos-devel] compiling freedos

Hi! > I can't use a batch file in my Linux environment. Therefore, I have to > write some script to compile it. I will look closer at the batch file > and see about the XCPU setting. >>> [EMAIL PROTECTED]:~/projects/dos_stuff/freedos_src/blah/kernel$ nasm >>> asmsupt.asm >>> segs.inc:34: error:

Re: [Freedos-devel] compiling freedos

Hi! >> - SVN snapshot of FreeDOS 2038 stable kernel or similar >> - NASM >> - OpenWatcom C > > Are there any c compilers available for linux that will > compile to intel realmode code? > >> - UPX (for example 2.x) All of them, including OpenWatcom, should be available for Linux, but the OpenWatc

Re: [Freedos-devel] [Freedos-user] Standart text editor for FreeDOS

Hi, as you wrote to both user and devel list, I reply to both lists, too :-). > Hi everybodu of users! I think write the one professional > text editor for the FreeDOS project for this stands standart > text editor for FreeDOS, but existed EDIT.EXE is bugged > (crashed while copying/pasting the s

Re: [Freedos-devel] The FreeDOS Bugzilla is moving

Hi! > If anyone else migrates bugs from Bugzilla into the SF Tracker, please > use the syntax/format that dos386 used. At the start of the subject > line for the bug, please put the Bugzilla bug. For example: > > "#1953 21h/29h returns 0 (valid) for all drive root names" Sounds good, thanks :-)

Re: [Freedos-devel] Question on S-ATA disks

Hi Aitor, > I've always wondered wether [S-ATA disks] are accessible through > int13h. I guess it should be so, in order to boot from them. So is > it generally true (ie. in all BIOSes, except maybe quite old ones)? Indeed... All mainboards and controller cards that I know which have S-ATA conne

Re: [Freedos-devel] FreeDOS LSM and fdupdate inventory issues

Hi everybody :-) First a correction about help.fdos.org - it does render okay in firefox, it is only outdated. Reason for the failure to display was a firefox update running exactly at the same moment... ;-). > wish to you all a great merry christmas/new year time! :) Thanks, same to you :-)

Re: [Freedos-devel] Windows NTVDM alternatives for 64-bit

Hi! > I am considering adquiring a new processor, but what can be found in > the shops is mostly x86-64. > If what I read is correct, there is no V86-mode, so there isn't NTVDM > under WIndows, and I guess that DOSEMU will not run under Linux. There is V86 mode, but it cannot be used together wi

Re: [Freedos-devel] FreeDOS LSM and fdupdate inventory issues

Hi, I would say fdpkg is the more complete package management frontend, so if you want to modify one to make the other obsolete, you should instead add fdupdate functionality to fdpkg ;-). But for me, it is fine to have both fdpkg and fdupdate. The latter could make more use of fdpkg, that would m

[Freedos-devel] bug in freedos kernel int 21.1c invalid drive handling?

Hi, I noticed that int 21 with ah=1c might return wrong values for "invalid drive", can somebody check this? For example: Is this a bug? When did we introduce it? What do other DOSes do here...? For invalid drives, I get: ds:bx=0:0 al=0 cx=400 dx=unchanged I expect: al=ff, other values are not e

Re: [Freedos-devel] bug in freedos kernel int 21.1c invalid drive handling?

Hi Laaca, thanks for checking! > ... FreeDOS, MSDOS 7.1, Windows98 and WindowsXP ... > existing 3,5 floppy disks all give the same (correct) results only > MSDOS gives wrong Total number of Sectors and Sectors per Cluster As this is MS Win9x DOS 7, the wrong number is expected... > 2) For exist

Re: [Freedos-devel] Country information in FreeDOS

Hi! > I want to ask whether is planned to fix the country infos through > functions INT21h/AX=65xxh in 1.1 release. > Now it doesn't properly work ant it is quite painful. The biggest > problem are the unsupported lower-upper case converting tables. > (f.e. INT21h/AX=6521h works badly) What else

<    5   6   7   8   9   10   11   12   13   >