Re: [Freedos-user] Over 4-GB for FreeDOS, Etc.
Hello, 2) Do not support a super allocate, just let XMS clients alloc memory as long as it is available - but start in the first 4 GB and/or use memory after that easy area only for big allocs... 3) You need no outside-visible super extended move as long as only XMS access to the extra memory is available. HOWEVER this means that the super XMS driver will have to reject requests to lock XMS memory to a fixed address inside the first 4 GB (which simply is the XMS 3 API limit) as soon as it runs out of space in the first 4 GB. For simplicity, I would not even suggest to move around XMS handles. Instead, I would support locking and fixed addresses only for handles which physically were in the first 4 GB anyway at the moment when they were allocated... Might work, but it's hackish and IMO it's important that a program can tell Himem that it prefers to get physical memory from beyond the 4 GB limit. PS: Regarding I/O virtualization, the MS EMM386 API for this is relatively small, int 2f.4a15 basically. JEMM386 with the JLM driver support infrastructure could probably implement support for int 2f.4a15 as a small JLM driver at some time. Yes. letting software use the extra memory. It is in no way part of the XMS interface to coordinate PAE paging between HIMEM and the software that uses XMS. Of course you are right that PAE paging most likely isn't needed, the simpler approach 32-bit paging with 4 MB pages should do as well. japheth -- 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] dos extender saga.
Hello, Japheth, I tried what you said: ran hdpmi32 -r-m, then the exe, and it worked; then tried cwsdpmi -x then the exe, that also worked. Remaining question: how do I build-in the '-x' switch at compile time? The sandman site does not address this point, and the delorie search archives are acting buggy, plus they are ten years long!. Sent email to delorie; waiting on that. If this is a dupe, my bad, There's a hint about this problem in the djgpp faq: http://www.delorie.com/djgpp/v2faq/faq9_1.html -- 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] DPMI,et al.
Eric, the program I wrote, which drew the page fault, uses the int86 in four of the eight functions. the program is a mouse event handler, and micro-gui. I already had included 'dos.h', but I did not realize ther was a 'dpmi.h'! I'll have to pry into that header to try to see what exactly it can do. The thing is, djgpp has a nice solid library, and I like to stick with something that looks standard. At any rate, does anyone know of a utility that will stick a PE stub on a djgpp, either alone, or in tandem with the MZ stub, insuring dos compatability?--kurtwb2...@gmail.com mailto:wb2...@gmail.com. If your program runs in a Windows DOS-Box, but causes a page fault in DOS or DOSEMU, then there's a good chance that it erroneously uses a NULL pointer for memory access. This is a pretty common error, and AFAIR there is a switch for cwsdpmi to disable the page 0 protection. You can also test with HDPMI's -m switch: C:\HDPMI -r -m C:\your_program.exe If your program runs in this configuration without page fault, there is a forbidden NULL pointer usage inside your program. -- 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] What do you need from Windows world...
Internet Exporer 5 and earlier, maybe 6. Hardest-core CRAP, please don't pull it out if it's grave. Using IE 5 instead of Arachne is a good idea. It has support for the MS version of JavaScript (JScript) and runs even on Windows 3.11 standard mode. This makes it render a lot of web sites far better than Arachne. -- 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] What do you need from Windows world...
Hi, Blake Stone Aliens of Gold requires the MS-DOS 6.22 or the Windows 9x version. It can run on top of Windows 9x. Wolfenstein 3D has the same problem because it's probably based on the same underlying engine. It starts under Freedos, but none of the keys work. I just tried BS and W3D with newest FD kernel on a P4 with a SB Live Value card. Software loaded is JemmEx, SbeInit and a German mini-kbd driver. I encountered no problems with either BS or W3D, both sound and keyboard work as expected. -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] make-me crazy.
Hello Ahhh, it's amazing; not one tutorial specifically for the dos version of 'make'; even what there is, not too specific. To wit: indeed, some thing you are trying to install,say , HX, GEM, etc., they do include makefiles, [snip] You mentioned HX so I'm forced to feel somewhat responsible. However, I don't know what you're talking about nor what you're trying to do. Is your post intended to be a bug report? Then it is a report of rather *questionable* quality and can easily compete in this regard with the one from Kink InuYasha recently. If you have the attitude that you're a - potential - customer and that because of this people should feed you with the information you need then I'll have to disappoint you. It doesn't work this way. It's your turn, you'll have to try to explain - in a structured and detailed format - what you're trying to do and what didn't work as you expected. -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS on Virtual PC 2007
Are the BLASTER settings described anywhere in detail? VPC says it emulates the Creative Labs Sound Blaster 16 ISA Plug and Play. Maybe my settings are wrong. You can use the GETSB.EXE tool which is contained in HXGUI (http://www.japheth.de/hx.html). It reads the SB16 mixer status directly, thus it's able to tell the true values for IRQ and DMA. A PnP card usually has to be enabled - for SB16, there was a tool DIAGNOSE.EXE, which did this. But IIRC this isn't needed for VPC, the SB16 card is enabled automatically. -- Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] generic bootsector as file? - versatility of grub4dos explained
also many things are running in background :) just ask Eric, Mateusz, Rugxulo, Blair, ... That's probably one of FreeDOS's problems: there's ony guy - I don't want to be more specific - who forces all communication into private mails. This makes the current FD status absolutely intransparent for other people. The public mailing lists - kernel and devel - are either virtually empty and dead or filled with lot of noise. -- Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] generic bootsector as file? - versatility of grub4dos explained
why do you think that the RxDOS kernel is superior - besides having many more bugs ? What about built-in support for LFN? -- Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] generic bootsector as file? - versatility of grub4dos explained
Hope you don't mind me to ask, why didn't you rather contribute to FreeDOS? But he DOES contribute to FreeDOS: once the few remaining bugs are fixed in the RxDOS kernel, it will replace the inferior current FD kernel. -- Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Poll and ideas compressed filesystem
Would you want a compressed filesystem at all? My discouraging answer: I just don't need it. I think, what FreeDOS needs for daily use is a good graphical web browser, a nice e-mailer, a word processor like Abiword, FOSS USB drivers, ... In what way would FreeDOS differ from Linux 2.4 then? Apart from being worse in performance, multitasking, having no GUI, no way to show several apps at once... Perhaps in the way that it won't need an eternity to boot or reboot ... Perhaps in the way that it won't need huge resources to work at all ... Perhaps in the way that it won't try to see everything as files ... Perhaps in the way that it has a way better DOSEmu :-)) Perhaps in the way that it won't have zillions of apps which are not really usable... ... Perhaps in the way that it's not that POS that Linux still is. -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Application crash
Sorry for long responce. I was update Jemm, because previous version have no xmsstat. The xmsstat output attached as memstat.zip. the report for Jemm did display no handle regionsize(kB) locks flags 1 00A8 0011-00138FFF 164 1 02 used 2 00B2 00139000-00158FFF 128 1 02 used 3 00BC 00159000-002D8FFF 1536 1 02 used 4 00C6 002D9000-00558FFF 2560 0 02 used 5 00D0 00559000-00958FFF 4096 1 02 used 6 00DA 00959000-009933FF 233 0 02 used 7 00E4 00993400-00995BFF 10 0 02 used 8 00EE 00995C00-00A95BFF 1024 0 02 used 9 00F8 00A95C00-00E5A3FF 3858 0 02 used 10 0102 00E5A400-00EF 663 0 01 free so the extended memory managed by Jemm is from 10h-EF only (14 MB). This might be due to a memory hole of size 1 MB at F0-FF. JemmEx, FD Himem and HimemX have a restriction: they can handle ONE extended memory block only. There are 3 options now: 1. try to disable the hole. Some BIOSes allow to enable/disable the memory hole in the setup. 2. use Jemm386 instead of JemmEx and continue to use your previous XMS host. 3. JemmEx's source can be extended to be able to manage more than one block. This means some work, because the current implementation isn't very flexible. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Application crash
2. use Jemm386 instead of JemmEx and continue to use your previous XMS host. 3. JemmEx's source can be extended to be able to manage more than one block. This means some work, because the current implementation isn't very flexible. Nothing wrong in my fdconfig.sys? JEMMEX.EXE A20 ALTBOOT I=TEST X=TEST S=C800-EFFF XMSHANDLES=32 SB EMX VERBOSE No. This isn't a problem of wrong command line options. If your BIOS doesn't allow you to disable the hole, try option 2. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] announce: jwasm 1.91 for dos windows linux
Hi, an update for JWasm was necessary, now v1.91 is current. The update is strongly recommended, v1.9 contains a pretty nasty bug in 16bit code generation, bad code might be generated without warning. Besides bugfixes, there's one improvement: the /bin switch allows to create raw binaries, no link step is needed. download: http://www.japheth.de/JWasm.html changelog: http://www.japheth.de/JWasm/history.txt - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] announce: devload cutemouse graphics triple update
Note that JWASMD, a WASM variant with MASM .asm support, needs the HDPMI32 DOS extender in your PATH. See www.japheth.de ;-). there's now JWasm v1.9 available, which contains a stand-alone DOS binary. download: http://www.japheth.de/JWasm.html changelog: http://www.japheth.de/JWasm/history.txt - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] cutemouse ctmouse 2.1 beta 4 and jwasm news
Maybe it is context sensitive in TASM, 0 in .data and nop in .code? I believe NASM has a whole range of ways to align things, including pad with user-specified value and pick a multi byte noop machine code instruction where appropriate but you would have to check the docs which is selected when and which syntax overrides. As for the MASM implementation - dunno, too long since I last used MASM ;-). What Nasm does is not that interesting for a Masm-compatible tool. I changed JWasm to the Masm behavior, that is, for 16-bit, NOP, MOV AX,AX and MOV CS:AX,AX are used to pad 1,2 or 3 bytes. About the direction of same-op and xchg instructions: Can you add a syntax for the reverse variant? Afair NASM has this, to make it possible for users to control the byte-exact machine language generated as some exotic apps may need that... Currently it's not the time to implement additional options. But I will check what Masm does and adjust JWasm accordingly. - cmp ax, valuebelow128 uses cmp ax,word in TASM but I cannot make JWASM do that - it uses cmp ax,byte - adc ax,0 has the same problem as cmp ax,4 ... Masm allows cmp ax,word ptr 0 to force it to use the non-sign- extended version, but this doesn't work yet in JWasm. I think this would be pretty useful - the word sized variant of that is popular for self modifying code where constants are updated later... It's fixed in v1.8. - macro options can be of type rest and vararg only in TASM Masm syntax allows VARARG as a parameter qualifier: Okay then it seems JWasm does not allow it yet ;-) It does. However, I don't know whether Masm's VARARG implementation matches Tasm's one. Check the jw-* files in the ctmouse jwasm port: TASM seems to let you write constants as combinations of variable names and lists of elements to fill in for their bitfield. Elements can be skipped and can have default values, as in ,,1,0,,3. You can also write lists of elementname=value to describe the value of a bitfield variable, it seems. With JWasm, you get either an error message or the value 0 in most cases I believe ;-). Good examples are the out_ macro invocations I had to replace... Indeed. I couldn't imagine anyone using bitfields seriously, because there are some stupid design flaws. Nevertheless default values and initializers for RECORD items are implemented in v1.8. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] cutemouse ctmouse 2.1 beta 4 and jwasm news
It's fixed in v1.8. Odd, my report already was about 1.80 ... Ok, then you forgot to tell us that you have access to a time machine. Because the versions stored on my site are v1.7 and v1.8pre. Then an error message would have been better than a 0 value... Sure. Looking back, many things could have been improved ... there are some stupid design flaws Which? most annoying one is that bitfield names are global. Also bad is the direction in which the fields are defined (from high to low), making it very difficult to convert C headers to ASM include files. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] cutemouse ctmouse 2.1 beta 4 and jwasm news
Hi, thanks for posting your results! - TASM evendata pads with 0, JWASM even pads with 0fch I do not know how to change this, I just used db 0. this is indeed hard-coded in the source and will be used only if a 16-bit CODE segment has to be padded by 1 byte. The reason why not just 0x00 bytes are used is because runnable code must be generated, as it can be seen in the following example: mov cx,8000 align 4 nextitem: xor ax,[bx] add bx,2 loop nextitem ... Using 0xFC, however, is a bad idea because it is the CLD instruction, which isn't a noop. - sbb ch,ch xchg dx,si xchg cl,bh xchg si,di sbb al,al xchg dh,bl xchg cx,si xchg cx,bx xchg dl,al xchg dl,ah xchg dx,si xchg ah,al (but not ALL xchg instructions) all swap the arguments when compiled with JWASM as compared to compiled with TASM - I used db ... here. Since someone has made big efforts to implement these optimizations in the Wasm source, I didn't touch them, although I have no idea whether they are useful. - cmp ax, valuebelow128 uses cmp ax,word in TASM but I cannot make JWASM do that - it uses cmp ax,byte - adc ax,0 has the same problem as cmp ax,4 ... Masm allows cmp ax,word ptr 0 to force it to use the non-sign-extended version, but this doesn't work yet in JWasm. - macro options can be of type rest and vararg only in TASM Masm syntax allows VARARG as a parameter qualifier: m1 macro p1, p2:VARARG ... - JWASM seems to have pretty bad support for record bitfields, I had to remove most references to them to avoid broken code Please provide more details. JWasm copies Masm, and Masm's implementation of bitfields isn't very intuitive. - JWASM uses only 8 instead of 16 bytes for foo db 8 dup (?,?) That's a severe bug. It occurs if a question mark is the last of multiple items in a DUP argument. Instead of .model use16 tiny I had to use the JWASM -mt command line option. valid Masm syntax is .model tiny. - you cannot say ERRIF in JWASM there are various .ERRxx directives in Masm. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] FD Debug + Jemm
Hello, v1.13 of FD Debug is available: http://www.japheth.de/debxxf.html. v5.71 of Jemm is available: http://www.japheth.de/jemm.html. Both are just bugfix releases, and the bugs fixed are minor. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FD Debug + Jemm
Hi :-) v1.13 of FD Debug is available: http://www.japheth.de/debxxf.html. v5.71 of Jemm is available: http://www.japheth.de/jemm.html. Both are just bugfix releases, and the bugs fixed are minor. Nice, Thanks for your kind remark! :) but could you update the two readme files on your homepage anyway, so we can read some information about the changes? Done! While you are busy anyway, it would be nice if you could even cut and paste those 2 changelog entries into a reply to this mail on this mailing list ;-). Sorry, no. cut and paste are things from the Windoze/Loonix world and have no reason to exist in DOS. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] FD Debug 1.11
Hello, Debug v1.11 is out. 7 bugs have been fixed (same as in Jemm v5.70 - seems to become my new standard). Also, debugx can now display floating point registers much nicer. So this update is highly recommended - at least for those who still know what DEBUG is good for. 1.11 [06 February 2008] - bugfix: debugger lost debuggee's HiWord(EFL) in real-mode. - bugfix: if debuggee set CR0 AM bit and EFL AC flag, an exception 11h occured in the debugger. - DEBUGX bugfix: G command was unable to set/restore breakpoints if HiWord(EIP) wasn't clear. - DEBUGX bugfix: U ignored HiWord of argument's offset part. - DEBUGX bugfix: E ignored HiWord of argument's offset part. - DEBUGX bugfix: M didn't accept first argument's offset . - DEBUGX bugfix: running in NTVDM and pressing Ctrl-C while debuggee is in protected-mode no longer drops to real-mode. - DEBUGX: RN now renders floating point register content properly (DEBUG still just displays raw hex format for size reasons). - DEBUGX: DI got an optional 'count' parameter. - DEBUGX: D default segment part is checked if it is valid in pmode and changed to value of client's DS if no. http://www.japheth.de/Download/debug111.zip - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] jemm v5.7 ...
The forum discussion suggests that most of the bugfixes in jemm386 5.70 fix minor or rarely occurring bugs :-). Yes. The one thing which I'm unable to decide whether it's relevant is the lacking reentrancy of v5.69 converning XMS block moves. A TSR which hooks the timer interrupt and then calls the XMS block more (i.e. a write-back cache program) usually should ensure that XMS is safe to call, but I don't know what usually is in this regard. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] jemm v5.7 ...
... is out: http://www.bttr-software.de/forum/forum_entry.php?id=3132page=0order=timedescasc=DESCcategory=all - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Jemm v5.69 ...
is out. It can be found at http://www.japheth.de/jemm.html changes for v5.69 - memory block copies are now done with interrupts enabled - if client's interrupt flag is set. This avoids interrupt latency and makes the previously implemented interrupt windows obsolete. It also avoids problems with Jemm's HLT emulation causing IRQs to be misinterpreted as exceptions (08, 09, 74, ...) on some cpus. - bugfix: VDS scatter/gather lock with region size 0 returned 0 entries, but 1 entry must be returned in any case (MS Emm386 does as well). - bugfix: there was a risk that a ROM located contiguously behind another ROM in address space wasn't detected. - bugfix: if SPLIT option was set and a split ROM page followed an UMB page (which is possible if ROM size is 4 kB), the ROM part of this page was added to the UMB. - bugfix: synchronization of VCPI and EMS free memory count did work for VCPI only, that is, allocating all VCPI memory didn't reduce free EMS memory to zero. - bugfix: the last XMS memory block allocated for EMS/VCPI memory was likely to be too large, thus wasting XMS memory. - VCPI/EMS memory alloc/release speed-up. - EMSSTAT -v displays more VCPI infos. - v86 exceptions = 8 are routed to v86 interrupt 06h only if this vector has been changed by another program. - evil exception 10h (floating point) is now detected and displayed, thus avoiding the hazardous call of video interrupt 10h (MS Emm386 also detects exception 10h, but just allows to reboot then). - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] JEMM troubles - with VESA LFB
Actually: Why does hdpmi use a non-1:1 mapping linear/physical? I mean it has every right to do so, but it turned out that this can make DPMI usage a bit more foolproof ;-). I assume it saves a bit of page table space? Being NOT foolproof can be good as it can help to detect bugs, but otoh, a command line option to go into a more foolproof style would not hurt either. I'm happy that this thing - which is old and hard to maintain - is still running. I don't feel to implement thousand tests and options to work around all possible and impossible protected-mode programming errors. :-D I just want to say: No Toasted does not simply crash because any emm386 is loaded. So you cannot say jemm386 works as bad as other emm386s so there is no need to fix it ;-). It's cool ... and it runs with Himem only. I tried Jemm, MS Emm386, DR Emm386, Win98 DOS Box, CWSDPMI, HDPMI (with/without Jemm's NOVCPI option) ... nothing worked. Anyway, it's not a Jemm problem. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] JEMM troubles - with VESA LFB
I'm happy that this thing - which is old and hard to maintain... But I was talking about hdpmi32...!? Yes, me too. hdpmi32 v1.0 (10/1993) is older than FreeDOS v0.001 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] JEMM troubles - with VESA LFB
You can download it as part of my NEWTRACK eye-tracking DOS software, and of course you need no dual VGA for PCXTEST ;-). The download is at www.coli.uni-saarland.de/~eric/newtrack/ I found out that: - pcxtest always works with dr emm386 - pcxtest fails (while some selector points to c0008000:x...) with fd emm386 and jemm386 in a DEFAULT freedos 1.0 install - but after I found out that some smart person had copied the HDMI32 exe file to CWSDPMI exe and put a REAL CWSDPMI in the same place, pcxtest also started to work with fd emm386 and with jemm386... - the funny thing here is that hdpmi32 is supposed to be very compatible with jemm386, same author ;-) You forgot to mention whether there was any test with Himem in real-mode. This is not a negligible detail, because the original issue is exactly this: why did something work with Himem alone but doesn't with Jemm/FD Emm386. I did this for you and can tell: your PCXTEST also crashes without Jemm under simple Himem, it also crashes in a Win9x DOS-Box and it also crashes when DPMIONE is used as DPMI host. The reason is simple: PCXTEST is buggy (yes, I know the bug, but I'm a nice guy and don't want to spoil you the pleasure to find the reason yourself). It happens to run with CWSDPMI, but I'm almost sure this is the only host it really runs with. Didn't you test with your favorite host, DosEmu? It also has LFB support in console mode, AFAIR. Just allow direct hardware access! - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] JEMM troubles - with VESA LFB
Just tell me what the bug is :-). in vesainit.c, search for /* update */ It happens to run with CWSDPMI, but I'm almost sure this is the only host it really runs with. What is special about CWSDPMI (and DR EMM386) then? I don't know. Even easier, you can tell DOSEMU to emulate a VGA with VESA LFB... If it forced me to go full screen, I would not use DOSEMU in the first place... Ok, but for testing PCXTEST it's ok. I bet it won't run. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] JEMM troubles - with VESA LFB
PS: The CTS Toasted 1996 ctstoast demo runs okay in LFB mode if CWSDPMI is resident or if you use DOSEMU, but I promise you that I did not write CTS Toasted and did not ask the authors to give it the same bug as PCXTEXT ;-). I don't understand what you are talking about. There was a bug in your program which remained undetected because it ran by chance in CWSDPMI/DosEmu. That doesn't mean at all that programs NEED to have this bug implemented to make them run in CWSDPMI/DosEmu. Now, after the PCXTEST thing has turned out to be a non-issue (as fas as Jemm/hdpmi are concerned), let's return to the original problem: your mysterious program which runs with Himem, but refuses to run in Jemm/FD Emm386. You told us a very vague result (things work better with DR EMM386) and then swept this thing under the carpet. So, after my experience with PCXTEST, I may ask: why don't you provide a download link for THIS unknown program, so that I can run it under MS Emm386 and/or check otherwise what the problem is. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] JEMM troubles - with VESA LFB
No, the crashing program just uses a DOS extender for direct framebuffer access. The DOS extender uses its own memory context (CR3, page tables), GDT and IDT. The EMM (Jemm) is responsible vor v86-mode only. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] JEMM troubles - with VESA LFB
- the program uses dos4gw but using dos32a instead does not help - the program crashes with fd emm386 and with jemm386... - the program works okay if only himem but no emm is loaded :-) this is no proof at all that the error is in the EMM! :)) So maybe it uses the int 15 memory copy function for framebuffer access at some point (the crash happens during initial graphics compatibility testing, might differ from animation display later)? if you didn't set NOCHECK a crash in Jemm's int 15h is not very likely. It might also be using XMS memory copy, no idea. XMS will not copy to/from regions not covered by a handle. A third idea is that it might access the framebuffer at a moment when the page tables of (J)EMM386 are active for some reason, maybe a TLB flush problem? impossible! :)) - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] JEMM troubles - with VESA LFB
Remember that there is a parameter in HIMEM to set apart a little memory for int15.. Did you try that? I tried nothing because it is Eric who has a crashing program. :) And from the error descriptions I got so far the problem is inside the DOS-extended application, not in the EMM. What might convince me that there is something to do is if the program runs with MS Emm386, but fails with Jemm. :) - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] JEMM troubles - with VESA LFB
Hi, I just double-checked my own EMM problem: With my PCIe GeForce 7600 VGA, both with the classic FD EMM386 and with JEMM386, I get a page fault when attempting to use VESA VBE 2.0/3.0 LFB framebuffer access to graphics. Please explain in more detail how you come to think that this is a Jemm problem. The only way Jemm might be involved is if you try to access the framebuffer via Int 15h, ah=87h. Then hopefully you didn't set the NOCHECK option!? The page fault address is c000, which matches the Linux idea of the memory map shown below. Please let me know how I can send you a dump of the various int 15 mem maps by email (off-list). I assume Linux uses int 15, PCI config space, and ACPI to generate the /proc/iomem memory map...? Is this a FreeDOS related question? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos x Virtual PC x Jemm
Lelio wrote: Thanks, now was with 613K of Convetional Memory Free... and with DOS VPC's Guest Additions. Good to know! The mentioned bug in Jemm which must be cirumvented currently by setting option X=CC00-CCFF will be fixed in the next release. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] JEMM troubles
I replaced HIMEM and EMM386 by HIMEMX and JEMM386 today (I am running FreeDOS 1.0). Unfortunately, it hangs my PC. The system is booting okay, but when I use the PC, it displays an error message Jemm386: exception 08 occured at... and various hex numbers. It never happens (so far) when I use a game/program, but always at the command prompt (for example, after a DIR command, or CD .., etc...). The PC hangs sometimes immediately after the booting, but sometimes it works even half an hour. Any idea what is the problem? What's an Exception 08? Exc 08 is a double fault, but this is unusual and there is a good chance that it is in fact an IRQ 0 (timer interrupt). Current Jemm disables interrupts in protected-mode (this will partially change in next release), so an IRQ 0 shouldn't happen at all, but who knows. To decide that it's an IRQ 0 or a true Exc 08, the Jemm register dump (at least the value displayed after ERRC=) will help. Did you read the troubleshooting section in readme.txt? If such problems occur, the first thing to do is to run Jemm with the safest configuration (X=A000- ...) and see if the error persists. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] JEMM troubles
There it is: Jemm386: Exception 08 occured at: ... ERRC = 00110B40Col:1 Yes, the ERRC=0011 confirms that it is an IRQ 0, not an exception. However, I have no clue what the Col:1 suffix is meant to be. If this isn't a typo, there is a chance that Jemm's code in memory has been - unintentionally - modified by another program. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos x Virtual PC x Jemm
Hi, You should have mentioned something about the context instead of only throwing URLs at us ;-). The first URL talks about making more low RAM free by loading things high into UMB and by using fewer drivers. The second URL talks about DR DOS. One thing that might be useful for FreeDOS and JEMM is the EMM386 hint in the first: It says you might be able to use: EMM386 ... I=B100-B7FF I=C600-C7FF I=CC00-CFFF I=e600-efff In other words, the Virtual PC VGA BIOS is only 24k it is 48 kB (C000-CBFF), but has holes. Using I=TEST finds most of them automatically, except the 4 kB region C700-C7FF (because it has a different last byte). OTOH, region CC00 seems to be not really free on VPC 2007, it contains a 2 kB ROM. Jemm somehow has the opinion that this region is free, however, I don't know why. To be safe, it should be excluded with X=CC00-CCFF. and the mono text mode buffer can be partially used for UMBs (b100-b7ff). My experience tells that the buffer can be fully used (B000-B7FF) Unfortunately it does not tell which things are in the way at e000-e5ff and c800-cbff, do you know more about that? Tool GetI15Ex (hxrt) displays: Int 15h, eax=E820h: addr 0, size 9FC00, type 1 (available) addr 9FC00, size 00400, type 2 (reserved) addr E, size 2, type 2 (reserved) addr 00010, size 001EF, type 1 (available) addr 001FF, size 0F000, type 3 (ACPI) addr 001FFF000, size 01000, type 4 (ACPI) which tells that region E000-EFFF is NOT free. Examining it with DEBUG confirms this. So a good Jemm line for VPC 2007 might be: DEVICE=JemmEx.exe NOINVLPG NOVME FASTBOOT I=TEST I=B000-B7FF I=C700-C7FF X=CC00-CCFF It will then install an EMS frame buffer in D000-DFFF. If EMS is not needed, the NOEMS will add 64 kB UMB. What should be mentioned with VPC's Guest Additions: the binary VMADD386.SYS must be loaded before Jemm in CONFIG.SYS and FSHARE.EXE is a buggy DOS TSR. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] HELP! i have problem with SBLIVE 5.1 driver in FreeDos.
-- Creative SB16 Emulation Driver, Version 5.00 Copyright(c) 1996-2001, Creative Technology Ltd., All Rights Reserved. Creative Audio @ Port d800, IRQ 7 error: Counld not allocate code/patch RAM below 4 Mbyte boundary. Try loading SBEINIT.COM before SMARTDRV.EXE or minimizing VDISK RAM. Creative SB16 Emulation driver NOT loading. - i dos lover , in freedos im new! :) help me all. With the SB Live emulation driver, you must avoid loading huge XMS memory consumers in config.sys and/or autoexec.bat. Usually such consumers are cache programs (LBACACHE, SmartDrive, UIDE, ...). If you need the cache drivers, then FIRST load the SBLive driver and THEN the cache program. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] ctmouse v2.1b problem in Qemu 0.90
Hello, when I run ctmouse v2.1beta in Qemu, it says Installed at COM1 (...) in Mouse Systems mode and the mouse does NOT work inside the emulator. If I try ctmouse /P, it displays Error: device not found The old ctmouse v1.91a does not have such a problem, it detects a PS/2 mouse and works in Qemu. - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Speed boost with xdma32/xcdrom32 in virtualizers
I made tests running xdma32/xcdrom32 in Qemu, VirtualBox and VirtualPC. There are significant speed increases to achieve, but they require to set additional parameters. For details see: Qemu: http://www.bttr-software.de/forum/forum_entry.php?id=2463 VBox VPC: http://www.bttr-software.de/forum/forum_entry.php?id=2482 Please use these versions in virtualized environments only, they are preliminary! (I checked this email several times for typos and was unable to find one!) - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Congrats to Grech!
Jack, my fRiend, do you think it is a good idea to make a federal case of a missing little r? Try to calm down! Jim Hall isn't a FOOL by having ignored it, it's at best an indication that he isn't paranoid. The guys you mentioned to be your witnesses, Kuhnt and Lucho, they are slightly biased, aren't they? The SHSUCDX bug you mentioned is NOT commonly known. See http://www.bttr-software.de/forum/forum_entry.php?id=2374 for more details. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Congrats to Grech!
I was referring to one forum already banned some of the people involved in this flamewar and another forum was closed because of this flamewar. I am not suggesting to follow those examples... ;-). Eric, you are a wag. :)) btw, I was banned by the admin of the EDR forum (Evil DoctoR) because of spamming, not for trolling. And it's nothing to be ashamed of, because my crime was to post several times that I find it slightly unwise to abuse and make fun of someone who just reports a bug. The someone was user NTOSKRNL and the thread is still to see here: http://www.drdosprojects.de/forum/drp_forum/posts/6007.html - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Jemm v5.68 available
Hello, Jemm v5.68 is now available at http://www.japheth.de/Jemm.html changelog for 5.68: - bugfix: JLOAD's Lock DMA function ignored flag to check for 64 kB border crossing. - NMIs occuring inside the monitor are now silently routed to v86-mode. Previous Jemm versions displayed an exception dump. - XDMA32 added, supports legacy and native IDE controllers. - XCDROM32 now supports legacy and native IDE controllers. - some bugfixes in XCDROM32. Many thanks to my fiend Jack R. Ellis! Without him and his XDMA/XCDROM drivers this update would not have been possible. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Jemm v5.66 bugfix for Phar Lab TNT binaries
Hello, running Phar Lab TNT binaries didn't work with Jemm versions 5.60-5.65. This is fixed in v5.66: http://www.bttr-software.de/forum/forum_entry.php?id=342 - 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] Jemm v5.66 bugfix for Phar Lab TNT binaries
Hello, I think this is a good idea for compatibility and debugging in general :-) A bugfix increases compatibility, that's correct, but in general there are no other benefits. PS: I notice you also updated the readme item about 5.65, saying that the EMS page frame is now on a 16 kB boundary again. This should always be the case - could you give us a hint which versions did support non- aligned page frames and where therefore confusing to some classic apps? the word again might be a product of your brain ... this check was new to v5.65, therefore all versions v5.65 didn't ensure 16 kB alignment. Japheth - 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] Jemm altboot update
Eric Auer wrote: ... [very detailed explanation] ... Thanks for your thoughts and hints, Eric! It is interesting that the catch just puts an int 19 there, is that a real reboot or just a fastboot in this case? I've forgotten by now. But you can test with DEBUG: a :0100jmp : g However, it is not good that JEMM now simply ignores the altboot option. it's acceptable IMO. The few machines which caused troubles were listed in the MS document, and I don't think they are widely used nowadays. And IMO the MS ALTBOOT strategy is slightly hackish. It checks the caller's address (which works with MS KEYB), but a - tiny - keyboard driver which just hooks into int 15h, ah=4Fh, won't be detected this way. So no, I'm not gonna do this extra work ... without a reliable test case ... for nothing. There also seem to be adjustments in virtual A20 handling and UMB handling, could you explain what has changed? Nothing, just cosmetic. - 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
[Freedos-user] HimemX v3.31
Hello, There is a bugfix release available for HimemX at http://www.japheth.de/Himem331.zip The first bug caused v3.30 to fail on cpus pentium when running in real-mode, the latter gave unexpected results when running on MS-DOS 6.x (and most likely 5.x, 4.x and 3.x as well). In case you wonder what this thing is at all: HimemX is an extended memory manager (XMM) derived from FD Himem. XMMs are needed by some DOS programs, caches, ram-disks and similiar sort of things. - 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] HimemX v3.31
There is a bugfix release available for HimemX at http://www.japheth.de/Himem331.zip sorry, the link actually is http://www.japheth.de/Download/Himem331.zip - 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] collision between freedos emm386 and memdisk
We (many people in this list) espent months testing himem and emm386 from Michael Devore. Are those two just a bugfix from *that* well tested version or is it descendent from somewhere else? As for HimemX: there are 12 bugfixes and some optimizations, all described in the readme.txt. As for Jemm: some parts are rewritten from scratch, some are heavily modified. It's quite different from FD Emm386 now. Btw, in the name of how many people are you speaking exactly? And what do you regard as well tested. Because, as for me, I seriously doubt that a program is well tested just because some dozens (or some hundreds? I have no idea how big the FD user base is.) people boot FD with Himem, running their favorite handfull of apps occationally and then switch back to windows/linux. - 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] collision between freedos emm386 and memdisk
Hi, Hi Japheth, Japheth escreveu: Btw, in the name of how many people are you speaking exactly? And what do you regard as well tested. Because, as for me, I seriously doubt that a program is well tested just because some dozens (or some hundreds? I have no idea how big the FD user base is.) people boot FD with Himem, running their favorite handfull of apps occationally and then switch back to windows/linux. Lots of tests were done by lots of people here in the list. I understand your point that lots of people can mean nothing... but those test were of many programs running in many platforms. Just to name one: there was one bug-for-bug fix that enabled BC31 to work, it was something about a register being 00h on exist of a certain call. The bug was by Borland, but the result is that now we can use one more impotant program that didn't work ;-) AFAIR this was a DPMI issue, using int 31h, ax=0300h with register CX != ZERO because the FD kernel returned CX 0 in a DOS version call and MS-DOS returned cx == 0. This issue is unrelated to Himem or Emm386. You should provide a better example. :) I am not woried about parts that you fixed or rewrote, on the contrary, you have a reputaion of very good code quality. What I am woried is that some compatibility fixes could get lost. I am planning to make a FreeDOS distro as of my own ideas. I personaly never had problems with emm386 since Michael's last version but I would like to know which is more appropriate for a general distribution. All I have to say is said already in the readme/history files. If you have worries, and FD Emm386 works fine for you, then there is no reason to care about Jemm. - 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] collision between freedos emm386 and memdisk
- FDHimem opens an interrupt window in v86-mode only. HimemX opens an interrupt window in both v86- and real-mode. that was probably the point where Jack started his own civil war ;) At least it WAS a bug, because this issue is mentioned in the XMS docs. - in FDHimem the routine which tests whether A20 is enabled is more complicated than necessary. I looks now like it looked ~5 years back. That's how things are going ... :) The 'more complicated then necessary' came in after some discussion about some (hypotetical) problems with 386, broken caches, etc. I don't mind - if extended memory is = 64 MB, the size returned by XMS V2 function is 65535 kB in HimemX, FDHimem returns 64448 kB. AFAIR, the 64448 number was intentional - some crazy app/game required this Yes. I didn't claim this to be a bug in FD Himem, I just changed it to the value returned by MS Himem. every thing else (just reading the ReadME !!) looks ok Thanks a lot! Btw, in the name of how many people are you speaking exactly? LOTS. It took lots of iterations to make EMM386 compatible with any existing DOS extender in lots of crazy/brain damaged apps/games. And what do you regard as well tested. it was developed according to the specs, then a couple of bugs fixed. after that, a ton of crazy software still didn't run as it expected specific limits (treating 65535 kB as signed integer etc.) AFAIK, Michael fixed all these issues. There are still some (dozens) left in FD Emm386 ... - 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] Freedos 1.1...
Bart has added support for that to the CVS/SVN version of our kernel. I hope Japheth noticed :-). The changes are: On int19 (prepare for warm boot / warm boot / run boot sector or however you want to call it), FreeDOS now un- hooks all hooked BIOS interrupts. And on boot, FreeDOS now stores the original vectors of several hooked BIOS interrupts at traditional 70:something (or 50:? 60:?) place in RAM. The latter is later used for int19 later, but can also be used directly. As said, the original BIOS interrupt vectors are stored at a well known / standard place in RAM by the CVS/SVN version of our kernel now :-). Good! To those who do not understand a word of the above: QEMM386 and newer versions of Japheth.de JEMM386 and JEMMX support a fastboot option which triggers the same style of reboot as FDAPM hotboot, which only loads the operating system again, skipping some boot up BIOS activities. This option only works if DOS and all drivers allow proper shutdown before reboot, and Bart added exactly that to the kernel recently. 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. - 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] FreeDOS and MPlayer
The hxrtd.zip file mentioned above also seems to have something wrong with it, the 'ole32.dll' file has a file size of 0 bytes! Thanks for the hint! It has been fixed. However, this file isn't relevant for mplayer AFAICS. I tried it too again with those files, but get lots of errors with any video file, such as Option_mv0_threshold needs a parameter at line 1 Option possibly needs a parameter at line 2 That's bad luck. mplayer works with hx more or less unintentionally - obviously with some codecs and/or binaries only. - 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] Screen Shot of FreeDOS boot problem -- illegal instruction
Then you should try www.japheth.de JEMM386 and maybe some manual tuning for the options. Try for example X=e000-efff X=test and maybe some options which are recommended in the JEMM386 readme. The most important setting in Jemm386 concerning MS VPC might be NOINVLPG. Indeed, this option was added just because of this emulator, which seems to have problems emulating the cpu's TLB correctly. With this option on Norbert Remmel got MS VCP, FD and Jemm386 to work finally. Generally, since the emulators apparently aren't fully reliable, it might be a good idea to first boot FD without Himem/Emm386 and then advance step by step. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Microsoft C/C++
May you show examples? Starting from minimal void main(){}, then with
printf(Hello, world!\n), then something more complex? With OW 1.6:
a dummy main and a hello world main are utterly irrelevant if you want to
compare size/speed optimisations (leaving CRT aside).
A complex sample is Jemm386 C part (it can be compiled with both MSVC and
OW). It is still small model, but uses some far pointers, and OW is very dump
with far pointers.
?! Using 32-bit instructions in 16-bit programs may be useful, but this
is another story. How this relates to difference in generating 16-bit code?
if this is another story, then why does a program benefit both in size and
speed if you add the -G3 switch (use 80386 instructions) in MSVC 1.5?
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Microsoft C/C++
How much? MS VC is 6% better than OW, both optimizing for size. OW is not bad, especially if comparing MSVC with TC, where MSVC is 25% better. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Microsoft C/C++
Better than watcom? How much better and in which areas? In Open Watcom just the 32bit C(++) compiler and WD are pretty good. The rest is of mixed quality. With optimisation on MSVC CL.EXE beats OW WCC.EXE significantly both in speed and binary size (not counting the CRT part). One reason for this might be: although the OW 16-bit compiler WCC has switches to optimize for 386/486/Pentium/PPro it doesn't seem to use the 32-bit registers if one of these switches is set. The one 32bit opcode I was able to find is the PUSH dword ptr [x] to push an (unsigned) long parameter for a function call. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Microsoft C/C++
I own MS VC 1.5 which runs in DOS with the Phar Lab TNT DOS Extender. IMO it is the best 16-bit C(++) optimising compiler :) - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] [Freedos-devel] announce: OpenWatcom 1.6 distributive in .zip archives
Are the binaries unmodified? I'm asking because there is a KNOWN bug in OW 1.6 with DOS4G applications launching other applications. The enviroment of the launched application contains garbage, which makes it pretty impossible to use BINW\WMAKE for example. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Connect to internet through Router (resend)
of Linux or Windows. This means that for example you have to wait until your app gets a new DHCP lease every time when you start it, because no central networking driver of the operating system would be around to cache that. IIRC watt-32 (not sure about wattcp) caches this info in file %TEMP%\W32DHCP.TMP. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] SHSURDRV Write Protection Violation
Lester wrote: I'm trying to replace SRDISK with SHSURDRV (v1.11, 2005-12-21) to make a ram drive E. Fdconfig and Fdauto load ok but when using Arachne browser, after exiting (to dos shell or permanently), I get the following error: error reading from drive E: DOS area: write protection violation attempted Readme file mentions /W switch but it's supposed to be used only with shsufdrv and not shsurdrv. I didn't try it because it looks like a high risk experiment (host drive corruption can occur). /W is for SHSUFDRV only. SHSURDRV uses XMS memory to install a RAM disk, which is far less critical than SHSUFDRV's file access. So the RAM-Disk is writeable by default (it would be pretty useless to let install SHSURDRV an - empty - RAM-Disk and then not be able to fill it somehow). I just tested SHSURDRV v1.11 (8 MB RAM-Disk) + ARACHNE v1.90 (core.exe dated 24.06.2006) + CTMOUSE v1.91 and did not get that error. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] How To Get Arachne Working With DSL Connection?
Lester Vedrox wrote: My connection: DSL modem + router + Realtek NIC. The packet driver RTSPKT.com loads fine but Arachne won't open any web page. _http://img138.imageshack.us/img138/9059/10112006035337it6.png_ Which version of Arachne.cfg shown below is correct? Ver #1 (all tcp/ip entries are blank or set to zeros) [tcp/ip] IP_Address BOOTP IP_Grab IP address set to NameServer AltNameServer Gateway 0.0.0.0 AltGateway 0.0.0.0 Netmask 0.0.0.0 TCPconfig LANTCP.CFG I dont know what's wrong with your config, but mine looks like this: [tcp/ip] IP_Address WATTCP IP_Grab IP address set to NameServer 0.0.0.0 AltNameServer 0.0.0.0 Gateway 0.0.0.0 AltGateway 0.0.0.0 Netmask 0.0.0.0 TCPconfig c:\dll\wattTCP.CFG and c:\dll\wattTCP.CFG is: my_ip = dhcp ;hostname = ; optional ;netmask = 255.255.255.0 ; mandatory if not using DHCP ... - 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=lnkkid=120709bid=263057dat=121642 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] [Freedos-devel] Version 2.23 EMM386/HIMEM New Release
The host stack problem is solved. Fine :) Not a severe problem (IMO it's more like a feature), but the A20 line switching will only work if an UMB handler has been installed. There are some constellation where this is not true, and then the A20 gate is unhandled by Emm386. There is also still no option to deactivate the A20 thing. I don't like it. A possible problem, but most likely also minor, if at all: the emulation of int 15h, ax=87h modifies PTEs under certain conditions, but I couldn't find a TLB flush done afterwards. - 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=lnkkid=120709bid=263057dat=121642 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Updated 1.0 Testing CD
Also, your patch doesn't solves issue (which you try to explain) in case, if extended key pressed together with Ctrl-Alt. Ie., even if problem exist, then you fix for it incomplete. Yes, since it is a bug in *qemu*, not Emm386. Emm386 can do its best to work around this bug, but not fix it. 386swat specific? Or this is more generic and applicable for other debuggers? If first, then, I suggest, this code shouldn't be present in production code (release) - not in executable (see how Michael excludes CheckBlockIntegrity or even not in source. Yes, indeed, 16 - 32 bytes of extended memory are wasted. :( - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Updated 1.0 Testing CD
Barring the fileset I requested, or other testable indication that your problem occurs with anyone else, I should not think that would be a problem. In other words, no need to wait for EMM386 3.0 - codenamed The Arkady Factor. Since the error is evident in my eyes, I will not spent any more time to proove this. But indeed there is no need to wait, and for those who might run into the problem as I did, you can download a fixed Emm386 at http://www.japheth.de/Download/emm386.zip it has also been tested to be compatible with the newest QHimem2 driver. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Updated 1.0 Testing CD
I have been made aware that there is no description of the error I was refering previously here on the list. That's true, sorry, it was described in BugZilla. But a brief overview is: - it requires Himem + FD Emm386 to be loaded - it occurs when FD Himem has been started with parameter /NOX2MAX32 or if another Emm386 compatible XMS host is used (MS Himem or QHimem2), which lacks this (NO)X2MAX32 parameters at all - it occurs with (some?) DOS extended applications (my test case were DOOM, HERETIC, ...). Real-mode apps are not affected. - it occurs on real machines (usually an instant reboot when starting the application), on qemu (usually a freeze) and in vmware (which smartly tells that a host stack corruption occured). The virtual environments were setup with 128 MB Ram. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Updated 1.0 Testing CD
Are you willing to do that trivial task and demonstrate an actual interest in helping to correct the issue, or will you just preach and post here? Neither nor. The issue is of minor general interest, since most FD users will use FD Himem and FD Emm386 with the standard parameters. For me it was of interest, because I want FD-Emm386 running stable with MS-Himem (and other XMS hosts). So I did some research, found a bug and described in Bugzilla - IMO sufficiently detailed for someone interested in the matter - what I've done and that I was able to fix it. That's all, after that I admittedly lost interest in this subject. For the 2-3 FD users who might also want to use FD Emm386 outside of FreeDOS or with other XMS hosts I provided a url to download the modified version, with source included. That's it. Where's the problem? The test case you are requesting, yes, sure, I didn't do that yet, since dealing with a fixed bug is like reading the newspaper of the day before yesterday. Compare this my lack of interest with your's not wanting to provide a working build environment and then ... - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Updated 1.0 Testing CD
J (apparently gives problems with extended keys). Which ones? As you possibly know, by reading port 60h you send the keyboard controller an interrupt acknowledged signal, so it can send the next byte. On real hardware this takes some time (some microseconds at least), but qemu is unable to emulate this slight delay. So everytime the keyboard controller has to send more than 1 byte (as it is the case with the extended keys for example), qemu will get confused if port 60h is read unnecessarily and send the next byte too fast. I think, not not hurt - this must have modification. Because original code lost all previous flags and enables interrupts on exit (which may be undesirable by caller). Yes, aggreed, but most likely you will not find a real-life application where this is indeed a problem. PS: There are more changes, which I not mention, and which are not commented. For example, You promised not to mention them, so why do you nevertheless? what does DebugBreak? (Letters swat suggest, that this relates to 386SWAT debugger?) yes I wanted to call 386swat on exceptions - if it was loaded Then, you change map from 1.75M to 1.5M - by which reasons? I suggest, this may have bad effect, because Michael found (though, as always, not comment) some issues, which relate to size of preallocated memory. IMO this is a safe optimization, at least since recently because the address context is switched now to the host for the VCPI memory functions - this is part of the main issue. Also, you add some deals with client stack - no comments what wrong with original code. But this is the main issue. Please read my explanation in Bugzilla. You replace some code by clts - is it code optimization (reduction) or something more? Just an optimization. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Updated 1.0 Testing CD
this is the c:\fdos\fdauto.bat which was generated. May give a hint where the messages are coming from. @echo off SET dosdir=C:\FDOS SET LFN=N set PATH=%dosdir%\bin set NLSPATH=%dosdir%\NLS set HELPPATH=%dosdir%\HELP set temp=%dosdir%\temp set tmp=%dosdir%\temp SET BLASTER=A220 I5 D1 H5 P330 REM ShsuCDhd /QQ /F:C:\FDBOOTCD.ISO REM LH VIAUDIO REM LH VIAFMTSR if not %config%==4 LH FDAPM APMDOS if not %config%==4 LH DISPLAY CON=(EGA,,1) if not %config%==4 ShsuCDX /QQ /~ /D:?FDCD0002 /D:?FDCD0003 /D:?CDRCACH0 SET CFGFILE=C:\fdconfig.sys [Undefined message 7.0] [Undefined message 7.1] [Undefined message 7.2] [Undefined message 7.1] mouse lh doslfn - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Updated 1.0 Testing CD
After the first installation I wanted to test if FD is now able to detect if it has enough free space (or at least is able to abort the install process in a friendly manner). I renamed directory FDOS to FDOSALT. About 6,5 MB free space are left on C: - I booted from CD and select Install, FD does not complain! - again I didn't change language or directory - during installation of the packages the system stops. No message that it has a problem is displayed - I press Ctrl-C, the system asks: Are you sure wou wish to abort I press Y. - a message appears: Warning: error 255 occured! Press a key to continue I press a key. - now again some dozens undefined message x.x appear, at last I'm in the CD boot menu again. - I press h to boot from HD. On the screen: Booting from local disk... ... Nothing more. Ctrl-C does nothing. Have to do a reset. The C: drive is not bootable anymore :((. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Updated 1.0 Testing CD
Blair Campbell wrote: I renamed directory FDOS to FDOSALT. About 6,5 MB free space are left on C: - I booted from CD and select Install, FD does not complain! I am so sorry. I forgot to include the updated install.exe ! I have re-uploaded the ISO with the updated install.exe included. The localize problem will be fixed in the next release hopefully. This is no problem, since that's why we're testing. No need for a hurry, btw., the final FD 1.0 should probably wait for upcoming Emm386 v2.22 to be released :). - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] EMM386 new release 2.20, new HIMEM 3.20
On my machine A20 is always enabled. BIOS int 15h reports kbd and fast PS/2 methods being available, but none works to disable A20. IMO if A20 cannot be disabled in real-mode, emm386 shouldn't try to emulate A20 disable in v86-mode. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] 2nd FreeDOS 1.0 Testing release
This is my experience so far: First attempt I tried to install on a pretty small partition (QEMU) where MS-DOS 5.0 was already installed. The installation very soon stops due to insufficient hard disk space (although nothing is told, you just see no more progress on the screen). After that the partition is unusable, one can no longer boot from it :(. This issue is reported to Bugzilla already. Second attempt I created a new partition image with QEMU, size 16 MB and installed FD here. I got through FDISK and Format and this time the installation succeeded. Now I would like to mount another image as second HD. It is already formatted as an FAT16 extended partition. No problem to access it with MS-DOS as D:. But FreeDOS now tells while booting: ... CuteMouse v1.9.1 alpha 1 [FreeDOS] Installed at PS/2 port c:\Remove diskette in drive A: Insert diskette in drive B: Press the any key to continue ... Error reading from drive B: DOS area drive not ready (A)bort, (I)gnore, (R)etry, (F)ail? and that was it [btw. where is the any key? ;-)] PS: this is how qemu 0.8.1. is started: qemu -L bios -m 128 -hda freedos2.img -hdb drive_d.img - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos Future
Without a true SB card, I can't duplicate the problem, but I would strongly bet against the Windows-introduced and flavored GEMMIS being used in any meaningful (or at least critical) manner by DOS4G -- or any other DOS extender of notable popularity. Function 4a15h is much more likely, although until two weeks ago I had never verified that anyone actually used the function on a live application. It would be pretty easy to test DOS4G, however. Run a DOS4G application under a debugger, trap the int 2fh interface, and breakpoint on condition ax=4a15h. Unfortunately, I believe this approach will not work here in the absence of a SB card, since card detection and branch past unsupported code likely occurs prior to any I/O permission setup via 4a15h. I was advised (thanks Eric!) that there exists a SB option for FD-Emm386. Setting this option indeed cures the SB MPU issues for the protected-mode games I tried. So the int 2f, ax=4a15 interface obviously is not used, and from how it is designed it may be restricted to emulate hardware for real-mode apps only. OTOH, the SB drivers work for any kind of apps (if they *do* work). - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos Future
But: DOOM does work with the current himem/emm386. As for me this is true for the newest versions of himem/emm386 (July 2006) only. In fact, any DOS4G application didn't work with FD-Emm386 previously because my machine has 768 MB. And do work doesn't mean works well. For example, the MIDI music played in Doom sounds strange with FD-EMM386 on my SB-Live card. My guess is that this is due to missing interfaces in Emm386 (apart from the obscure GEMMIS interface), for example the documented I/O trapping interface (int 2Fh, ax=4A15h). - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] C compilers.
Digital Mars --- 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=lnkkid=120709bid=263057dat=121642 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
