Re: [Freedos-user] EMM386 2.05 update, recommended for all
Hi Michael, This version of EMM386 has a number of compatibility changes Cool. While on the topics of VDS, the VDS option is now on by default. Too many environments require this to leave it as optional, plus a default on condition matches Microsoft EMM386. There exist SCSI setups which will REQUIRE you to turn off VDS support via the new NOVDS option. Unfortunately for those SCSI-ites, the people who need VDS outnumber the people who need to not have VDS, so they lost out. Or maybe the people who need VDS just yell louder. Ahh well, same difference to me. I like quiet. A better option would be to get to the bottom of why SCSI and VDS do not like each other. SCSI is a drive interface - I don't see how it can be affected by VDS unless there's something bigger going on. It may he SCSI is merely showing up the problem, as opposed to BEING the problem? the amount up to $60.00 and made the contribution on August 9, specified for where it was most needed with the title 'FreeDOS'. Confirmation e-mail available on request. Very nice, but I don't get it? You are spending hours developing this excellent Free software, and then paying out to charities based on it's popularity?? -- Gerry Hickman (London UK) --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] EMM386 2.05 update, recommended for all
Gerry Hickman schreef: A better option would be to get to the bottom of why SCSI and VDS do not like each other. SCSI is a drive interface - I don't see how it can be affected by VDS unless there's something bigger going on. It may he SCSI is merely showing up the problem, as opposed to BEING the problem? VDS being enabled by default *will* cause people to report any problems with SCSI setups. Previously VDS was omitted by default, so people would never find out there would have been an issue. the amount up to $60.00 and made the contribution on August 9, specified for where it was most needed with the title 'FreeDOS'. Confirmation e-mail available on request. Very nice, but I don't get it? You are spending hours developing this excellent Free software, and then paying out to charities based on it's popularity?? non-commercial programmers take their time to make their software as good as possible, there's no pressure except for the desire to make good enough (or even perfect) software. I'm glad Michael wants to deliver such quality and keeps improving these memory managers. The better the quality and reputation, the more downloads, the more testing, and more remaining issues exposed -- goto begin :) Michael's charity helps the charity itself, and it helps getting EMM386 more exposure and testing. As you can see from the changelog, most bugs seem to be detected by Michael himself. That's quite impressive, as most people are blind with regard to their own code, meaning their code is too familiar to look at it properly as a critic. Happy bughunting people, and thanks for the release, Michael :) --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] EMM386 2.05 update, recommended for all
At 11:21 PM 9/19/2005 +0100, you wrote: A better option would be to get to the bottom of why SCSI and VDS do not like each other. SCSI is a drive interface - I don't see how it can be affected by VDS unless there's something bigger going on. It may he SCSI is merely showing up the problem, as opposed to BEING the problem? Nope, there are documented instances of SCSI drivers being incompatible with VDS. In those cases, they share the same interrupt and potentially the same register values which VDS uses to determine its functions and what to do. Obviously if SCSI wants to read a disk sector and VDS thinks you want to check for contiguous memory amounts, something is going to wind up very unhappy. Is that what the problem is with your SCSI setup(s)? Can't say, good chance it's a failure elsewhere, or it could be the fundamental failure described above. If you want me to get to the bottom of your particular VDS failure, then you or someone else will need to send me a machine that demonstrates the problem, same as Mark Bailey did with his laptop. Otherwise, it's all conjecture here. the amount up to $60.00 and made the contribution on August 9, specified for where it was most needed with the title 'FreeDOS'. Confirmation e-mail available on request. Very nice, but I don't get it? You are spending hours developing this excellent Free software, and then paying out to charities based on it's popularity?? I was interested in knowing how many people overall, more or less, downloaded from my site for FreeDOS. The contribution served three purposes: 1) it motivated interested people to download the latest rather than wait for release+n like people tend to do; 2) it gave me a better baseline against people who solely hit the site to download files simply because they are there (BBS'ers used to call them file-rapers); and 3) it made a little money for a universally helpful charity that could use it. Oh, 3.5) I was bored and it was a mild diversion. And, 3.75) It gave me an excuse to start working with Perl and Cygwin-based utils a bit more to process the results, instead of coding something up in C/C++ overkill as I typically have done. --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] EMM386 2.05 update Bug Report
Michael Devore wrote: Uploaded to ftp://ftp.devoresoftware.com/downloads/emm386 are the files emmx205.zip, EMM386/HIMEM mostly executable package, and emms205.zip, EMM386/HIMEM mostly source package. This version of EMM386 has a number of compatibility changes to enhance operability with a variety of DOS applications and environments without the need for advanced option tweaking. As a result of the seven changes to EMM386 and two changes to HIMEM, this is a recommended released. Hi, This update breaks MEM. While it finally allows OpenGEM to work at the same time as my plug-n-play SoundBlaster AWE64, upon running the latest stable version of MEM, I get MEM: UMB Corruption. -Dan --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] EMM386 2.05 update Bug Report
Daniel Quintiliani schreef: This update breaks MEM. While it finally allows OpenGEM to work at the same time as my plug-n-play SoundBlaster AWE64, upon running the latest stable version of MEM, I get MEM: UMB Corruption. -Dan MEM (1.6) itself is broken, get 1.7beta or 1.8alpha both available at: http://wiki.fdos.org/Main/mem Please report back if that solves your UMB Corruption error or not. Bernd --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS on PC XT
Blair Campbell wrote: As you can see from my previous mailing list post, I do indeed have a pre-386 system with a CDROM. The above snip leads me to belive that the cdextensions file (though it runs on my XT) hasn't been debugged for that platform, and may not even be properly compiled (e.g. 386 optimizations)? Could any devs shed some light on this, perhaps? There is an 8086 version of SHSUCDX available, so you musn't use SHSUCDX to load the extentions, but you must instead use SHSUCD86 or something like this. I'm not sure if there are any drivers available for pre-386 systems, however. I'll try SHSUCD86 and see what happens. I'm not sure what you refer to by I'm not sure if there are any drivers available for pre-386 systems though. Do you mean the cdrom .sys driver file? If so, yes there are. I have one installed. - Nick --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS on PC XT
Nick Bright wrote: Blair Campbell wrote: As you can see from my previous mailing list post, I do indeed have a pre-386 system with a CDROM. The above snip leads me to belive that the cdextensions file (though it runs on my XT) hasn't been debugged for that platform, and may not even be properly compiled (e.g. 386 optimizations)? Could any devs shed some light on this, perhaps? There is an 8086 version of SHSUCDX available, so you musn't use SHSUCDX to load the extentions, but you must instead use SHSUCD86 or something like this. I'm not sure if there are any drivers available for pre-386 systems, however. I'll try SHSUCD86 and see what happens. I'm not sure what you refer to by I'm not sure if there are any drivers available for pre-386 systems though. Do you mean the cdrom .sys driver file? If so, yes there are. I have one installed. Correction to myself. I am assuming this driver works with the PC XT since the document I read indicates as such. - Nick --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] EMM386 2.05 update, recommended for all
Michael Devore wrote: Uploaded to ftp://ftp.devoresoftware.com/downloads/emm386 are the files emmx205.zip, EMM386/HIMEM mostly executable package, and emms205.zip, EMM386/HIMEM mostly source package. Firstly, I have not tested this new release. That said, what is the status with regards to having FastTracker II working on FreeDOS? My FreeDOS installation consists mainly of what was distributed with the Beta9 SR1 CD, so some of the components may be fairly old. I did however download your previous EMM386 and HIMEM release back in July or August. --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] EMM386 2.05 update, recommended for all
At 05:05 PM 9/19/2005 -0700, Brolin wrote: Firstly, I have not tested this new release. That said, what is the status with regards to having FastTracker II working on FreeDOS? My FreeDOS installation consists mainly of what was distributed with the Beta9 SR1 CD, so some of the components may be fairly old. If you're asking me personally, I don't have a clue. If you're asking the list, hopefully someone will have the answer. Should FastTracker work without EMM386 loaded and NOT work with EMM386 loaded as the ONLY difference, it may be a compatibility problem with EMM386, otherwise not very likely to be related to it. --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS on PC XT
Nick Bright wrote: Blair Campbell wrote: There is an 8086 version of SHSUCDX available, so you musn't use SHSUCDX to load the extentions, but you must instead use SHSUCD86 or something like this. I'm not sure if there are any drivers available for pre-386 systems, however. I'll try SHSUCD86 and see what happens. I'm not sure what you refer to by I'm not sure if there are any drivers available for pre-386 systems though. Do you mean the cdrom .sys driver file? If so, yes there are. I have one installed. Correction to myself. I am assuming this driver works with the PC XT since the document I read indicates as such. - Nick I can't find an SHSUCD86.* anywhere on the SR1 CD, though I haven't really looked elsewhere yet. I did look at the output of SHSUCDX /V though, which indicates: Compile-time options: 8086, CD root form not used, High Sierra supported, Joliet supported, image on CD supported. Run-time options: tilde generation is off, read only attribute is on This would seem to indicate that this version of shsucdex is compatible with this system, no? - Nick --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS on PC XT
Nick Bright schreef: -=-=-=-=-=-=- SNIP -=-=-=-=-=-=-=- Nice to actually see that people read documentation :) At the time I wrote those texts, there were no *known and working* (IDE/SCSI) cdromdrivers for config.sys, and also the 8086-compatible version of SHSUCDX wasn't released yet. As you can see from my previous mailing list post, I do indeed have a pre-386 system with a CDROM. The above snip leads me to belive that the cdextensions file (though it runs on my XT) hasn't been debugged for that platform, and may not even be properly compiled (e.g. 386 optimizations)? Could any devs shed some light on this, perhaps? DEVICE=FDCD.SYS /D:FDCD0001 /F/R/Z instead of above driver, could you also try ASPICD.SYS? It's closed source, so we cannot see if it works on pre386 systems, As it's SCSI, maybe even a SCSI DVDdrive would work (Pioneer 105S maybe?) :) ASPICD.SYS is from: http://www.techadvice.com/w98/S/Startup-Disk_w98.htm Usually cdrom driver components are the following: *cdrom hardware device *controller + specific controller driver: DEVICE=DCAM950.EXE /CA00 3 *generic device driver for some type of device (Disk, or CD): DEVICE=FDCD.SYS /D:FDCD0001 /F/R/Z *ISO9660 redirector: SHSUCDX /D:FDCD0001 (or MSCDEX maybe) As that device-type driver should be generic, you might have a chance of switching to ASPICD.SYS Another generic driver should be SYMCD.SYS, available in package at: http://www.lsilogic.com/downloads/license.do?id=2000did=2907pid=2099 I hope you're able to run any programs - DOS is a memoryhog if only conventional memory is available. thanks for the 'adding cdrom to ancient computer' link. Bernd --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS on PC XT
This would seem to indicate that this version of shsucdex is compatible with this system, no? That would. However, there is a file called shcdx86.com. This is the file I meant. --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS on PC XT
Nick Bright schreef: Compile-time options: 8086, CD root form not used, High Sierra supported, Joliet supported, image on CD supported. Run-time options: tilde generation is off, read only attribute is on This would seem to indicate that this version of shsucdex is compatible with this system, no? correct, sometimes I rename files in order to achieve maximum compatibility. It happens that programmers release separate 8086 drivers, but give them an alternative name. SHSUCDX 3.02 available from http://www.geocities.com/jadoxa/shsucdx/ Bernd --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] [XT] edit.exe seems to hang
I'm not sure if it'll be helpful or not, but as I'm working on my XT, I'll post things I come across that seem to not work on this platform. In this case, running edit.exe simply hangs. The drive accesses for a moment, the cursor sits blinking, and nothing happens until I push the reset button. I doubt if it makes a difference, but my installation currently consists of a sys'd drive, with files from the CD copied over when I had the drive subsystem plugged in to a later i686 motherboard for testing. I figured all the binaries I might need to get things going would be on there :) - Nick --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] [XT] edit.exe seems to hang
In this case, running edit.exe simply hangs. The drive accesses for a moment, the cursor sits blinking, and nothing happens until I push the reset button. Try this version of edit: http://www.coli.uni-saarland.de/~eric/stuff/soft/by-others/edit07d.zip --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] [XT] edit.exe seems to hang
Nick Bright wrote: I'm not sure if it'll be helpful or not, but as I'm working on my XT, I'll post things I come across that seem to not work on this platform. In this case, running edit.exe simply hangs. The drive accesses for a moment, the cursor sits blinking, and nothing happens until I push the reset button. I doubt if it makes a difference, but my installation currently consists of a sys'd drive, with files from the CD copied over when I had the drive subsystem plugged in to a later i686 motherboard for testing. I figured all the binaries I might need to get things going would be on there :) - Nick There's only one solution for this: use edlin instead. ;-) Gregory Pietsch --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS on PC XT
Bernd Blaauw wrote: Nick Bright schreef: -=-=-=-=-=-=- SNIP -=-=-=-=-=-=-=- Nice to actually see that people read documentation :) At the time I wrote those texts, there were no *known and working* (IDE/SCSI) cdromdrivers for config.sys, and also the 8086-compatible version of SHSUCDX wasn't released yet. Yes, sometimes it seems that not many people read documentation anymore :) I perfer to read as much documentation as possible before posting to a mailing list, so as to make a well informed posting (as well as not look like an idiot). I also belive strongly in not posting I solved it. to the list, but rather I solved it, here's the solution However, as pointed out to me by Bernd in a private email, I am using a fairly old copy of the CD (SR1). I'm going to start all over with the latest ODIN and post results in a little bit. As you can see from my previous mailing list post, I do indeed have a pre-386 system with a CDROM. The above snip leads me to belive that the cdextensions file (though it runs on my XT) hasn't been debugged for that platform, and may not even be properly compiled (e.g. 386 optimizations)? Could any devs shed some light on this, perhaps? DEVICE=FDCD.SYS /D:FDCD0001 /F/R/Z instead of above driver, could you also try ASPICD.SYS? It's closed source, so we cannot see if it works on pre386 systems, As it's SCSI, maybe even a SCSI DVDdrive would work (Pioneer 105S maybe?) :) ASPICD.SYS is from: http://www.techadvice.com/w98/S/Startup-Disk_w98.htm Usually cdrom driver components are the following: *cdrom hardware device *controller + specific controller driver: DEVICE=DCAM950.EXE /CA00 3 *generic device driver for some type of device (Disk, or CD): DEVICE=FDCD.SYS /D:FDCD0001 /F/R/Z *ISO9660 redirector: SHSUCDX /D:FDCD0001 (or MSCDEX maybe) As that device-type driver should be generic, you might have a chance of switching to ASPICD.SYS Another generic driver should be SYMCD.SYS, available in package at: http://www.lsilogic.com/downloads/license.do?id=2000did=2907pid=2099 I hope you're able to run any programs - DOS is a memoryhog if only conventional memory is available. thanks for the 'adding cdrom to ancient computer' link. Bernd --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS on PC XT
by I'm not sure if there are any drivers available for pre-386 systems though. Do you mean the cdrom .sys driver file? If so, yes there are. I have one installed. Yes, that is what I meant. --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] EMM386 2.05 update, recommended for all
Uploaded to ftp://ftp.devoresoftware.com/downloads/emm386 are the files emmx205.zip, EMM386/HIMEM mostly executable package, and emms205.zip, EMM386/HIMEM mostly source package. This version of EMM386 has a number of compatibility changes to enhance operability with a variety of DOS applications and environments without the need for advanced option tweaking. As a result of the seven changes to EMM386 and two changes to HIMEM, this is a recommended released. Briefly, besides various fixes and compatibility modifications, the VDS option now defaults to on, with a new NOVDS option to turn it off (NOVDS possibly required for some SCSI disk drivers); the XMS memory manager supports growing memory blocks on resize for the Graphics Vision text editor; and a limited MEMCHECK default of 3-4G is present for MMIO-based devices such as USBASPI.SYS, with the ability to turn it all off by use of the new NOCHECK option. Particulars ponderously proceed post-paragraph: The HMAMIN setting of HIMEM never up-converted its K setting to actual bytes as required internally, plus it allowed 64K instead of a maximum of 63K. Bad HMAMIN, bad boy. Fixed. The NOVCPI option was blocking allocation of UMBs. This was overly aggressive, even for a severe option like NOVCPI, and it was chastised back to proper behavior. Regardless of that whoopsie, friends don't let friends use NOVCPI, as it is almost never a good idea. Unless you know exactly why you are using NOVCPI, don't. There was an error when parsing EMS, such that an EMS page frame was marked present even if there was insufficient upper memory (i.e. no 64K contiguous block) to place it properly. The problem would not be present if you specified NOEMS and even without NOEMS it would not cause misbehavior unless you used an application which depended on EMS and a page frame. Admittedly, it was an error with a nasty bite, but one had to wander far into the hinterlands of nontypical environments to get bitten. Such is how developers rationalize away crippling guilt. And minor bugs. The EMM386 driver saves the full 32-bit part of all general registers it uses, as well as segment registers. This may or may not clear up problems with 386-optimized kernels. I can't test. It consumes an additional 22 bytes of stack, which I'm thinking probably shouldn't be a problem. Of course, I used to think an incompetent buffoon probably wouldn't make a second term as President, and now look what the USA is stuck with, so counting on me to tell you whether a particular kernel version is safe seems chancy. HIMEM's XMS API supports growing a block on resize; previously only shrinking was supported. Sufficient contiguous memory must be available to simultaneously hold the old block and the new block or else it will fail. This feature was added because the Graphics Vision text editor did not gracefully handle a failed XMS growing resize, although resizing is never guaranteed. I don't know whether it's a bound-in extender fault or an application fault, but something is acting goofy in there and we're stuck writing the work-around for it. Not that I feel crabby about it. EMM386's VDS option had a bug in the scatter/gather function and made various setups, such as Bernd's VMWare and Mark Bailey's laptop, cry in grief and frustration at the unfairness of it all. The evil error was corrected to help better balance Universal Justice towards the Good Guys. While on the topics of VDS, the VDS option is now on by default. Too many environments require this to leave it as optional, plus a default on condition matches Microsoft EMM386. There exist SCSI setups which will REQUIRE you to turn off VDS support via the new NOVDS option. Unfortunately for those SCSI-ites, the people who need VDS outnumber the people who need to not have VDS, so they lost out. Or maybe the people who need VDS just yell louder. Ahh well, same difference to me. I like quiet. EMM386 internally defaults its MAX setting to 256M, so that unless you explicitly specify a MAX= setting more than 256M, available VCPI will not exceed this amount. This change was made solely to accommodate the DOS/32A extender complaining when large amounts of free VCPI memory are available. Applications which used the extender would fail with a fatal error in such cases, including MPXPLAY -- an otherwise extremely impressive DOS program that deserves major kudos. It appears that DOS/32A is dumb as a leaf of lettuce about the whole lots of VCPI available thing, which kind of sours me on those rabid endorsements of it. The final change is to ensure better compatibility with device drivers that use MMIO (memory-mapped I/O) to high addresses outside of normal RAM, such as USBASPI.SYS. Previously, the MEMCHECK option was required. EMM386 now defaults to operating as if MEMCHECK was present IF the source or destination address range starts (not ends) within the
[Freedos-user] [XT] CD Rom Support
Thanks for getting me straightened out on which version of FreeDOS I was using, Bernd. The updated versions of all the software seem to be working much better, including edit :) After stripping out enough to get a 720K disk, I was able to successfully boot the ODIN floppy with the DCAM950 and FDCD drivers, and read the CDROM drive! Of course, I've now updated my hard-drive installation with the files from this disk :) It appears all my troubles were related to using an outdated version of the distribution. For refrence I used the files located at: http://odin.fdos.org/odin2005/ Using readme.txt to determine how to cull the files down to 720K, then writing to disk of course; then editing the configuration files to add the necessary directives, as established previously in the thread (duplicated here for clarity): --- Configuration Directives to load driver: Config.sys example: DEVICE=DCAM950.EXE /CA00 3 DEVICE=FDCD.SYS /D:FDCD0001 /F/R/Z DEVICE=DCAM950.EXE /CA00 3| says that there's a Future Domain SCSI controller at address CA00h, IRQ 3. These settings match the jumpers on the SCSI card itself. I set the card to IRQ 3 so it wouldn't conflict with the hard drive controller on the motherboard. DEVICE=FDCD.SYS /D:FDCD0001 /F/R/Z| says that there's a CDROM drive attached to the controller. The |/D:MSCD0001| gives the drive an ID so that MSCDEX can use it (see below). The other bits (|/F/R/Z| are options to do with scanning for the drive, and probably aren't necessary). Autoexec.bat example: shsucdx /Q /D:FDCD0001 I also tested the aspicd.sys driver you requested a test of, I tried the following fdconfig.sys combinations of drivers - 1) This did not work: DEVICE=dcam950.exe /de000 5 DEVICE=aspicd.sys /d:fdcd0001 2) This did not work, as I found as soon as I tried it that aspi2dos.sys is for AIC-6xxx controllers: DEVICE=aspi2dos.sys DEVICE=aspicd.sys /d:fdcd0001 --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] [XT] CD Rom Support
Thanks for getting me straightened out on which version of FreeDOS I was using, Bernd. The updated versions of all the software seem to be working much better, including edit :) Hopefully soon I will be producing a floppy version of my distro, which includes the latest software that is available on ODIN. Unfortunately, ODIN is not really for installations and (I'm not sure about this) it is unfriendly to install from currently. --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] [XT] edit.exe seems to hang
Blair Campbell wrote: In this case, running edit.exe simply hangs. The drive accesses for a moment, the cursor sits blinking, and nothing happens until I push the reset button. Try this version of edit: http://www.coli.uni-saarland.de/~eric/stuff/soft/by-others/edit07d.zip This version works (same as latest ODIN), but is VERY slow. Of course, this is a very slow machine though. Changing the options to disable all window decorations resulted in a significant improvement in editor performance, though. I suspect the clock in the status bar is the culprit. However, when I select save options the saved options only take effect if I change to c:\fdos before executing edit. Perhaps I am doing something wrong? I noticed that this program has a lot of nice features that could possibly be stripped out for improved performance for perhaps a specific version for low end systems, perhaps to be named minied or something? Some thoughts of a mini version: *) remove multiple file editing support *) remove ascii table and calendar *) remove undo/redo function or remove other advanced editing features *) remove search Perhaps I'll hack on the source, but I doubt it. I've got a lot of projects going on :) - Nick --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] [XT] CD Rom Support
Blair Campbell wrote: Thanks for getting me straightened out on which version of FreeDOS I was using, Bernd. The updated versions of all the software seem to be working much better, including edit :) Hopefully soon I will be producing a floppy version of my distro, which includes the latest software that is available on ODIN. Unfortunately, ODIN is not really for installations and (I'm not sure about this) it is unfriendly to install from currently. I was able to sys my disk and get a basic installation going by copying over all the files off the disk to d:\fdos and modifying autoexec/fdconfig as necessary... but it may not be that easy for less experianced users, who are not familier with doing that kind of thing. - Nick --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] [XT] edit.exe seems to hang
culprit. However, when I select save options the saved options only take effect if I change to c:\fdos before executing edit. Perhaps I am doing something wrong? This sounds like a bug to me. Make sure you e-mail Eric Auer with a bug report before he releases the final version of 0.7d. I noticed that this program has a lot of nice features that could possibly be stripped out for improved performance for perhaps a specific version for low end systems, perhaps to be named minied or something? Some thoughts of a mini version: *) remove multiple file editing support *) remove ascii table and calendar *) remove undo/redo function or remove other advanced editing features *) remove search Once more, e-mail Eric with your suggestions. --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] [XT] CD Rom Support
autoexec/fdconfig as necessary... but it may not be that easy for less experianced users, who are not familier with doing that kind of thing. Which is exactly what I meant. A current FreeDOS install system should be available on floppies as well as CD-ROMs, but for now I haven't gotten around to making a floppy version of my distro (which is only available on 100 and 200 mb ISOs). --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] [XT] Bug found - zip utility
Just testing things about, I tried to zip a file, and received an error about requiring an 80386. The ODIN readme.txt file indicates this is an 8086 compatible binary. Perhaps a documentation error, perhaps a compile error? Unzip successfully unzips a file from the ODIN disk; slowly, of course - it's an XT :) The exact error text is: C:\zip 80386 required. 80386 required. Load error: no DPMI - Get csdpmi*b.zip - Nick --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] [XT] Bug found - zip utility
error? Unzip successfully unzips a file from the ODIN disk; slowly, of course - it's an XT :) One cool thing you could try (although it won't work for zip), is using EMU386 to emulate a 386 on a 286. This will probably not work for most programs becuase the docs say it only works if 1) only real mode is used, and 2) the program does not check the CPU. Here is a link: http://members.tripod.com/~survpc/emu386/ It'd be very interesting if the source ever became available; it could possibly be expanded to support PM and apps that check the CPU type. --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
