Re: [Freedos-user] FYI: I'm speaking at FOSDEM'21 this weekend
As a former FOSDEM presenter I wish you good luck Jim, also getting up early this Sunday :-) ! I have a little scheduling conflict with the HPC devroom (https://fosdem.org/2021/schedule/track/hpc_big_data_and_data_science/) that I'm helping to organize but I'll have a look at the recording for sure (in fact all talks are pre-recorded, to make sure everything goes smoothly). Bart ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FOSDEM Retrocomputing DevRoom CfP
My talk was accepted so I'll be presenting in 4 weeks: https://fosdem.org/2018/schedule/event/dosemu_and_freedos_past_present_future/ Bart On 1 December 2017 at 08:56, Bart Oldeman wrote: > Hi guys, > > (still lurking but not a lot of time... over the past years) > > I'll be at FOSDEM for work related purposes (HPC devroom). Since I'll > be there anyway I submitted a proposal for Retrocomputing to talk > about DOSEMU and FreeDOS. > One exciting development that somehow was missed is that there is > finally a GCC port with support for far pointers > (https://github.com/tkchia/gcc-ia16/). I have been able to compile the > FD kernel with it and run the result, though it needs various changes. > I would have never guessed in 2000 that this would be possible in 2017! > > I'll be in touch with you Jim if my proposal gets accepted; I am not > sure if for retrocomputing the deadline was extended or not (for the > HPC devroom it is today). > > Bart -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FOSDEM Retrocomputing DevRoom CfP
Hi guys, (still lurking but not a lot of time... over the past years) I'll be at FOSDEM for work related purposes (HPC devroom). Since I'll be there anyway I submitted a proposal for Retrocomputing to talk about DOSEMU and FreeDOS. One exciting development that somehow was missed is that there is finally a GCC port with support for far pointers (https://github.com/tkchia/gcc-ia16/). I have been able to compile the FD kernel with it and run the result, though it needs various changes. I would have never guessed in 2000 that this would be possible in 2017! I'll be in touch with you Jim if my proposal gets accepted; I am not sure if for retrocomputing the deadline was extended or not (for the HPC devroom it is today). Bart -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Only C: can be used in config.sys?
Hi, > Does FreeDOS only accept drivers located on C: so it rejects to load from F: ? this is a known bug in the FreeDOS 1.0 kernel. It's been fixed in newer kernels (from July 21 2007, and newer, e.g. 2038, 2039). Bart -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] [Dosemu-devel] window behavior dosemu/freedos on Ubuntu Linux
First, there exist workarounds: either put $_speaker="" in ~/.dosemurc or if you *want* beeps in DOSEMU, e.g. for very old DOS games, you should not change ~/.dosemurc but instead configure your Linux window manager, see http://tombuntu.com/index.php/2008/08/04/replace-the-system-beep-with-a-compiz-effect/ for hints. That said DOSEMU-in-development now has the issue fixed (SVN -r1900). 2009/7/15 Eric Auer : > I experience the same, but am not sure what causes it. > Seems to be related to the "visual bell" and the fact > that dosemu can use terminal ESC sequences for sound > output whenever the emulated "internal PC speaker" is > touched. In the case of X they are not terminal sequences but X calls but those can also be turned visual. > so a > more elegant patch would modify do_sound to make operation > of the speaker gate "lazy". In other words, to make it only > switch the speaker on / off if the speaker was not already > in the same state at that moment :-). I wonder than why you only write out the less elegant patch? It would be easier to follow you if you would write your emails after you've drawn a conclusion instead of during the figuring-out stage -- we don't want to know about a "suggested patch" that you later say has a more elegant alternative. My patch just avoids calling the speaker-off code at a lower level if the speaker is already off, in src/base/speaker/speaker.c. Bart -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Incompatibility with EMSDSK
2009/6/21 jasse...@itelefonica.com.br > I only tested it with 4364KB, which is the same size I use under > DR/MS DOS. This is just a value I found to work comfortably for > all my ordinary applications. I may try other values if you think > this is important. BTW, I have 16 MB total memory in this machine. I see no problem here: C:\>emsdsk 4364 EMSDSK driver not loaded. Want to load it (y/n) ? *** EMS RAMdisk v1.9I (FU - 08/98): Installed as drive F:. C:\>dir f: Volume in drive F is MS-RAMDRIVE File not found. C:\>copy config.sys f: config.sys => f:config.sys C:\>dir f: Volume in drive F is MS-RAMDRIVE Directory of F:\ CONFIG SYS 469 16-06-09 17:45 1 file(s) 469 bytes 0 dir(s) 4.456.448 bytes free What are you seeing? How do you load emsdsk? What is a minimal config.sys/autoexec.bat that exposes the problem? In other words, how can others reproduce your problem? Bart -- Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Fwd: exFAT32
On 10/16/07, Florian Xaver <[EMAIL PROTECTED]> wrote: > Found it at http://en.wikipedia.org/wiki/Fat32#exFAT. > Would it be much work to add support of it at FreeDOS? Yes, much work, even if somebody finds specifications and it turns out to be very similar to FAT32 (than it might be doable though for someone with enough time). But I cannot find any details right now, so it would have to be reverse engineered which is even more work. 64-bit file sizes are quite a stretch for a 16bit OS though! So I doubt it, but of course you are free to try yourself. Bart - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Problem to unzip in DOSEMU 1.4
On 7/23/07, Eric Auer <[EMAIL PROTECTED]> wrote: > > Hi Florian, > > > It (*) is NOT a problem of the "redirected linux directory..." > [ (*) the problem with unzipping directories in DOSEMU 1.4 and older ] > > Strange! > > > But you will find the message, at DOSEMU list > > There were no messages on this list after 24 May...? 18 July. Although I've had hardly any time for DOSEMU or FreeDOS since the beginning of June. The message about PKZIP is here: http://www.mail-archive.com/[EMAIL PROTECTED]/msg04541.html Bart - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.1...
On 6/17/07, Japheth <[EMAIL PROTECTED]> wrote: > > As far as Jemm is concerned, only the kernel has to restore "its" vectors. > Vectors changed by drivers/tsrs which are loaded after Jemm can be ignored, > because Jemm saves the current state of the IVT on init and restores it when > an int 19h is called. I just ported (almost copy&paste) the code straight from your driver. The hard part was fiddling around with the various segments, groups etc that are used to force the data at 70:xx. Eric remarked that before restoring interrupt vectors the code should probably do a CLI which your code does not do either. I'm suddenly worried about the IRQ vectors too, as they are redirected if STACKS>0. Might look into that later... Bart - 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. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Boot sector not standard? [Solved]
On 10/27/06, Marton <[EMAIL PROTECTED]> wrote: > Any chances of a permanent fix or it is actually hard to implement? Something like this: --- initdisk.c.old 2006-10-30 00:30:02.0 + +++ initdisk.c 2006-10-30 00:32:31.0 + @@ -995,7 +995,9 @@ for (num_retries = 0; num_retries < N_RETRY; num_retries++) { regs.d.b.l = drive | 0x80; -if (driveParam->descflags & DF_LBA) +LBA_to_CHS(&chs, LBA_address, driveParam); +if ((driveParam->descflags & DF_LBA) && +(InitKernelConfig.ForceLBA || ExtLBAForce || chs.Cylinder > 1023)) { dap.number_of_blocks = 1; dap.buffer_address = buffer; @@ -1009,7 +1011,6 @@ } else { /* transfer data, using old bios functions */ - LBA_to_CHS(&chs, LBA_address, driveParam); /* avoid overflow at end of track */ if (chs.Cylinder > 1023) - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Russian by UTF-8 in FreeDOS?
Hi, On Wed, 5 Jul 2006, Henrique Peron wrote: > DISPLAY CON=(,,3) > MODE CON CODEPAGE PREPARE=((858,852) C:\FDOS\BIN\EGA.CPX) > MODE CON CODEPAGE PREPARE=((,,808) C:\FDOS\BIN\EGA3.CPX) > > Then, you'll type MODE CON CODEPAGE SELECT=858 for french or 852 for polish > or 808 for russian. UTF-8 is codepage 65001 but I doubt that'll work. Maybe, once somebody implements CP932 and other double-byte character sets (DBCS) support, then UTF-8 will be easier. But displaying all those characters requires graphics mode, text mode won't do. It just needs some serious developer's interest from East Asia to get that working. As for converting, and then displaying the result in your favourite DOS character set, recode will do; search for rcode35b.zip in the v2gnu directory of your local DJGPP mirror. With the DJGPP port of GNU Emacs you may also be able to view and edit UTF-8 files. Bart Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] C compilers.
On Wed, 24 May 2006, Arkady V.Belousov wrote: Wesley Parish wrote: Didn't someone recently abstract all the DOS executables and put them up somewhere? Sorry for the garbage. In the OpenWatcom site, I only find the installer for windows. No DOS version. I don't think this is hard - you may list separate .zip-s from older versions and makes similar archives with same files. I suggest, I may do this task. Issue is where and how to place these archives. Most ideal way - place on openwatcom.org site. I can send you the old manifest (list of files) files that were used to produce the .zips in the older versions if you don't have them in case that helps. Just let me know. Bart --- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Re: Sorry Jack, but you need to "examine"
On Fri, 19 May 2006, Johnson Lam wrote: Eric, as Jack did not want to reveal WHY qhimem is, in his opinion, better than freedos himem, Bart HAD to disassemble qhimem to TRY to find out about the things which Jack did not want to reveal. Of course it is Sincerly I beg you not to upset Jack anymore, otherwise everyone will have no more QHIMEM/QDMA/QCDROM to use. Guys, there is no "HAVE TO" here, but curiosity killed the cat. And I "was welcome to", so could not upset anyone ;) thank you, and please don't take this all *too* seriously Bart --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] (fwd) FDXMS Sources.
On Wed, 10 May 2006, Johnson Lam wrote: Quote a few lines from his email: = I did not "model" QHIMEM after Microsoft HIMEM V2.03, like you know. QHIMEM's source or binary files are very different from V2.03 HIMEM. Disassemblies may only confuse folks. But they are welcome to try. = Hey, I always like a challenge, so if I was welcome to try, I disassembled a bit. Some observations: QHIMEM is indeed not modelled after MS HIMEM. You can see that the MS source has been referenced, e.g. in the algorithm for allocating an EMB (very similar) and how to decide when to use PS/2 A20 switching (the "MCA" bit for int15/ah=c0). It certainly doesn't have a "clean-room" feel (purely coded from XMS spec), but that may not be necessary. Just like FD-HIMEM and FDXMS it either uses INT15/AH=87, or temporarily switches to protected mode (almost the same GDT setup) to copy. However, and that is what the interrupt stuff is all about, it copies in chunks of 8K: for every 8K it returns to real mode, STI's, CLI's and gets back into protected mode. QHIMEM, unlike MS-HIMEM, does not use flat real mode (aka unreal mode). I'm not sure where Jack got the 8K from -- maybe the timing on the slowest possible machine (386SX 16MHz) has something to do with it. The value for int15/87 is 1K, where FD-HIMEM and FDXMS use 8K chunks. QHIMEM uses a few tricks to save memory, e.g.: * the KBD A20 switching code is overwritten with PS/2 A20 switching code when necessary * eax is initialized to 0 and is exploited that way (saves 1-3 bytes in various asm instructions, versus an immediate 0 operand) * comparisons versus number of handles are patched in the code to save on an extra variable in the data segment * the XMS spec requires that " In order to maintain compatibility with existing device drivers, DOS XMS drivers must not hook INT 15h until the first non-Version Number call to the control function is made." the "hook int15" code + various other delayed init code is copied to (hardcoded) segment 0x7030, and called from there so it does not stay resident. This is somewhat risky: it relies on the fact that the DOS kernel does not overwrite anything there, and will make XMS calls itself. That usually happens, or QHIMEM would crash. Segment 7030 is also used for communication between QHMBOOT and QHIMEM. That's the gist of it, at least from my mileage. Bart --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] (fwd) FDXMS Sources.
On Tue, 9 May 2006, Johnson Lam wrote: Originally he found 4 bugs, this is one of them. Ok, in that case, what is the bugzilla bug number? I think people are wondering here what this stuff is all about, without any real (reproduceable) technical details given. All we can see is that someone wrote a closed-source driver that allegedly fixes a problem that I can't find in bugzilla, and now nobody knows what it's all about. Well --- obviously, if you have a lot of time you can disassemble qhimem.sys, diff it with the MS reference source code and try to make sense of it. But that's a bit of a waste of time with no developer benefit, ain't it? Bart --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] (fwd) FDXMS Sources.
On Tue, 9 May 2006, Robert Riebisch wrote: Yes. ftp://ftp.microsoft.com/softlib/mslfiles/XMS.EXE Just google a bit: deja vu: http://freedos.sourceforge.net/freedos/news/press/2000-himem.txt and the consensus was " ... Therefore you cannot derive any rights from it to change or modify it or re-use portions of it within FreeDOS tools. " note that the BSD license explicitly allows modification (provided that...) and nothing is written about that in the MS source code, just that the *specification* is in the public domain. (BTW I don't think offending people really helps, and as far as Eric is concerned, I've never seen him doing it consciously (certainly no CAPITAL name calling like the posts here), but I have been annoyed by Eric's emails from time to time, simply because he did not do his homework (IMHO) and he could save a lot of people's time by spending time testing all the suggestions made instead of typing long emails -- but I think the right strategy is to not feel offended or take things personally but just to ignore, life is too short to worry about these things -- but anyway enough said about this). Bart --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Maximum path and filename length for FreeDOS?
On Tue, 3 Jan 2006, Andre Tertling wrote: Blair Campbell wrote: obvious question. What is the maximum path and/or filename length under FreeDOS? I think that it's 2 + 80 + 8 + 3, but I could be wrong. This may be true, but command lines are IIRC limited to 80 chars. It may be possible to extend that to the 93 chars you mentioned by using environment variables, but I'm not sure about that. (...and I don't feel like trying, might break other things...) In DOS command lines are restricted to 126 bytes for the options. (the PSP has room for 128 characters, of which one is a length byte and one an end byte (0Dh)) Windows 95 and 4DOS extend this using the environment. Paths are 79 bytes max. The limiting factor comes from the get directory function, which is passed a 64 byte buffer for the directory name excluding c:\ but including an ending 0. So we get C:\ 3 directory name 63 \ 1 filename 8 . 1 ext 3 __ + 79 a terminating 0 gives the infamous limit of 80. Bart --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] EMM386 2.08/Nomyso 2.0 Available
On Mon, 28 Nov 2005, Blair Campbell wrote: PS: If the C is ever to be compiled with Watcom C, as Bernd suggested, the global functions in the asm would need to have a _ in front instead of behind, as this is (for some weird reason) the way OpenWatcom does things. I think you have this the wrong way around. The reason is not so weird, as it avoids severe bugs interfacing. The _ is put the other way because the calling convention is different, so just changing the _ isn't enough, you also need to convert stack to register parameter passing. If you want a _ in front with OW, and stack calling conventions, like Turbo C, all you need to do is to decorate the function with _cdecl in the C or H file. Bart --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeCOM ^Z in copy con indeed broken
On Thu, 20 Oct 2005, Eric Auer wrote: Hi, odd, while I remembered ^Z to be working, it actually is broken when testing in Dosemu and Bochs, with FreeCOM versions 0.82pl1, 0.82pl3 and 0.84-pre. This really should not happen :-(. Copy con test.txt type something ^Z --> does not end the copy con (^Z at start of line should do that!). Hi Eric, this would be a kernel problem, not a freecom problem. I don't see it, with a quick test (of the stable cvs branch kernel). Bart --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Re: Re: GRUB for DOS How-To
On Fri, 31 Dec 2004, Michael Devore wrote: > At 01:22 AM 12/31/2004 -0800, 16BIT wrote: > > >Grub for DOS prints the following error message if I try and run it with > >FreeDOS: > > > >- > > > >Sorry! Currently supported DOS versions are: MS-DOS 3.30 and later; > >FreeDOS kernel build 2029 and, hopefully, 2032 and later. > > > >- > > > >A rather interesting error message don't you think? > > What do you bet that it's looking for the original FreeDOS versioning which > was recently changed to work around the Borland RTM bug? $100 ;-) The GRUB code doesn't use int21/ah=30 at all. An extract from the patch in grub013.zip is below. It's far nastier. Very nasty. It's code that assumes that the binary code of FD-kernel's IRQ stack handling never changes, noone uses STACKS=0, and MS HIMEM may be loaded (int15 hooked by himem.exe not considered apparently). Note the use of the magic 0x3086 number... Your dog may eat this code for lunch. It seems to need this dirty technique to try to restore the BIOS IRQ vectors to their original values. Booting with STACKS=0 without HIMEM could avoid this hackery. (another note: remember that AT&T syntax reverses wrt Intel syntax for assembly). + /* check for FreeDOS (build 2029+) */ + + /* +* MS himem.sys takes over int 15, so check for the case. +*/ + + xorw%ax, %ax + movw%ax, %es + movw%ax, %ds + movw$0x0054, %di + movl(%di), %eax /* int 15 vector in table */ + cmpl$0xc000, %eax /* is it a valid BIOS vector? */ + jnb 1f /* yes, do nothing */ + movw$0x3086, %si/* no, take one from himem */ + movl(%si), %eax + cmpl$0xe000, %eax /* is it a system BIOS vector? */ + jb failed_check_freedos/* no, do not continue */ +1: /* yes, continue */ + xorw%ax, %ax + movw%ax, %ds + movw$0x0020, %si/* DS:SI points to int 08 */ + lodsl + movl%eax, %ebx + movl%eax, %edx + movw$7, %cx +1: + lodsl + addw$6, %bx + jc failed_check_freedos (snip) Bart --- 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 -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] new
On Thu, 21 Oct 2004 [EMAIL PROTECTED] wrote: > I tried to fix the problem by changing the $_hogthreshold parameter in > dosemu.conf : neither value that I tried changed anything (0, 1 and 10). $_hogthreshold = (0) causes no idling at all, so dosemu will use 100% cpu time. with $_hogthreshold = (1) it tries to sleep as much as possible (slowest) anything higher than 1 makes it sleep a little less, but still sleeps more than 0. Can you try DOSEMU 1.2.1? There are some known issues in this area with 1.2.2 now, so I'd like to know if it's a regression. In general freedos-users isn't a DOSEMU forum, of course FreeDOS specific issues are on-topic but this isn't (unless if you boot MSDOS in DOSEMU things are different). The dosemu users list is [EMAIL PROTECTED] You can also report at the sourceforge bugtracker at http://www.dosemu.org. Bart --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] 4DOS free now!
On Thu, 26 Aug 2004, Jim Hall wrote: > Bart Oldeman wrote: > > > > Probably best to be quiet (also polite) now. It's extremely likely to > > happen according to Mike Bessy and he was affiliated with JP Software > > up to a couple weeks ago. Any more requests or questions just take time > > away from the person at the other end at this point. > > > > See > > http://groups.google.com/groups?selm=_zeXc.540%24lV5.320%40fe25.usenetserver.com > > Interesting. I hadn't seen that one, since I don't read that ng. I'll > sit tight for now, and watch what happens. Well after all it's not going to happen very soon, but as soon as 4NT is far enough ahead of 4DOS and 4NT specific code is removed there may be a possibility. http://email.sparklist.com/cgi-bin/lyris.pl?visit=jpsoft_support click "read messages", then scroll down to Matthias Paul and Rex Conn's answer. Bart --- 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 Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] 4DOS free now!
On Thu, 26 Aug 2004, Jim Hall wrote: > Yes, this is quite possible. I've emailed JP Software in the past to > (politely) ask that they release the source code to 4DOS, and I intend > to do so again. I would encourage others to do so, as well. However, > please remember to follow the rules of good FreeDOS advocacy: > > http://sourceforge.net/docman/display_doc.php?docid=23406&group_id=18412 > > > Above all: be polite. Probably best to be quiet (also polite) now. It's extremely likely to happen according to Mike Bessy and he was affiliated with JP Software up to a couple weeks ago. Any more requests or questions just take time away from the person at the other end at this point. See http://groups.google.com/groups?selm=_zeXc.540%24lV5.320%40fe25.usenetserver.com Bart --- 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 Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] 4DOS free now!
On Thu, 26 Aug 2004, Luchezar Georgiev wrote: > The next logical step will be releasing the source code :) This is not as improbable as it may seem (unlike what Bernd says). It happened with 4OS2, well Matthias Paul already tried as you can see from the forum at JPSoft. > I attach the license under which 4DOS is now distributed. > Does it allow its inclusion in the FreeDOS distributions? Yes, it's a very liberal license. Also FreeDOS does have precedent in distributing binary only software, see arrow-asm in "lang", but not in "base". Even then FreeCOM has some advantages, being a lot smaller, while still having nice features such as command line editing and tab completion. The license is very similar to www.w3.org/Consortium/Legal/copyright-software The two sections that are added can be found (in slightly edited form) in the GPL. If this were a source license it would be a BSD-ish subset (possibly even GPL-compatible but IANAL so can't be sure). Bart --- 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 Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] EMM386.exe
On Mon, 17 May 2004, Michael Devore wrote: > I have no idea what Eudora is doing, the e-mails look okay to me going > out with plain style. By the way, your original quote-back was not > wrapped and indented, and Bernd's was, so what does that mean? There is something strange here. Eudora seem to be one of the main supporters of "format=flowed". http://www.eudora.com/techsupport/kb/1626hq.html Yet Bernds mail uses according to the headers Content-Type: text/plain; charset=us-ascii; format=flowed Mozilla Thunderbird 0.6 (Windows/20040501) but Michaels mail: Content-Type: text/plain; charset="us-ascii" QUALCOMM Windows Eudora Version 5.1 -- note the "format=flowed" is missing! (us-ascii becomes iso-8859-1 when replying to Arkady in a hopeless attempt to deal with quoted cyrillic characters but that's a different story...) Maybe all that's necessary is to change a few Eudora settings to convince it to use "format=flowed" in its headers. Happily for me "pine" has ^J to fix up any messed up quotes... And no matter what other mailer I tried (even mutt) my fingers always seem to want pine again. Bart p.s. to others, please don't ask me when I'm going to do this or that -- as I said I'm not even sure if there'll be a new FD kernel release or even basic CVS updates before July -- most of the components of my freedos test box are on their way to a container ship due to arrive mid-July... --- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Using the internet with FreeDOS made easy
On Sun, 9 May 2004, Eric Auer wrote: > Hi, this is a fun followup to the problems of 8.3 names and > FreeDOS internet connection. [ that GPL requires 8.3 is bullshit indeed. Though it talks about equivalent access to the source code. If someone who can access the binary can't access the source code, only then you have a problem, but as most released zips have both source code and binary there is usually no issue. Anyway without the OP explaining his claim this is just guessing ]. > I am writing this mail in DOS :-)). > SSH2DOS -t vt100 -v -n -g username servername err, you are using your DOS PC as a vt100 terminal to a Unix-style server. But then what does DOS know about writing emails... > Another good point with FreeDOS + SSH2DOS is that my disk just went > to sleep :-). In Linux, it is never really idle. The bad point is that > I cannot switch to another window or do anything else than SSHing > while I am in this SSH2 session in FreeDOS... run dosemu remotely (perhaps using "-dumb") and GNU screen or something like that and you can switch between multiple DOS programs and Linux programs as often as you like :) Bart --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] freedos in french
On Mon, 3 May 2004, jeff dyn wrote: > I use dosemu-1.1.1-3.i386.rpm under linux e-smith 6, and i find a > freedos who works in french for this system i try with > dosemu-freedos-1.1.1-3.i386.rpm but i cant type "é" or "è" caracteres i DOSEMU 1.1.1-3 is really old now, and the freedos in the rpm you mention as well: please try 1.2.1, see www.dosemu.org. In most of these the accents should work out-of-the-box with 1.2.1. If not then it really depends where you run dosemu: using xdosemu, in an xterm or via telnet/ssh, or on the Linux console and I can only tell how to solve it if you say where it goes wrong. Bart --- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id149&alloc_id66&op=click ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS FAT32 support state (was: FreeDOS beta9 release candidate 5)
On Mon, 3 May 2004, Eric Auer wrote: > SYS, by the way, hardcodes BIOS drive number to 0x80 for FAT32 boot. Bad. Hi Eric, where does SYS do that? I can't find it: as far as I can see the boot sectors use DL for FAT32 partitions. Bart --- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] edit problem (fwd)
Hi Claudia, forwarding this to Freedos-user -- I don't think Eric Auer is on linux-msdos. Bart -- Forwarded message -- To: DOSemu Mailingliste <[EMAIL PROTECTED]> Hi Bart, hi all. I wonder if you can make it possible to read a file bigger than 64 kB with the FreeDOS edit. In MSDOS 7.1 it is no problem. It is at the moment the only flaw with our clipper/foxpro programm running in DOSemu with FreeDOS. Regards Claudia --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Installing symbios SCSI drivers
On Mon, 8 Mar 2004, Julien Pierre wrote: > A lot of DOS installation programs modify > C:\CONFIG.SYS and C:\AUTOEXEC.BAT . How do you deal > with that ? I don't like the fact that those files are > ignored. > Maybe you could do some sort of chaining. Process > FDCONFIG.SYS first, CONFIG.SYS next. I tend to think of fdconfig.sys as an alternative to config.sys if you want to dual boot multiple DOSes from C: -- for instance Windows 98 and FreeDOS on the same hard disk partition. DRDOS can do the same with dconfig.sys. Processing both defeats this purpose. However the primary configuration file is config.sys. If the installer names it fdconfig.sys even on a non-dual-DOS-boot system then IMHO that should be corrected (for the reasons you mention). Bart --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user