Re: [Freedos-devel] Kernel 2037 actually available
Blair Campbell wrote: > Ok, I took the time to upload proper kernel pacakges to > www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/kernel/ > > as kernel2037-binary.zip and kernel2037-source.zip > > Enjoy > > PS: They contain Eric's QB 4.0 compatibility fix. Thanks, What is the difference between this kernel and the one you used in your last testing-iso? Is it only Eric's patch? Erwin - 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-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] 1.0 Just around the corner.
Hi Arkady, > EV> I would like to ask on the status of 2 allready mentioned > EV> issues on this list: > EV> -2- PATH problems > EV> Some commands can not be found in the PATH. The behaviour seems > EV> rather erratic. Adding the extension usually solves the problem. > > Issue was that FreeCOM: > > - finds also directory names (this prevent to find correct program file, if > it resides later in PATH) > and > - for "cmd" FreeCOM finds "cmd." file/directory (this prevents to find > correct program file, like "cmd.exe", which resides later in PATH). Yes, that must be it! I only experienced it with HELP, MENU, VC and NET and all of these where also present as a dir. And it also explains why it sometimes did work fine, because I once used NET.EXE when there was no dir NET. Then it worked fine. It made no sense to me, but now it does. Thanks. > This fixed with my patch, already present in CVS. Ask Blair, how to download > recompiled FreeCOM. I will just wait for next ISO by Blair. I have no reason to distrust your patch. :-) Erwin - 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-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] 1.0 Just around the corner.
Blair Campbell wrote: > After finally resolving that Florian's hard disk trashing problem was > related to LBACache, I think that 1.0 can be released as long as > LBACache isn't loaded during the install process. That is good news indeed! Kudos to all contributors of the upcoming 1.0 release! Especially in the last months great progress has been made towards this milestone. ... ... > Since FreeCOM 0.84pre2 has become quite stable recently, it will be > included, and 0.82 pl3 MIGHT find its way in as a backup in case any > users would prefer legacy (but possibly better-working) versions. I would like to ask on the status of 2 allready mentioned issues on this list: -1- 'map_cluster: empty' With almost every redirection (piping) this is printed to screen. BTW, Eric Auer's kernel released on 2006-07-26 does not seem to be affected by this. -2- PATH problems Some commands can not be found in the PATH. The behaviour seems rather erratic. Adding the extension usually solves the problem. I tested the new FreeDOS stuff (upto and including emm386 2.23 release) with my lengthy batch-routines on the NwDsk boot disks. These disks are based on http://www.nu2.nu/bootdisk/network/ See http://www.veder.com/nwdsk/#images for older 3.35 releases. Currently everything runs fine on the NwDsk 3.40 betas except for the 2 problems mentioned above. The PATH-problem is only happening with some commands: HELP, MENU, VC, NET. HELP, MENU, and VC are batch-files, NET is NET.EXE the Microsoft network-utility. When called with extension they work, when called without they do not work: 'Bad command or filename - "vc"'. The set of updated FreeDOS-components seems far more compatible to different hardware and 3rd party software. However the PATH-problem would be a show stopper for me including 0.84pre2 with upcoming new NwDsk release. End users should just be able to type HELP, MENU, or NET to get a proper response. BTW the NwDsk 3.40 betas (e.g. all their batch-files) run fine on MsDOS 6.22, MsDOS 7.10 (W98se), OpenDOS (DrDOS by Udo Kuhnt), and FreeDOS-pre-pre-1.0. FreeDOS-1.0 vastly improves compatibility with respect to the previous FreeDOS used (kernel 2006-04-28, freecom 2006-01-06, emm386 2005-11-28) but triggers the 2 mentioned problems. Just tell me there is a new kernel/freecom that I can test addressing these issues ... ;-) Erwin - 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-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Test (ignore)
Testing ... Erwin - 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-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] [TEST]
> List quiet or...? > Aitor Or all are waiting for "Urbi et Orbi" ... Erwin --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Re: XMS Manager on '286
On 16 Mar 2005 at 7:39, Michael Devore wrote: > I'm 684 lines of new code into a EMM386 revision to support dynamic > EMS/VCPI pool-sharing with XMS, with probably more than that many new !!! > lines of code left, plus at least several hours debugging. Where can I send the Cohiba? :-) Erwin (with his NwDsk/NIOS torture disk ;-) Erwin Veermans[EMAIL PROTECTED] Department of Social Psychiatry, University of Groningen P.O. Box 30001, 9700 RB Groningen, The Netherlands Fax: +31 50 3619722, Tel: +31 50 3612079 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] UDMA2 poll
> I had contact with Jack Ellis, and he claims that there are NO systems > (that he knows about), where UDMA leaves it in a unusable state. maybe > it won't work(accelerate), but at least it doesn't break the system. > So UDMA could be used as default driver on ANY system. > > are there ANY reports, that a fairly recent version of UDMA(2) leaves > the system in an unusable state? Erwin ? Nope. I must say I am impressed with the whole line of recent updates. The only problem I experienced and reported was the "FOOLISH disk-select bug" from 1.7 as Jack calls it. All later versions, even the 2.0-early-betas that Jack questioned himself, ran fine on my (multi-HD) systems. Also I could not duplicate Bernd's VMware no-harddisk-bug. Looks like a VMware 5beta issue and not UDMA's. Did not hear anything on UDMA from my end-users yet. Some solid piece of programming. Kudos to Jack! Erwin P.S. Using 2.0 "UDMA2.SYS /L /S" with UMBPCI.SYS 2.63 --- 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-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] UDMA2 poll
Thank you Bernd for steering this good effort by Tom away from semantics and back on track. @Tom I will send you any info on non-working hardware I get from my NwDsk end-users. Since I provide an escape-option in config.sys to choose when experiencing errors like this, the response might be low due to end-users successfully using this workaround. @Bernd On VMware 4.5.2 without harddisks defined I do not duplicate your problem. I get a proper message by UDMA2 (/L /S) that there are no harddisks so it got nothing to do and won't load. Erwin > > Hi! > > Where? > > in a previous message. Tom wants to collect results about UDMA2.SYS > compatibility. It's a driver to set IDE devices (not ATAPI, only IDE) > from PIO into UDMA mode. > Result will be usefull for his own software (partition imaging product), > but also for FreeDOS community. > > > te> one VERY important thing: what information to provide. > > > > For what? > > Testing report about compatibility between UDMA2.SYS and the physical > system that the user tests this driver on. > > > > "UDMA" - as some driver? From which URL I may get this driver? > > http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/udma/devel/udma2_20.zip > (93KB) > > > te>AMD/Intel CPU > > te>approximate age > > > > Age of who/what? Mine? Shiping date of case, CPU, mboard? Date of their > > manufacturing? Date of "releasing" press-release? > > age of complete computersystem I think. Incompatibility with new system > should indicate that you ask your BIOS manufacturer for a new BIOS which > fixes things. Incompatibility with an ancient computer shows that > UDMA2.SYS driver might need more workarounds. > > > te>and - of course - GOOD, BAD, HARMLESS > > > > May you explain, what you poll? > > poll about how compatible UDMA2.SYS driver is with the system. > GOOD : loads correctly > BAD: crashes system or makes it unstable > HARMLESS: aborts safely on error > > My example: using UDMA2.SYS in VMware emulator, with no harddisk in that > emulated environment, causes "Bus-Master setup BAD; driver NOT loaded!" > message, instead of "No disks to use; driver NOT loaded!" > > That's an emulation error, probably. > I've also noted that UDMA2 might help with the VDS feature of EMM386 > driver, but I probably should check that again. > > Bernd Erwin Veermans[EMAIL PROTECTED] Department of Social Psychiatry, University of Groningen P.O. Box 30001, 9700 RB Groningen, The Netherlands Fax: +31 50 3619722, Tel: +31 50 3612079 --- 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-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] USBASPI.SYS and EMM386
> If there is anybody who has tried to use USBASPI.SYS and EMM38, has > had USBASPI.SYS reboot immediately with EMM386 loaded, AND wants to > try a test EMM386 to get around the reboot, let me know and I'll send > on a copy for you to try. Well, stupid of me I did not test that on my images. Because it indeed fails. I use the 2.06 version of usbaspi since that one will auto-unload when no USB-device is present. I experience a "freeze" when trying to detect an USB-device. When no USB-device is present it will just unload usbaspi, and there is no problem. I do not experience a reboot. > I don't have a USB drive, so can't test here beyond the reboot > workaround. And the workaround masks the problem instead of fixes it, > so no promises of a major breakthrough. Yes, I would like to try it. Erwin > But heck, it might work. --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] VDS fail
> Forget trying that test. EMM386 turns off VDS when all UMB's are > excluded. That's what the common people call a "bug", programmer > cliche' calls a "feature", and sophisticates like me call > "unauthorized code modification by a dog when my back was turned". > > I'm going to make my dog fix it, though. ROFL Erwin --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] "LH /L: someprog" sets errorlevel 95 (on success)
Last fix in FreeCOM CVS (changed revision 1.155): "fix: LH: Errorlevel of program effects LH's error reporting" might indeed have improved the sometimes erratic errorlevel set by loadhigh (no tests done yet), but it introduced a new problem. The trick to force-loadlow a program that tries to load itself into UMB by "LH /L: someprog" now produces errorlevel-95 upon success. FreeCOM's revision just before this patch (changed 1.154) does produce the expected errorlevel-0. The wrongly set errorlevel 95 suggests that CBREAK_ERRORLEVEL is accidently set or triggered (CTRL+C, DOS error code interrupted system call) upon success. >From last config.h: /* Use this errorlevel if an external program was terminated by ^C or ^Break --> DOS error code interrupted system call */ #define CBREAK_ERRORLEVEL 0x5F I hope this info may help in solving this problem. Erwin --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Compiling XMS-SWAP FreeCOM: almost ...
> > You're doing nothing wrong here as far as I can see. The source is > > too big now to fit in 64k. Large model is a work around but then > > you'd need a suppl_l.lib. > > The simplest workaround is to use > CC = $(BINPATH)\TCC +$(CFG) -1 > in config.mak. It makes command.com unusable on 8088s but for the > xmsswap version that's not an issue (as XTs don't have XMS anyway). > > Bart > Thanks, that did the trick! That would imply it is always better to compile xms-swap version for CPU > 8088 ? So here I recap compiling FreeCOM for mere mortals. - Get and install Nasm (16bit, minimum version: 0.98.35) http://sourceforge.net/project/showfiles.php?group_id=6208 - Get and install TurboC++ 1.01 http://community.borland.com/article/0,1410,21751,00.html - Get and unzip latest FreeCOM CVS http://fdos.org/kernel/freecom.HEAD.zip - Get and unzip Suppl to .\Freecom\Suppl2 http://freedos.sourceforge.net/freecom/packages/suppl.zip - Copy Config.std to Config.mak (in .\Freecom) - Address following in Config.mak: CC_BASE_PATH = C:\TCPP101 (substitute your path) NASM = nasm.exe (substitute your path) SUPPL_INC_PATH = ..\SUPPL2 - Insert in Config.mak after "CC = $(BINPATH)\TCC +$(CFG)" !if $(XMS_SWAP) CC = $(BINPATH)\TCC +$(CFG) -1 !endif - Create empty file "skip" in .\Freecom\Suppl Now (re)create your Command.com from .\Freecom with "build -r", and xms-swap version with "build -r xms-swap" Keep a copy of Suppl.zip and your Config.mak at hand when you decide to delete all Freecom sources before upgrading with a new Freecom-CVS-zip. Erwin Veermans --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Compiling XMS-SWAP FreeCOM: almost ...
While not qualified as a hardcore DOS programmer I am trying to compile FreeCOM and I never got so close as this time so maybe someone can help me out here ... I downloaded and unzipped current CVS-freecom: http://fdos.org/kernel/freecom.HEAD.zip (2004-11-05) I installed Tcpp101 and NASM 0.98.36 I adjusted the paths in config.mak for TCPP and NASM. I run build.bat and it halts almost immediately in .\suppl "suppl.tgz: bad compression data" (after it first produces some warnings on untar) It seems there might be a workaround so I follow that. I download an alternative Suppl from: http://freedos.sourceforge.net/freecom/packages/suppl.zip extract this to .\Suppl2, adjust the path for Suppl in config.mak and create a file "skip" in .\Suppl as instructed. Now I try "build" again. Bingo! Some warnings here and there but in the end there is a fresh command.com produced ! One step away from my goal: xms-swap-command.com. So I run "build.bat -r xms-swap". It also seems to go all the way but in the end it chokes in .\shell: "Error: segment _TEXT exceeds 64K" (repeated 4 times) Command.map starts with: Warning: __fstpcpy defined in module FSTPCPY.OBJ is duplicated in module FSTPCPY Warning: _exit defined in module cswapc.c is duplicated in module EXIT Warning: _putenv defined in module ENV_PUT.OBJ is duplicated in module PUTENV Error: Segment _TEXT exceeds 64K Error: Segment _TEXT exceeds 64K Error: Segment _TEXT exceeds 64K Error: Segment _TEXT exceeds 64K Start Stop Length Name Class 0H 1008FH 10090H _TEXT CODE 10090H 10090H 0H _FARDATAFAR_DATA .. What can I do about this to finally compile my xms-swap command.com? Thanks, Erwin --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] DOS=HIGH failure on latest kernel
I gathered some info on the DOS=HIGH failures reported earlier on this list and entered it at Buzilla under 1842. http://www.freedos.org/bugs/bugzilla/show_bug.cgi?id=1842 Erwin --- 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-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Kernel DOS=HIGH Failure (Was: the HTMLHELP problem)
I would suggest to point our attention to the Kernel here. I received emails of NwDsk-users complaining that my boot disks hang when using "DOS=HIGH". According to one user FreeDOS fails on an IBM ThinkPad T40 when using "DOS=HIGH" in config.sys. Another user reports that FreeDOS bootdisks fail on VMware 4.5.x when using "DOS=HIGH". I cannot confirm this myself, since on my hardware there are no problems. But combined with the remarks here by Bernd (see below) I am starting to beleive we have a problem with moving Kernel stuff to HMA. Anyone with a Thinkpad that can verify here? Erwin > I can confirm Jeremy's conclusion that DOS=HIGH affects HTMLHELP. I > changed DOS=HIGH,UMB into ;DOS=HIGH DOS=UMB ... snip ... > I am not sure why DOS=HIGH, XMS-driver or A20 (BIOS A20 method is used > in Vmware) have any effect. clean-boot ofcourse does not have any > HIMEM or DOS=HIGH setting. ... snip ... > btw, are we dealing with a kernel issue or a program issue here? --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Re: Buy a PC with FreeDOS
... snip ... > is definitely ignored by DOS. Did anybody test if HIMEM can handle > more than 2 GB RAM, by the way? Or are there problems even below that? I used HIMEM.EXE on 2 GB machines. It works fine, although I choose to limit it to 1GB with the MAX= parameter because it was more likely to run out of handles. I settled for "/numhandles=64 /max=100" on my boot disks, assuming that "1GB should be enough for anyone" paraphrasing a certain Basic programmer;-) Erwin --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] EMM386 enhancement, plus cosmetic HIMEM change
> >I created a barebone image for you to reproduce the problem, > >but I need to know which nic-driver I need to add for you > >(nic name or ven/dev-ID would be fine) > > As a future time I may look at expanding VDS support to allow known > problematic network drivers in upper memory, so if you can send > something which demonstrates the problem, that would be good. The > files should provide a way to definitively detect that things are > failing, if a crash isn't evident. > > The FreeDOS machine has a VIA Rhine II Fast Ethernet Adapter according > to XP device manager. Red Hat calls it a VT6102 (Rhine II). I hope > that lies within the realm of your known card drivers. Yes, this one is in my collection of 40+ drivers. I left my diskette with the above setup at work so I will send it to you when I get there (next week) or when I succeed in reproducing it on the fly. Erwin -- Erwin Veermans <[EMAIL PROTECTED]> Psychiatry RuG, PO Box 30001, 9700 RB Groningen, Netherlands --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] EMM386 enhancement, plus cosmetic HIMEM change
> > I am experiencing troubles with EMM386 on WATTCP > > applications over 16bit ODI + ODIPKT packet driver. > loading high network drivers isn't supported by emm386 > standard due to missing VDS support. > depending on the protokoll layer above (and a couple of other things), > it might also be nessessary to load the protokoll driver low. Aha, I see. Yes, only after I "loadlow" LSL.COM (Link Support Layer) and "loadlow" my nic things work again. So I conclude that UMBPCI has a very different approach which does not raise all these implications but at the price that it is very chipset dependent, where EMM386 follows a generic line (aiming hardware independence) but having to fullfill far more issues (VDS, DPMI/EMM/XMS memory pooling, etc.) The thing is that network clients plus drivers are usually used as a ground layer and not as the end goal, so I try to be cautious with resources. Many applications that need to surf on a network client (Citrix ICA for DOS, Arachne, Powerquest Image, etc...) can be quite hungry for conventional memory. > if the drivers are real clever, and auto-loadhigh themself, use > > LH /L: load network driver Yes, that is a nice trick. Erwin --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] EMM386 enhancement, plus cosmetic HIMEM change
> Uploaded to ftp://ftp.devoresoftware.com/downloads are the files
> emm386.zip and himem.zip containing uncompressed executables of,
> respectively, EMM386.EXE and HIMEM.EXE, plus the source files modified
> in this latest version.
Michael,
I am experiencing troubles with EMM386 on WATTCP
applications over 16bit ODI + ODIPKT packet driver.
Also your latest EMM386 did not solve this.
When using NO UMB-manager at all, or using UMBPCI.SYS
everything works fine. When I use EMM386 ("noems x=test")
the WATTCP applications fail (DHCP/BOOTP failed, PING
failed). Also sometimes the loading of the 16bit nic driver
sometimes fails when loading high. These problems I could
reproduce on several machines (different nics) and did
not happen without UMB-manager or with UMBPCI.
I created a barebone image for you to reproduce the problem,
but I need to know which nic-driver I need to add for you
(nic name or ven/dev-ID would be fine)
Erwin
BTW This has no link with the unresolved NIOS problem
(NIOS needs EMM/XMS memory pooling). NIOS is from
32-bit Novell client. Above problem is from 16-bit client.
---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
___
Freedos-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] members.cox.net/dos and newdos.yginfo.net gone?
> Hi, it seems that the nice DOS pages > > http://members.cox.net/dos/ Mirrored (on 3 continents) by: http://short.stop.home.att.net/ Erwin --- 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-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Command.com 0.82pl3e-w: Mem.exe reports "UMB corruption"
I am very pleased with ongoing Command.com development and improvements made, but I encountered a problem related with or revealed by Bart's MEM.EXE. When booting with latest kernel (2035 or Arkady's) plus Himem.exe plus Emm386 and using xmsswap-command.com 0.82pl3e or higher, MEM.EXE fails and reports: UMB Corruption. I do not know if UMB is really corrupted by command.com or that this is cosmetic, but either way it affects me because I use the output of MEM.EXE to signal if certain TSRs or drivers are loaded. Obviously this does not work anymore with 0.82pl3e or higher. The official 0.82pl3 is working fine so it should arise from first changes implied on 0.82pl3. Erwin --- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] A000 to A001 possible change
> Alright, I'm a bottom-line kind of guy. Do you think we should > > A. remove the A000 -> A001 code (Arkady preferred) or > > B. not remove the A000-> A001 code (status quo) or > > C. don't care? > > I'm neutral unless more than one other person supports removing the > code. I cannot oversee compatibility issues here and my interest would be that whatever is choosen it should be most compatible for most hardware around. So would it be an option to add an Arkady-A000 switch that will skip the A000->A001 ? Everybody happy? Erwin --- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] "copy . c:" fails. Kernel or Freecom?
> > Yep, the "copy . c:"-failure ("heap corruption") which seemed to
> > have been present in freecom for a long time has been fixed already
> > by Tom by his 1.129-fix (03-05-2004). In fact it was discussed
> > already in Bugzilla #556. Both the "q" and "r" revisions of 0.82pl3
> > carry the fix.
> >
> > Erwin
>
> thank you for notifying me.
> Should have checked more often before requesting a newer version from
> Steffen (again..).
>
> any idea if Bugzilla reflects these changes? (now closed bug reports
> for example)?
See: http://www.freedos.org/bugs/bugzilla/show_bug.cgi?id=556
(resolved since revision 'p')
BTW, that is why I started this thread. I could not find this bug
under the "unresolved"-bug-entries (it was fixed already by then)
while I did not find a freecom binary revision under dir "testing"
that included the fix. And unfortunately compiling your own
freecom binary is not as straight-forward as compiling a kernel
from the daily-tar, for a non-hardcore programmer like me :-/
But now it is there with the "q" and "r" versions. Would be great
to have interim revisions on par with the submitted fixes.
> hope you like the 2035 kernel for your Nwdsk project.
Yes, but I am again wrestling with EMM386 and NIOS. Though
it looked like a closed case it now turns out that Ghost
(which is main application for NwDsk users) will not run
on the combination of EMM386, XMSDSK and NIOS, due
to the fact that NIOS needs to get its feet into first part
of XMS. Michael is looking for a dirty fix to keep NIOS on
board here while honoring DPMI requests by apps like Ghost.
Erwin
---
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
___
Freedos-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] "copy . c:" fails. Kernel or Freecom?
> > A well known alternative for '*.*' is to use '.' with 'copy', like:
> > 'copy . c:' This works fine with MsDOS and DrDOS (OpenDOS) but fails
> > on FreeDOS with every kernel (2026b - 2035) and freecom (0.82pl1 -
> > 0.82pl3k) I tried (clean boot, no himem/emm386). This dot-shortcut
> > is used a lot in batch-files on DOS so I think this deserves a
> > Bugzilla entry. Would this be a Kernel or a Freecom issue ... ?
>
> maybe fixed in CVS? see:
> http://cvs.sourceforge.net/viewcvs.py/freedos/freecom/CHANGED?only_with_tag=MAIN
Yep, the "copy . c:"-failure ("heap corruption") which seemed to have
been present in freecom for a long time has been fixed already by Tom
by his 1.129-fix (03-05-2004). In fact it was discussed already in
Bugzilla #556. Both the "q" and "r" revisions of 0.82pl3 carry the fix.
Erwin
---
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
___
Freedos-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] "copy . c:" fails. Kernel or Freecom?
Hi Tom, Bernd just pointed me on the CVS of Freecom and I saw your fix 1.129 there "copy c: d:" "heap corruption". Since the "copy . c:" failure also leads to "heap corruption", could you verify if "copy . c:" on your 1.129 revison of command.com works? I will educate myself a little here and try to work my way through the 10 Steps of How to Compile Freecom, but you might have the answer whether you tackled this already with your 1.129 right at hand ... Erwin > Hello Erwin, > > > A well known alternative for '*.*' is to use '.' with 'copy', like: > > 'copy . c:' This works fine with MsDOS and DrDOS (OpenDOS) but fails > > on FreeDOS with every kernel (2026b - 2035) and freecom (0.82pl1 - > > 0.82pl3k) I tried (clean boot, no himem/emm386). This dot-shortcut > > is used a lot in batch-files on DOS so I think this deserves a > > Bugzilla entry. Would this be a Kernel or a Freecom issue ... ? > > Freecom > > tom --- This SF.Net email is sponsored by: GNOME Foundation Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event. GNOME Users and Developers European Conference, 28-30th June in Norway http://2004/guadec.org ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] "copy . c:" fails. Kernel or Freecom?
A well known alternative for '*.*' is to use '.' with 'copy', like: 'copy . c:' This works fine with MsDOS and DrDOS (OpenDOS) but fails on FreeDOS with every kernel (2026b - 2035) and freecom (0.82pl1 - 0.82pl3k) I tried (clean boot, no himem/emm386). This dot-shortcut is used a lot in batch-files on DOS so I think this deserves a Bugzilla entry. Would this be a Kernel or a Freecom issue ... ? Erwin --- This SF.Net email is sponsored by: GNOME Foundation Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event. GNOME Users and Developers European Conference, 28-30th June in Norway http://2004/guadec.org ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] LBAcache update - bigger changes
Hi Eric, >Syntax for the size info changed, too: If you select a size in range >1..99, it will select a cache size of 1/4..99/4 MB. If you select a >size in range 100..32767, however, it will be rounded up to a >multiple of 128k (but not reach 32768k). Yes, you can now give the >size in kilobytes if you want :-). I was about to ask you for this. Now I can write my caching code generic for OpenDOS, MsDOS and FreeDOS (I mean regarding the cache size). Thanks, Erwin --- 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-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Intel PRO/1000 driver fails under FreeDOS
> With FreeDOS (ke2034_32), it crashes as I described: The driver loads, > but when tinyrfc.exe tries to obtain a DHCP lease, it gets an invalid > opcode. Wild guess: Did you try "switches=/E" in config.sys? Some people were reporting issues with latest kernel that could be reverted with the /E-switch. Browse this list for more info ... Erwin --- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] HIMEM w/XMSDSK 2G resolution
> Even at 4G max, the number of handles XMSDSK could need is 64, plus > the HIMEM overhead for itself and EMM386 of 2 or 3. Accordingly, I am > probably going to increase the default setting of HIMEM XMS handles to > 72. I would welcome 72 for default as you may anticipate from our discussions on getting XMSDSK to work on large ram. Erwin --- 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-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] NRV secret revealed. It went to Mars but not to Earth
> Today, Markus Franz Xaver Johannes Oberhumer > launched his new site at last (after NRV marsed)! Lucho, You always make my day when you quote Herr Oberhumer's full name. Someway somehow it evaporates some of the 'heaviness' associated with the compression & GPL discussion. But not for long so keep quoting him from time to time ... ;-) Erwin --- 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-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] EMM38664.EXE compatibility
> I tested it with Descent 1. I couldn't install it in dos, I forget > what the error message was, but when I installed it in Windows, then > booted into dos, it worked fine, with & without "noems". I've got to > figure out how to slow the game down though because on a 1.8 ghz, it > runs to fast. Slowdown: http://members.cox.net/dos/misc02.htm#slowdown Erwin --- 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-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Test for anybody with MS/DR-DOS
> ftp://ftp.devoresoftware.com/downloads A: Test machine 440BX 512 MB (brand A) B: Test machine 440BX 256 MB (brand B) - OpenDos 7.01: - OpenDos 7.01 (DrDos) EMM386 NOEMS on A: Reported INT 67h value of 025C:006B EMS function 40h, Get Status, failed EMS function 41h, Get Page Frame, failed, address h EMS function 42h, Get Number of Pages, failed, total 0h, unallocated 0h EMS function 43h, Allocate Handle and Pages, failed, handle 0h EMS function 46h, Get EMS version, failed, version 0.0 - On B only 67h different: Reported INT 67h value of 0258:006B - MsDOS: - MsDOS 6.22 HIMEM + EMM386 NOEMS on A: Reported INT 67h value of 0C7E:02B0 EMS function 40h, Get Status, successful EMS function 41h, Get Page Frame, failed, address 4000h EMS function 42h, Get Number of Pages, successful, total 818h, unallocated 800h EMS function 43h, Allocate Handle and Pages, successful, handle 1h EMS function 45h, Release Handle and Pages, successful EMS function 46h, Get EMS version, successful, version 4.0 - On B only 67h different: Reported INT 67h value of 0C71:02B0 - On DOS-W98se HIMEM + EMM386 NOEMS only 67h different on A: Reported INT 67h value of 0296:0270 - On B on DOS-W98se only 67h different: Reported INT 67h value of 0295:0270 It looks like OpenDOS (DrDOS) performs a more serious NOEMS than MsDOS Erwin -- Erwin Veermans <[EMAIL PROTECTED]> Psychiatry RuG, PO Box 30001, 9700 RB Groningen, Netherlands --- 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-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] EMM386 with VCPI for testing
> >> > -dc820:0 2 > >> It reads FF FF FF > > ok. that'll be the unmapped space then. It looks like Lucho is right > > and you have a tiny 512 byte sized signature "EPROM" at c800:. > > That'll be easy to fix. > > But it's very strange to have such a tiny piece of uncompressed ROM! > Erwin, please test more bytes from C820:0 than just 3 bytes. It's > possible that the ROM module there has "holes". It's also possible > that it reports just its first 512 bytes as its size but its *actual* > size is much larger. Finally, it's (at least theoretically) possible > that all the first 512 bytes are all ones (FF) and the REAL code > starts after them, to avoid having to update the checksum after a > change (completely violating the purpose of the ROM scan which should > check this checksum ;-) I ran "-dC000:0 " to get some overview here: C000-C7FF looks to be my 32k Video bios (starts with 55 AA 40, shows string "VGA Coompatible BIOS") C800-C81F indeed has something to do with the extra UDMA (starts with 55 AA 01, shows string "HIGHPOINT", no FF's) C820-CFFF is empty (all FF) So could it be that the HIGHPOINT UDMA jumps to somewhere else for its payload ? Erwin -- Erwin Veermans <[EMAIL PROTECTED]> Psychiatry RuG, PO Box 30001, 9700 RB Groningen, Netherlands --- 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-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] EMM386 with VCPI for testing
> >When I add /verbose I see > > 'EPROM at c800:, size 0 KB' > >endlessly scrolling by ... > > Okay, so you're having problems with the EMM386 startup then. I > didn't mess with the memory scanning portion of the original code, but > looks like it needs to be updated for location of EPROMS. Can you try > the /X= parameter of EMM386 to exclude that portion of memory where > the EPROM is located? If so, let me know whether it fixes anything or > causes different problems. X=C800-CFFF and even X=C000- fail. (same message scrolling endlessly) And yes, this always failed on earlier EMM386. I always figured EMM386 unstable and choose UMBPCI. If I read Bart's reply correctly it should be lines 183-190 in EMM386.C where the "1" read at my c800 vanishes as zero (1/2). Erwin -- Erwin Veermans <[EMAIL PROTECTED]> Psychiatry RuG, PO Box 30001, 9700 RB Groningen, Netherlands --- 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-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] EMM386 with VCPI for testing
> > > > When I add /verbose I see > > > >'EPROM at c800:, size 0 KB' > > > > endlessly scrolling by ... > > > > > > try booting without emm386 and then: > > > c:\>debug > > > -dc800:0 2 > > > If it says 55 AA 00 then something is very weird. > > > > It says 55 AA 01 > > Is that "avarage" weird ? > > So I would have 0x01*512 = 512byte video Bios > > Wouldn't that be a little low (understatement). > > yes, indeed. The code is in emm386c.c, easy to see where: it divides > 1/2 which becomes 0. This code could be changed to check every 512 > bytes for a ROM instead of every 2k, and to avoid this division. > > The value for a 64k bios should be 0x80. Not sure about 128k (that's a > little high) but what is the real size of your BIOS? 256k > Please check: > c:\>debug > -dc820:0 2 It reads FF FF FF > (i.e. 512 bytes later) Perhaps your BIOS is split. There is an integrated highpoint IDE UDMA controller next to the "normal" IDE on this 440BX. Could this be referenced at c800 and misunderstood by EMM386 as being 0 ? Erwin -- Erwin Veermans <[EMAIL PROTECTED]> Psychiatry RuG, PO Box 30001, 9700 RB Groningen, Netherlands --- 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-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] EMM386 with VCPI for testing
Hi bart, > > When I add /verbose I see > >'EPROM at c800:, size 0 KB' > > endlessly scrolling by ... > > try booting without emm386 and then: > c:\>debug > -dc800:0 2 > If it says 55 AA 00 then something is very weird. It says 55 AA 01 Is that "avarage" weird ? > I have 55 AA 40 at c000: which means: here's an "EPROM" (video > bios) of 0x40*512 = 32K. So I would have 0x01*512 = 512byte video Bios ???? Wouldn't that be a little low (understatement). Erwin -- Erwin Veermans <[EMAIL PROTECTED]> Psychiatry RuG, PO Box 30001, 9700 RB Groningen, Netherlands --- 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-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] EMM386 with VCPI for testing
Hi Michael, VCPI that would be great! But on my test-board (440BX) that I use for testing my NwDsk boot disks EMM38664.EXE immediately hangs my machine. My config: Kernel 2033, 0.82pl3, Himem64 3.10 dos=high,umb stacks=0,0 files=99 lastdrive=z buffers=-32 When I add /verbose I see 'EPROM at c800:, size 0 KB' endlessly scrolling by ... Himem(64).exe & Umbpci.sys allways worked on this machine. Any clues? Erwin -- Erwin Veermans <[EMAIL PROTECTED]> NwDsk: NetWare Boot Disk (IP/IPX) <http://www.veder.com/nwdsk/> NwDskPe: NetWare Client for WinPE <http://www.veder.com/nwdskpe/> --- 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-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] FreeDOS people list
> I've been working on a contributor's list (wow ... hard to do since > some people have too little information, maybe they want to keep > low-profile). > > Please take a look and comment, try my best to improve. > > http://johnson.tmfc.net/freedos 'I wonder where Nagyd (mouse driver, SSH software) and some of the others are from...' Nagyd: Hungary (Daniel Nagy) Contact him at http://www.aefdisk.com http://www.masterbooter.com -- Erwin Veermans <[EMAIL PROTECTED]> Psychiatry RuG, PO Box 30001, 9700 RB Groningen, Netherlands --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Re: UDMA as base?
> > But if freedos-devel disagrees that UDMA belongs in 'base', I'll > > move it back to 'util'. What's the rest of the list say? Where > > does it belong? Base ! >From time to time I get end-users of NwDsk complaining that UMBPCI "does not work", where I explicitly have options in my Config.sys-menu to load with/without UMBPCI and with/without UDMA (defaulting to: with UMBPCI, with UDMA). I am still waiting for the first complaint of an end-user that NwDsk "does not work" because of UDMA. I consider UDMA as very few bytes very well spent and an enrichement to FreeDOS. Thanks Jack & Lucho for this fine piec of work. Erwin -- Erwin Veermans <[EMAIL PROTECTED]> NwDsk: NetWare Boot Disk (IP/IPX) <http://www.veder.com/nwdsk/> NwDskPe: NetWare Client for WinPE <http://www.veder.com/nwdskpe/> --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Executable compression
> FreeDOS command.com UPX 66.426 byte > FreeDOS command.com aPack63,818 byte > FreeDOS command.com aPack -1 63,766 byte > FreeDOS command.com aPack -2 63,791 byte > FreeDOS command.com aPack -3 63,799 byte > > tom For someone like me struggling to pack as many as possible on a boot disk, aPack is very appealing! I hope the licensing issues with Joergen work out well. Erwin -- Erwin Veermans <[EMAIL PROTECTED]> NwDsk: NetWare Boot Disk (IP/IPX) <http://www.veder.com/nwdsk/> NwDskPe: NetWare Client for WinPE <http://www.veder.com/nwdskpe/> --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] XMS + UMB + DPMI ?
> Right. So here are my questions. First, is there some better > combination of utilities I should use? Second, what am I losing, > exactly, by using umbpci.sys instead of emm386.exe? And finally, how > come cwsdpmi doesn't work with emm386.exe? I can share my experience with FreeDOS memory managment as I have been using it with my NetWare boot disk project (NwDsk: http://www.veder.com/nwdsk ), allthough I lack the technical background to discuss the bit-level details. I use the combination HIMEM.EXE (now HIMEM64.EXE) for XMS/HMA (dos=high) and UMBPCI.SYS for UMB (dos=umb). NwDsk has grown popular among NetWare admins as starting point for imaging or unattended OS installs from NetWare servers. As such it is used on a very wide range of hardware. HIMEM(64).EXE has proven to be very reliable. Thanks, Tom! I only do get feedback from users about UMBPCI.SYS which unfortunately does not work with all chipsets. For that I provide a CONFIG.SYS with a menu in which they may choose to boot with (default) or without UMBPCI.SYS (with additional choice for UDMA.SYS). I am very pleased with Michael's intentions of tackling VCPI for EMM386 wich would make a good replacement for UMBPCI.SYS (VCPI being needed for NIOS.EXE). With 2 previous releases of NwDsk I side-stepped to FDXXMS.SYS but had to pay for that by having to answer a lot of email from my end-users complaining it was freezing NIOS.EXE on their hardware. Since I am back with HIMEM64.EXE things calmed down again ;-) Since the 32-bit NetWare client (NIOS) is loading in XMS the pain of having no hardware-independent UMB provider (UMBPCI is hardware dependent) is not that hard. It leaves enough for "winnt.exe". But from a general perspective I will swap UMBPCI for a non-hardware-dependent EMM386(64).EXE right away whenever it features VCPI. So far for my observations based on the feedback of my users concerning HIMEM(64), FDXXMS and UMBPCI. Erwin P.S. OpenDOS (DrDOS 7.01) has a full featured EMM386. For me it has 2 major concerns: it is too big for my boot-flop, and its license status is unclear to me (still open source ??). -- Erwin Veermans <[EMAIL PROTECTED]> NwDsk: NetWare Boot Disk (IP/IPX) <http://www.veder.com/nwdsk/> NwDskPe: NetWare Client for WinPE <http://www.veder.com/nwdskpe/> --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
