Re: [Freedos-devel] IDE CDrom/Dvd

Hi Alain, > What I need is a SATA cdrom driver... Sure... UIDE, gcdrom, gxcdrom (or was it xgcdrom?), should be no problem. If you boot from it, you can also use bios as driver (plus eltorito,sys). Same for SATA DVD and BD drives, but remember that our SHSUCDX and MSCDEX both support only ISO9660

Re: [Freedos-devel] IDE CDrom/Dvd

Hi Johnson, >>Sure... UIDE, gcdrom, gxcdrom (or was it xgcdrom?), >>should be no problem. If you boot from it, you can >>also use bios as driver (plus eltorito,sys). Same >>for SATA DVD and BD drives, but remember that our >>SHSUCDX and MSCDEX both support only ISO9660, not >>UDF formatted disks

Re: [Freedos-devel] freedos emulation under 64-bit windows 7

Hi Alain, > I know thar Qemu used to work great, and it is actively developed. It > will give you a nice emulated machine with a NIC emulation. VirtualBox > should work too, and should be much more easy. Both have nice vesa graphics. > > Neither will give you shared folders, you will have to u

Re: [Freedos-devel] freedos emulation under 64-bit windows 7

Hi Jim, > I have a problem. the only OS microsoft offers now is windows 7. > machines from HP only have drivers for windows 7. I want XP. so I > am up a creek without a paddle trying to do dos development and > needing a newer intel machine with more cores (4 or 6). Does Windows 7 have the ab

Re: [Freedos-devel] freedos emulation under 64-bit windows 7

Hi Jim, > I did more research I and I heard some rumblings about windows 7's > "Windows XP Mode". it turns out it's a Windows Virtual PC that Nice :-) > emulates XP yet provides access to your devices. I don't know what > kind of filesystem access it provides. Very interesting question. > ht

Re: [Freedos-devel] IDE CDrom/Dvd

Hi Johnson, pity that Jack has so much stress with his neighbours... I think we have a misunderstanding about the drivers: UDF would be something for SHSUCDX, while AHCI would be for UIDE (SATA). I do not know whether AHCI would be useful for DOS, as SATA already is supported by UIDE anyway and

Re: [Freedos-devel] CuteMouse compilation

Hi Sergei Antonov, thanks for your mail, sounds like JWASM changed in interesting ways... Would be interesting to also know why it did that ;-) > Hi! > There are problems compiling CuteMouse 2.1 beta 4 with JWasm 2.02. > And I'd like to suggest a patch to fix them. > > The problem in the makefi

Re: [Freedos-devel] C/C++ BIOS backup

Hi! >> I read through the boot code and didn't see and specifics written >> about where the system bios is stored in memory. > > The boot code uses the software interrupts associated with the BIOS to > call BIOS functions. For example, interrupt 16h (BIOS keyboard functions) > and interrupt 13h (

Re: [Freedos-devel] ASCII to unicode table

Hi Ladislav, > I think we should discuss how to implement unicode. There already is some interface for double byte chars in DOS, which we could implement. However, it was made for Chinese as far as I remember and needed support by more drivers even if you had a DBCS-enabled DOS version. > In th

Re: [Freedos-devel] ASCII to unicode table

Hi Christian, > Just noticing that this grows quite large. If someone finds this > unbearable for this list, please speak up to let me know I should cut down > the off-topic stuff on my public mails! No problem :-) I would hope that people talk more about the "big font" approaches - Having eithe

Re: [Freedos-devel] ASCII to unicode table

Hi Christian, >> Should the translation be "accurate" or should it be "useful"? That depends a lot on which languages we are talking about. For the DISPLAYING of already existing strings such as file names on some USB stick made by somebody using Linux, MacOS or Windows, if your language is "so

Re: [Freedos-devel] ASCII to unicode table

Hi Christian, Using UTF-8 CON with a codepage based app or vice versa is worse for block graphics than just using the wrong codepage, as not only the shape but also the number of displayed characters will change: Everything outside of basic ASCII takes 2 or more bytes in UTF-8, so display on code

Re: [Freedos-devel] Edlin 2.15 is on Sourceforge!

Hi Gregory, > Yes, a new version of Freedos Edlin is on SourceForge! The version is > to fix bugs in the previous version. Nice! > FreeDOS Edlin is the standard line editor in the FreeDOS operating > system. Without it, the kernel developers would not have anything to use. Thanks, but real dev

Re: [Freedos-devel] UEFI+GPT has/is replaced/replacing BIOS?

Hi Jim, > some BIOSes have already been replaced with UEFI. AMI has been using it for > years, and now it is the only kind of "BIOS" supported in their diags suite. > ack! I wanted to have that suite someday for testing systems... > > http://www.ami.com/products/product.cfm?CatID=3&SubID=23&

Re: [Freedos-devel] freedos - is dpmi out of the question - unicode fonts

Hi Jim Michaels, > sorry - the context of using dpmi was in relation to the problem of having > only > 512K for a font. or is that a video card limitation, and you would otherwise That is a misunderstanding. You can have a hardware font with either 256 or 512 characters, not kilobytes, in VGA.

Re: [Freedos-devel] ASCII to unicode table

Hi Alex, > * in some cases best readability is the target [best user experience] > * in some cases exact string representation is the target [copy+paste, debug] > * in some other cases you simply want to be fast [viewing text/binary files] ... > for exact representations any sort of escaped chara

Re: [Freedos-devel] documentation for FreeDOS filesystem or other programming functions/interfaces?

Hi Jim, > I am possibly going to rewrite my df utility to work with freeDOS' FAT32 > filesystem (DJGPP uses int21h function 36h which is 16-bit FAT16 and 16-bit > regs). > > I cannot find any documentation on the functions that freedos uses for its > filesystem functions, like getting filesys

Re: [Freedos-devel] documentation for FreeDOS filesystem or other programming functions/interfaces?

Hi again, > I was hoping a hint might spark some documentation on the > FreeDOS filesystem API so others (like me) can do development. :-) > > you might see an increase in freedos programs if your API was documented. > who knows, maybe even commercial systems might be made or something. That is

Re: [Freedos-devel] documentation for FreeDOS filesystem or other programming functions/interfaces?

Hi Jim, > define "nonsense sector sizes" > there are new large sector drives coming out, > where 1k sectors, 2k sectors, and 4k sector sizes are not uncommon. At the moment, FreeDOS only supports 512 bytes. I know of no drives which have sectors above 8 kB sector size and there are no drives whe

Re: [Freedos-devel] documentation for FreeDOS filesystem or other programming functions/interfaces?

Hi Jim, > Eric, Leland Holliday (sp?) told me that he reworked your freetest.asm in > that > zip file and got it outputting correct numbers (the numbers were bogus) and > displaying usable output. I find it strange when somebody says my software produces "bogus" results and that person even c

[Freedos-devel] pointers to CWSDPMI (was: freedos emulation under 64-bit...)

Hi Jim, > I expect it to be able to do something to make > dpmi work. but all dpmi fails under vbox. That is not the fault of virtualbox but... > vbox said it supported dpmi, but it doesn't. It simulates a PC on which you can install any software which provides DPMI. If you do not put such so

Re: [Freedos-devel] Need help with project coordinator role

Hi! > Anyone having the super editing power needed can please update this one: > > http://sourceforge.net/apps/mediawiki/freedos/index.php?title=Unstable_Kernel_Branch Can you mail the text that you want to be added or changed to the list? I think that would enable people with super editing pow

Re: [Freedos-devel] bug in edit

Hi Jim, > if you try to highlight text by holding down the left shift key and > hitting the end key or using any of the arrow keys, the program will > not let you do anything (like save or exit). the only thing you can > do is reset the computer. it locks up. kind of. menus are still > sort o

Re: [Freedos-devel] Severe bug in kernel 2040

Hi! >> in fact the SVN kernel was fixed 10 days ago (I saw the bug somewhere >> else) but the binary at http://dosemu.org/bart/kernel.sys >> was not. I uploaded a new binary now > > Result: http://jafile.com/uploads/dos386/fdkernsh.png > > NOT fixed: >>> Kernel mirrored here: http://jafile.com

Re: [Freedos-devel] working usb drivers?

Hoi Bernd, > has anyone any experience with properly working USB drivers? Depends on what you mean with properly working ;-) As said in my previous mail, I am already happy with booting from flash USB sticks or using USB keyboards and mice using the BIOS but that is limited (no hotplugging, ofte

Re: [Freedos-devel] Stack setting in FreeDOS

Hi Ladislave / Laaca, > How I should set STACKS in CONFIG.SYS ? STACKS=0,0 works quite often but you can also try 9,256 or 9,384 or so. The highest possible setting is 64,512 which does not make much sense. Eric PS: config.txt also recommends > DOSDATA > Usage: dosdata=umb > Try to load kern

Re: [Freedos-devel] confused by NLS-settings

times. So me holding out blind > hope that FreeDOS will ever work ("for me"), in this particular > hardware area, is not going to happen. > > Eric (Auer) probably knows more (or maybe Jim Tabor). In MS DOS, it probably was something which knew the mapping of characters to bytes

Re: [Freedos-devel] confused by NLS-settings

Hi! >> COUNTRY.SYS isn't needed for DISPLAY-only stuff, e.g. codepages on >> screen, nor for KEYB either. It's only other stuff (collate >> tables, y/n), I think. Yes. And if you only need country style numbers and times, often the kernel built-in country table can be enough for you. > Most of

Re: [Freedos-devel] watcom tcp

Hi Bernd, > I'm happy with whatever I can get. My real hardware has an Nvidia > chipset network driver for which no packet drivers exist, so sticking to > virtual machines. I wonder if any PCI (or even PCI-express or onboard) > network cards still support packet drivers. You probably can stil

Re: [Freedos-devel] mTCP FTP performance (Was: watcom tcp

Hi Bernd, > My own testing sometimes involves a solid state disk, other > times a ramdrive. Bye latencies :) SSD have a quite noticeable per-write latency. The reason why you do not notice it with Windows or Linux is that those may use NCQ (queueing of concurrent disk I/O activities) and will o

Re: [Freedos-devel] confused by NLS-settings

Hi Aitor, Rugxulo, >> It still needs a lot of unnecessary UMB room free to load there, e.g. >> 64 kb or some fairly high amount. And you may even have to explicitly >> mention it. I forget exactly and always (I think) loaded it low. Well, >> I'd have to check > > If only I could assume that

Re: [Freedos-devel] confused by NLS-settings

Hi Aitor, It still needs a lot of unnecessary UMB room free to load there, e.g. 64 kb or some fairly high amount. And you may even have to explicitly mention it. I forget exactly and always (I think) loaded it low. Well, I'd have to check >>> >>> If only I could assume th

Re: [Freedos-devel] Updated INSTALL program

Hi guys, >> That message comes from the Unzip program. I got that too, during >> testing, but I rebuilt the zip file it was complaining about, and the >> error didn't reappear. I think the problem was mixed case in the zip >> package file. > > Ah, now I think I know what you mean. I think that s

Re: [Freedos-devel] Updated INSTALL program

Hi, sorry for replying the same thread twice... Thanks to Bernd for the very verbose testing and pointing out so many corner cases, impressive :-) >> * Suppose I'd be a complete newbie to DOS: how do I know what to type >> there? (a.k.a what's valid input). >> * Absolute paths required? Relative

Re: [Freedos-devel] Testing & evaluating the 1.1 release

Hi Mike, > - Are all of the binaries always put into the one "bin" dir? I expected Yes, like with Linux. Also remember that DOS often has small environment variable space, so we keep PATH short and have no "opt" or "usr local" ;-) However, FreeDOS 1.0 did have a few packages using further direc

Re: [Freedos-devel] Anybody working on a CIFS/SMB redirector?

Hi! > Anybody working on that already? I'm about to start making one myself. > Of course, any tips or ideas will be more than welcome :) As far as I remember, the ftp-client style SMBCLIENT from Samba is the only Samba thing ported to DOS yet, but that of course differs from running in the backg

Re: [Freedos-devel] confused by NLS-settings

Hi! >> Eek. Um, anybody want to tell us why 2039 has it but 2040 doesn't?? >> Certainly lacking NLSFUNC support can't be good, can it? :-/ > > 2039 was part of the UNSTABLE series, along with 2035 and 2037 and had > a lot of experimental features, but also had the unstable tag for a > reason ;-

Re: [Freedos-devel] confused by NLS-settings

Hi Eduardo, inthndlr.c int2F_12_handler should implement this... >> So in short, I do not know what broke int 2f.122b and 122d >> or whether it was removed deliberately. The changelog says: > > Definitely, they are not implemented. > Supporting country.sys and nlsfunc are completely different

[Freedos-devel] suggestion - add fdshell to freedos 1.1

Hi, some suggestion to comment on the list :-) >From marinelluccia1 tiscali.it: Hi at all, please remember to include in distro 1.1 a shell for freedos. i suggest freedos shell from Emanuele Cipolla http://fdshell.sourceforge.net/ because it's more standard doshell clone i've found. Emanuele

Re: [Freedos-devel] Updates to software list

Hi! > XMGR. HIMEMX (AFAICT) has no maintainer (and/or we really need to push > out that "jmp $+2" fix for old 386s, i.e. unofficial version 3.33, In other words, Japheth took over HIMEMX but does not add the patch? >> www.freedos.org/software/ > > To be completely honest, please don't take thi

Re: [Freedos-devel] Testing & evaluating the 1.1 release

Hi again Rugxulo, > So VMware needs PCNET? VirtualBox needs AMDPD? QEMU needs NE2000? > Anybody know BOCHS? (Yes, I'm assuming more re: emulation than real > hardware here, isn't that reasonable?) Bochs emulates a bad(?) NE2000 and a nonstandard "PCI Pseudo NIC" for which an Etherboot driver exi

Re: [Freedos-devel] EXE2BIN

Hi! > BTW, what's the goal of EDLIN ??? Never used it ... It is there for nostalgic reasons and aims to be the DOS text editor which is translated into most languages ;-) But actually even the author of MS EDLIN barely used it, so we can be happy to also have our EDIT text editor. > But please

Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released

Hi Georg, > I did a test of this CD too. First I would suggest to make an El-Torito hard > disk instead of using ISOLinux. DOS I feel should boot directly and not by > booting a version of Linux first. Isolinux is not Linux. Isolinux is a boot menu which, among other things, has the ability to

Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released

Hi Jeremy, earlier in the thread, people said it is hard to find out which drive letters are used in a fool-proof way... Also, I will not have "DOS time" for the rest of this week - so if you can come up with something magic, you are welcome. Thanks, Eric :-) >>> ... Now, when I load DOSUSB an

Re: [Freedos-devel] freedos 1.1. :F loppy distro

Hi guys, > networking, at least for me, is a nightmare. what packet driver? > how do you install it? what interrupt do you hook? is there any DOS > packet driver other than http://crynwr.com/drivers/00index.html which The Veder / Bart DOS network boot disks make that easy, by including many d

Re: [Freedos-devel] freedos 1.1. :Floppy distro

Hi Bernd, >> please remeber to create a distro with installer on floppy >> disk (1 or more 1,44 mb disk) > > * Is this intended for a networked computer or stand-alone machine? > * Is this for machines without any optical drive at all? Or machines > that have CD/DVD but don't support booting fr

Re: [Freedos-devel] Testing & evaluating the 1.1 release

Hi Jim, while I agree that more and more software is creeping into the distro if we "add all interesting things", this list is still somewhat comparable to "full 1.0". Yet already 1.0 had exactly the "creep" problem that you describe. So first we should indeed get a more "basic" 1.1 ready before

[Freedos-devel] ancient new freecom external app running bug fixed yet?

Hi! A delayed reply to "Can't Install; FreeDOS 1.1 test release #2": >>> You might need FreeCOM 0.84-pre2, I think. It has "set /e" (but needs >>> %TEMP% !!) and "cdd" works for "c:\path\blah.exe". Otherwise, you... >> I wasn't aware SET /E requires a location to write. > > I can't remember if

Re: [Freedos-devel] BIOS function support is going away for good

Hi Jims, > whitepaper from AMI on the BIOS-to-UEFI transition (very informative). > http://www.ami.com/support/downloadwp.cfm?DLFile=AMI_UEFI_Transition_Whitepaper_PUB.pdf&FileID=1387 > UEFI is taking over and slowly(?)/fastly(?) transitioning out BIOS > functionality. > This could either mean a

[Freedos-devel] 8x14 font helper for freedos 1.1 - was: EXE2BIN

Hi! While I also wonder why we wonder for so long about which DOS versions had EXE2BIN (it is small, just include it :-))...: > Other commands which were dropped by the 6.22 era, or at least relegated > to a separate download/purchase, were ASSIGN (MS-DOS 6), BACKUP (MS-DOS > 6 and PC-DOS 6, alt

Re: [Freedos-devel] ancient new freecom external app running bug fixed yet?

Hi Bernd, > * has anyone managed to get SHELLHIGH working for whichever > shell/program? Might be that FreeCOM is simply too large. And it has only very limited use, given that most of FreeCOM will swap to XMS when available anyway ;-) > * does > http://ericauer.cosmodata.virtuaserver.com.br/

[Freedos-devel] potential issues with freedos in virtual environments

Hi Bernd, Jeremy, different virtual PCs seem to have different issues, but they are all useable and I am quite sure that users run Linux and Windows inside them without real problems. Why should we have to tell DOS users that only a certain and small subset of all virtual environments can do Free

Re: [Freedos-devel] ancient new freecom external app running bug fixed yet?

Hi Rugxulo, >>> * has anyone managed to get SHELLHIGH working for whichever >>> shell/program? Might be that FreeCOM is simply too large. I find a MUCH more annoying problem with FreeCOM now: Version 0.84 pre 2 always! hangs after it beeps, but only hangs on newer hardware. Yuck! My LOCKTONE too

Re: [Freedos-devel] potential issues with freedos in virtual environments

Hi Mike, > Ultimately we're going to need to have DOS device drivers that know how > to interact with the various VMs... Only for two reasons: - the simulated hardware of the VM is "broken" so that normal drivers for the corresponding real hardware after which the simulation was modelled w

Re: [Freedos-devel] potential issues with freedos in virtual environments

Hi Eduardo, >> Even VMWare has open source mouse and X drivers around: >> >> www.vmware.com/resources/opensource/projects.html#c53533 >> >> vmmouse.c is "only" 1350 lines, the graphics driver has >> circa 250 kilobytes of sources in their 11.0.3 version... > There is also an unofficial implement

Re: [Freedos-devel] If I want to compile applications in FreeDOS, which compiler should I use?

Hi Robbie / Decheng, > don't know what's the standard (or recommended) development environment > to develop applications in FreeDOS. Would you please let me know? That depends on what sorts of applications you want to write. OpenWatcom is certainly a nice choice for C / C++, as ist NASM for Asse

Re: [Freedos-devel] Freedos and lack of drivers

Hi Bernd, >> I suppose only because no one want to start a project for free.. Linux has more support from companies, and more users. >> Linux have a developpers comunity capable to work in team, dos have "single >> volonteers" approach. > > Big corporations funding work seems to help as well :

Re: [Freedos-devel] Freedos and lack of drivers

Hi :-) > In fact , i running arachne with older pcmcia 11 mb drivers for wifi, BUT i > can't use new pcmcia card wifi > up to 54 and more MB .. Wireless is a pain in DOS, yes, sorry. > Impossible also using wifi pen See above, unfortunately. But some network cable. > or usb external device

Re: [Freedos-devel] How does the boot sector know the partition start

Hi, >> 22:23 <@aljen> you mean ds:si pointing to selected partition entry in >> mbr when jumping into vbr's code ? >> 22:23 < mmu_man> yup > > Could have told you about that. At least some MBRs leave ds:si to point to > the entry, which seems a random occurrence rather than an intentional >

Re: [Freedos-devel] How does the boot sector know the partition start

Hi Christian, >> As far as I remember, the MS DOS 7.x / Windows 9x boot >> sectors did use it and it is in fact intentional there. > > Almost entirely certain that you are wrong. > > Superficially checked both boot sectors in the MS-DOS 7.10 SYS.COM now > (one's for FAT12 and FAT16, the other

Re: [Freedos-devel] Testing for valid drives

Hi Mike, > Ulrich Hansen just reported a bug in my FTP server and I have verified > it. The technique that I use to detect if a drive is valid behaves > differently under FreeDOS than under PC DOS or DOSBox. > > Can anybody point me to documentation or code for DOS INT 21,32h ? The > functi

Re: [Freedos-devel] Issue while using free dos in XPC target stand alone application

Hi Dhanunjay, > I am new member joined recently in this group.I am new to Freedos and Even > Dos, so can I have your help Dos is a classic, so you will find a lot about it online :-) > Recently I am struck with some problem while using Freedos version 1.0 in > Xpc Target Stand alone application

Re: [Freedos-devel] Testing for valid drives

Hi Mike, here is the code of int 21 function 32 of FreeDOS: > /* Get DPB */ > case 0x32: > /* r->DL is NOT changed by MS 6.22 */ > /* INT21/32 is documented to reread the DPB */ > { > int drv = (lr.DL == 0 ||

Re: [Freedos-devel] pretty soon no more floppy controllers, only usb floppies

Hi Jim, while you can get even mainboards for socket AM3+ with floppy controllers (plus all the modern stuff as USB3) the question is whether you really NEED a floppy today > My reasons for needing a floppy are: > - development of diskwipe & mbr. it's convenient to make a floppy to > test with

Re: [Freedos-devel] Emulating Keystrokes

Hi Tom, > I am trying to emulate a keystroke programmatically under FreeDOS. > The problem is that I need to make it work for *anything* that uses > the keyboard. So far the attempts I've made (one using INT 16 with > AH=5 to store a keystroke in the keyboard buffer, and one using That sounds r

Re: [Freedos-devel] dosfsck, chkdsk, whatever and doslfn41

Hi Jim, > fixing a filesystem is an important thing... > > does anyone know if any or all of the filesystem repair programs work with > doslfn? > > or does doslfn basically not matter? LFN are stored in fragments in (short) directory entries, so old tools are supposed to at least not break t

Re: [Freedos-devel] Source Code Released: 386SWAT, QLINK, and DPMIONE

Hi Bob, > At long last, I am releasing the source code > for three of my old DOS projects: You wrote all of those? Wow! How? Why? (bow) :-) > 1. 386SWAT: A Protected Mode Debugger > svn://svn.sudleyplace.com/386swat/trunk A quite strong debugger. Can do dual-screen. Takes a bit of getting us

Re: [Freedos-devel] [Freedos-user] writing a loadable block driver for 4k-sector drive (Questions)

Hi Chris, Bertho, >> Dear List... I'm calling back with respect to the 4k-sector USB disk >> drive. I'm considering writing a loadable DOS 'block' driver for it, as >> Eric Auer suggested. > > This doesn't belong on Freedos-user then. Maybe

Re: [Freedos-devel] [Freedos-user] writing a loadable block driver for 4k-sector drive (Questions)

Hi Chris, >>> NOTE: Transformation of sector sizes is easiest in FAT32. >>> Other FAT sizes may take more effort. > You're probably referring to the root directory alignment handling, > which of course is not needed in FAT32 as its root directory is not > in a specifically reserved area. Corr

Re: [Freedos-devel] writing a loadable block driver for 4k-sector drive (Questions)

Hi! To put it in un-technical terms, I am talking about a block device driver which tells the kernel "hey here is a nice FAT partition, 512 bytes per sector" but when a DOS kernel asks the driver to read or write sectors in that partition, the driver will actually access a 4096 byte per sector di

Re: [Freedos-devel] resources, including JAVA JVM for DOS

Hi Rugxulo, >> pardon me, SIG-M library was for CP/M >> http://www.retroarchive.org/cpm/cdrom/SIMTEL/SIGM/ ... >> SIMTEL is the library you are looking for. simtel has an msdos section. >> http://www.lanet.lv/simtel.net/msdos/ >> there are multiple mirrors. just google simtel msdos. > > Yes,

Re: [Freedos-devel] DOS Development Idea

Hi Martin, > The main aim behind the idea is to make a DOS system that is comparable > to Linux, Windows or any other of the 100+ OS's out their while still > using the DOS Kernel at the core, which if my idea is viable would allow > DOS to be 16, 32 & 64-bit compaitable, seems like a crazy idea

Re: [Freedos-devel] Minimalist linux.

Hi Bernd, > http://lennartb.home.xs4all.nl/linux.html > > has plenty of pointers for creating your own minimalist Linux bootdisk. > Personally, I'm still looking for a minimalistic Linux distro that > contains GCC. Somewhere around 500MB to 1GB maximum. Rugxulo probably knows one :-) > If you h

Re: [Freedos-devel] Minimalist linux.

Hi Rugxulo, > Almost definitely doesn't fit on floppy anymore, not since 2.2.0 or > such. Even 2.4.x branch is basically (officially?) dead now. Yes a modern Linux kernel and initrd (boot time ramdisk with basic tools and drivers loaded before the harddisk is accessed further) can easily be 5 an

Re: [Freedos-devel] DOS Development Idea

Hi! > something fast, clean, simple, able to access loads of memory, and > still (mostly) use dos development tools, would be a great thing for > a lot of embeded developers if nothing else. Question to those who also know more embedded operating systems: How would the suggested variant of D

Re: [Freedos-devel] DOS Development Idea

Hi Martin, > On an expansion of before. Just like BSD and Linux are relatives of > each other and just as capable of each other, why shouldn't DOS be > able to be just as capable as its relative Windows? BSD and Linux have a culture of source-based software, often even open source. With acceptab

Re: [Freedos-devel] bug in mode

Hi! > for some reason, there is a bug... requires these 2 lines to get into 132x50 That might be because e.g. DOSEMU does not have a ready-made text mode for 132x50. It offers 80x60 132x25 132x43 132x60, but not 132x50, and 132x43 seems to be broken font-wise? In any case, you can say "mode con

Re: [Freedos-devel] DOS Development Idea

Hi! > Is there a list of applications, currently available for DOS > only, that it may make sense to reimplement for contemporary > free software systems? > > For me, it's probably only certain games. (In particular, those > still distributed via http://gog.com/.)

Re: [Freedos-devel] KEYB BUG

Hi Tom, >KEYB.EXE 11,446 06-24-12 > > leaves, when running, a huge memory hole. at least with only HIMEM > loaded. note the HUGE memory hole behind KEYB As far as I remember, KEYB and DISPLAY did this deliberately: Instead of reserving only a small buffer statically and the rest dynamically

Re: [Freedos-devel] cutemouse behaviour API fn 10h

Hi Rugxulo, Eric, >Don't know, you'd have to specifically ask Eric Auer or Daniel > Nagy. If you want to hack up a forked version with your changes... Actually I was hoping for some other comments and references here. >> While reviewing the mouse programming API und

Re: [Freedos-devel] Please add the features to Bloček and Kašmár.

Hi Tae Wong, > Bloček needs to be updated with keyboard for Hungarian and Polish. > Kašmár does not support editing files that contain the .ch file format. What is a ch file format and what is Kasmar? I remember that Blocek is a DOS text editor with graphical fonts, so you can edit Unicode text

Re: [Freedos-devel] contributing to FreeDOS

Hi :-) > http://falco1.heliohost.org/softwares.html#dos > > Most of them mainly help the old DOS environment to cooperate better > with modern processors (PWR or LOWP) or just help testing in some way > (TSCDOS, CACHE). The Turion / Athlon64 mobile / Sempron / ... and Phenom tools to select low

[Freedos-devel] Lua testing and versions for DOS

Hi FreeDOS devel people, as I was wondering "how small is that popular newish scriptish language, Lua, in DOS?" recently, Rugxulo put together a few files. Maybe you want to test :-) Old Lua 4.0 in a 16 bit version: www.ibiblio.org/pub/micro/pc-stuff/freedos/files/devel/lua/4.0/ A test suite,

[Freedos-devel] new version 2.6 of Bochs available

Hi all, Bochs 2.6 is available since 2012-09-03: http://bochs.svn.sourceforge.net/viewvc/bochs/tags/REL_2_6_FINAL/bochs/CHANGES You can download Linux and Windows versions and sources here: http://sourceforge.net/projects/bochs/files/bochs/2.6/ Things which are still buggy can be reported her

Re: [Freedos-devel] Question about of source code FreeDos

Hi, to give another "large point of view" answer: > Hi, I'm Sebastien Favier, of France > For a large project for the creation of a Kernel > because i would remplace msdos per freedos > I have a question about the source code FreeDos > the source code is it completely free? > what are the limitati

Re: [Freedos-devel] Cutemouse build environment

Hi John, > Need to know the version of make and link used to build Cute Mouse v2.1 beta > 4. Cutemouse originally builds with tasm, tcc, tlink and the make of Turbo C and is compressed with UPX. However, only C is only used for the mousetst utility, not for the driver itself and not for the com

Re: [Freedos-devel] FreeDOS development sense

Hi Jevgenij :-) Indeed very interesting download stats, Jim, thanks! > Please add on the FreeDOS website in the page of download the form is > required to fill before download the FreeDOS with questions about who > and for what who download the FreeDOS for collect more complete > information abo

Re: [Freedos-devel] FreeDOS development sense

Hi Jevgenij, > I do not use Borland or other proprietary toolkit - I use my own > written window toolkit. Cool :-) >>> GENTEXT - multiwindow text editor, more stable but standard EDIT. >> Actually FreeDOS EDIT already is multiwindow, but limited >> in file size. For big files, an interesting ed

Re: [Freedos-devel] Can start a 16Bit program in 32 with Freedos ?!

Hi! I think some people (CWSDPMI, Japheth, ...) have done some experiments with tricks to use more than 4 GB RAM in DPMI, but you can only use 3-4 GB in one block that way. If your goal is (easier) to get from 640 kB to 4 GB, you can use a number of methods: You can use (DPMI) DOS extenders, whic

Re: [Freedos-devel] I found limitation bugs!

Hi! MEM tells you how much RAM you have but DF tells you how much DISK space you have, two different things. If DF does not support FAT32, it can have a limitation to displaying not more than 2 GB or 4 GB of disk space, but that should be relatively easy to fix. Please provide a link to DF and to

Re: [Freedos-devel] FreeDOS limits! and FDNPKG v0.93a released

Hi sparky, (PS: Please decide on which of the 3 lists this should be discussed) > FreeDOS's mem program output only 4 GB of detected memory out of the > machine's total 16 GB Dose this mean FreeDOS can only detect 4GB > maximum? This is NOT related to the kernel: MEM only reports what EMS,

Re: [Freedos-devel] FreeDOS limits! and FDNPKG v0.93a released

Hi Jim, > unfortunately, freedos doesn't support anything over 8GB Please explain. It supports up to 2 TB with LBA. Maybe you mean the size of individual files, limited to 2 or 4 GB. > on x64 and maybe i386, even if support for BIOS should go away and > only UEFI and x64 remains You can use DO

[Freedos-devel] Fwd: SourceForge Project Upgrade Notification

Hi! This is probably interesting for all developers :-) > Your code repository in upgraded project fdos is now ready for use. > > Old repository url: http://fdos.svn.sourceforge.net/svnroot/fdos > > New repository checkout command: svn checkout > --username=YOURSOURCEFORGENAME > svn+ssh://yours

Re: [Freedos-devel] Fwd: SourceForge Project Upgrade Notification

Hi Jim, best wishes for your studies :-) > I don't think I understand what "fdos" is. The project page > describes it as "FreeDos > Distribution Of Sorts". Is this a different SourceForge project from > the regular "FreeDOS"

Re: [Freedos-devel] RAM disk and task switching

Hi Charles, you have so much RAM on a modern machine, you can just as well allocate XMS or other memory whenever you feel like swapping out a task :-) No need to use a file on a ramdisk. Also, the latter has the extra complexity that you need DOS to access that disk, which already needs stabiliza

Re: [Freedos-devel] freedos.img - spoke too soon

Hi Charles, > Hate to complain, but, you people are letting this initiative get away > from you like what happened to LINUX. Too many bits and pieces > cobbled together from here and there without the code writers knowing > enough about what the bits and pieces all do. And too many > distributi

Re: [Freedos-devel] Fwd: format error in FAT32 kernel

Hi Roy, > Forwarded from sourceforge bug tracker: > https://sourceforge.net/p/freedos/bugs/115/ > > Boot FAT32 kernel (ex. ke2041_86f32) from A: and "format b: /u", then an > error occurs. Does this only happen with the FAT32 kernel? Does this only happen with a FreeDOS kernel? Are your A:

Re: [Freedos-devel] Fwd: format error in FAT32 kernel

Hi 大内義隆, Roy, > I try some case. Thanks :-) > case1. DR-DOS 7.01.07 WIP (24.11.2004) > -> no problem > case2. DR-DOS 8.0 > -> no problem > case3. Windows ME boot disk > -> no problem All with the same FreeDOS FORMAT tool? Then it might indeed be kernel-related. >> If you do DIR B: before f

Re: [Freedos-devel] Do not use any code from ms-dos release!

Hi CHarles, > The big problem for me as an app developer in bioinformatics is > finding an OS worth investing in. For the time being I'm using Win XP > SP3, but not really happy with the choice. I need something fairly > mainstream so potential users will be able to easily download and try > it

Re: [Freedos-devel] Do not use any code from ms-dos release!

Hi Travis, > I'm still wondering why there's nothing to take advantage of these > multi-core processors to allow someone to run multiple oses > simultaneously using one core for each os. No reason you can't use > task switching, and run dos, windows, linux, and others all on the > same m

  1   2   3   4   5   6   7   8   9   10   >