Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
At 03:38 AM 7/30/2005 +, Mark Bailey wrote: I see no difference at all with that version, either with the development kernel/command.com or the stable kernel/ command.com. Specifically, with device=a:\himem.exe device=a:\emm386.exe x=test memcheck vds vol c: hangs. Remove vds, it works normally. (development) Alright, one more time. I rewrote the VDS routines such that any reserved function which was unused (0, 1, 0dh-0ffh) no longer returns an error code, but simply sets carry flag and chains to old INT 4bh handler. That may get around a SCSI conflict. Or not. In addition, I cleaned up slightly naughty code which re-enabled interrupts when returning from the VDS call. Theoretically, the VDS interrupt might have been called with hardware interrupts disabled for good reason. Will these revisions change anything? Don't know, but it's the best I can do without a misbehaving machine here to test. Hopefully no new error was introduced. Those with VDS-unhappy machines will need to try it out and report back results. To test this version of EMM386, amble over to ftp.devoresoftware.com\downloads\emm386 and download emmhorse.zip. As before, unofficial release, no exterior version change, no EXE compression. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
Hi Michael: No change with this version...system hangs on vol c: with VDS option, works without. Mark Bailey At 03:38 AM 7/30/2005 +, Mark Bailey wrote: I see no difference at all with that version, either with the development kernel/command.com or the stable kernel/ command.com. Specifically, with device=a:\himem.exe device=a:\emm386.exe x=test memcheck vds vol c: hangs. Remove vds, it works normally. (development) Alright, one more time. I rewrote the VDS routines such that any reserved function which was unused (0, 1, 0dh-0ffh) no longer returns an error code, but simply sets carry flag and chains to old INT 4bh handler. That may get around a SCSI conflict. Or not. In addition, I cleaned up slightly naughty code which re-enabled interrupts when returning from the VDS call. Theoretically, the VDS interrupt might have been called with hardware interrupts disabled for good reason. Will these revisions change anything? Don't know, but it's the best I can do without a misbehaving machine here to test. Hopefully no new error was introduced. Those with VDS-unhappy machines will need to try it out and report back results. To test this version of EMM386, amble over to ftp.devoresoftware.com\downloads\emm386 and download emmhorse.zip. As before, unofficial release, no exterior version change, no EXE compression. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
At 04:05 AM 7/30/2005 +, Mark wrote: Hi Michael: Well, the E000 message is repeatable on this box... Found that problem. A matter of the EMS routines not properly reporting failure to locate a suitable page frame. Instead they fell through and reported the default page frame. I suppose that would have caused program failure if you didn't specify NOEMS option, didn't have enough room for the EMS page frame, AND the program actually tried using EMS. Anyway, it's fixed now, with better feedback on failure to locate a page frame when NOEMS and FRAME=NONE options are not specified. If you want to try this test version of EMM386, Go to ftp.devoresoftware.com\downloads\emm386 and download emmcow.zip. It should fix your page frame feedback problem. Very much doubt it affects your VDS situation, but you can give it a shot. Interesting thing, though. I could only get the message here if I first booted into Win XP, then rebooted into my FreeDOS flash stick through Windows restart. Apparently, the X=TEST option found garbage bytes at segments E000 - EF00 in those circumstances, so it excluded that entire range. Wouldn't happen on subsequent reboots direct with the FreeDOS flash stick OR powering down and up into the flash stick. Only rebooting from within XP. And that's a good reason why X=TEST probably shouldn't be a default option. Under reproducible conditions on my computer, it can exclude an entire 64K range of upper memory that is available. There is no way to automatically detect that the range shouldn't be excluded, because the bytes are nonrepeated and look like they actually have a purpose. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
Hi! 30-Июл-2005 04:39 [EMAIL PROTECTED] (Michael Devore) wrote to freedos-user@lists.sourceforge.net: MD After bootup, type debug to run DEBUG.EXE. At debug prompt, type d 0:12c MD and press enter. MD There will be a display of 2-digit hex numbers, the first line lists four MD of them. Just hint: to limit D output to 4 bytes, use L suffix - d0:12cl4. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
Michael Devore schreef: At 04:05 AM 7/30/2005 +, Mark wrote: If you want to try this test version of EMM386, Go to ftp.devoresoftware.com\downloads\emm386 and download emmcow.zip. It should fix your page frame feedback problem. Very much doubt it affects your VDS situation, but you can give it a shot. this version also complies to your instructions, like ftp://ftp.devoresoftware.com/downloads/emm386/EMMBLORT.ZIP ? (and unlike EMM386 v2.04) I guess so, just tested your procedure and getting a 'OR AL,AL ; JZ 014A' and that VDS vector must be allright then. Now why is my Mozilla Thunderbird making a link of your 'link' ? ftp.devoresoftware.com\downloads\emm386 And that's a good reason why X=TEST probably shouldn't be a default option. Under reproducible conditions on my computer, it can exclude an entire 64K range of upper memory that is available. There is no way to automatically detect that the range shouldn't be excluded, because the bytes are nonrepeated and look like they actually have a purpose. for end-users better too much excluded, than having crashes I think. Bernd --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
Hi Michael: I dual or triple boot all of my machines and routinely switch from DOS to WindowsXP and back. So, this makes sense. Frankly, XP makes for a more convenient Web and e-mail interface (IMHO! :-)). So, during much, even most, of my testing, I boot XP a lot...sometimes just to copy something like UDMA2 or a new version of EMM386 from the web to a test floppy or to e-mail results of a test. I also create FreeDOS boot CD's and floppies from XP. Mark At 04:05 AM 7/30/2005 +, Mark wrote: Interesting thing, though. I could only get the message here if I first booted into Win XP, then rebooted into my FreeDOS flash stick through Windows restart. [...] Only rebooting from within XP. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
At 04:05 AM 7/30/2005 +, Mark wrote: Well, the E000 message is repeatable on this box... Thanks again for all of your help! Well, we can check if your VDS vector is okay pretty easily. Try this with the test EMM386 using VDS option. Don't type VOL first to crash things or load UDMA. After bootup, type debug to run DEBUG.EXE. At debug prompt, type d 0:12c and press enter. There will be a display of 2-digit hex numbers, the first line lists four of them. Probably the first two will be 45 01. Whatever they are, type them in as U 43:21. So if the four numbers are 45 01 21 03, type U 0321:0145 and press enter. You should see a assembly language listing starting with CMP AH,81 followed by JZ 0181. Take the 0181, or whatever it is, and type U 0321:0181 (replacing 0321 with the number you typed for first U and 0181 with the number after JZ), then press enter. You should see OR AL,AL, then JZ 014A. If you don't see that let me know. If you do see that, then your basic VDS re-vectoring is fine. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
At 09:32 PM 7/30/2005 +0200, Bernd Blaauw wrote: 1) harddisk present, but unpartitioned and not formatted d 0:12C U 0307:0145 U 0307:0180 output: MOV BYTE PTR CS:[0084],00 CMP AL,02 JZ 01E1 You're not using test EMM386 is what that indicates. No test for AL equal to zero, as was added. The rest is correct for last 2.04 EMM386 release. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
Hi Michael: Well, what's trying to use it is the FreeCOM VOL command! (Or something else in FreeCOM). I doubt that there are any explicit calls to VDS functions there. The kernel may be more likely. This appears to be the same bug that caused FDISK to wipe out the MBR, so it at least appears that just initializing the VDS functions is trashing something in memory. I could ship you this laptop if you believe that will help or I can run any test routines you can think of! Mark Bailey At 11:53 PM 7/28/2005 +, Mark wrote: Do I need VDS? :-) What does it do? How can I help identify the problem? I do have the Haunted HP Pavilion (TM)! Turn it off if everything works without it. It's just for upper memory reporting of true physical address instead of logical address for DMA purposes. Maybe something is trying to use a function that isn't supported or ignoring a return code that a sub-function is not supported. You don't see any feedback messages when it's present do you? VDS will write to display a line about unsupported functions, but can't help if a program tries to use a subfunction that returns an unsupported code. Without the machine that croaks, though, not much chance I can tell you what's going on with the VDS problem. Could be the fault of either VDS support, or what's trying to use VDS. And no way of knowing here what or how to fix/work around it. I was going to make VDS a default, maybe I shouldn't. --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
At 10:13 AM 7/29/2005 +, Mark Bailey wrote: This appears to be the same bug that caused FDISK to wipe out the MBR, so it at least appears that just initializing the VDS functions is trashing something in memory. No such thing. VDS functions just are, they don't initialize. Only thing that VDS actively changes is that INT 4Bh is revectored and a bit is set at 40:7bh. Ha! That's it. Some SCSI BIOS uses INT 4BH. It must be passing the register value that VDS interprets as a VDS function, which means AH = 81h. Hmm, let me look things over to see if there's a way to resolve the conflict by further determining the difference or if it's inherently incompatible. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
At 12:42 PM 7/29/2005 -0500, I wrote: Ha! That's it. Some SCSI BIOS uses INT 4BH. It must be passing the register value that VDS interprets as a VDS function, which means AH = 81h. Hmm, let me look things over to see if there's a way to resolve the conflict by further determining the difference or if it's inherently incompatible. Okay, this looks like the smoking gun. Now to figure out a workaround: INT 4B - Common Access Method SCSI interface (draft revision 1.9) ES:DI - CAM Control Block (see #03229 at INT 4F/AX=8100h) InstallCheck: test for the string SCSI_CAM eight bytes past the INT 4Bh handler Notes: the CAM committee moved the interface to INT 4F after revision 1.9 to avoid conflicting with the IBM SCSI interface and the Virtual DMA specification the only driver to date reported to use the CAM interface on INT 4B instead of INT 4F is from Future Domain (which has drivers for CAM on either interrupt) INT 4F - Common Access Method SCSI interface rev 2.3 - SEND CCB TO XPT/SIM AX = 8100h ES:BX - CAM Control Block (CCB) (see #03229) Return: AH = status 00h successful 01h invalid CCB address (h:h) Note: the SCSI Interface Module (SIM) may complete the requested function --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
Hi Michael: Does this provide a means of easily identifying the affected machines? How do I check the Haunted HP Pavilion? :-) Mark Michael Devore wrote: At 12:42 PM 7/29/2005 -0500, I wrote: Ha! That's it. Some SCSI BIOS uses INT 4BH. It must be passing the register value that VDS interprets as a VDS function, which means AH = 81h. Hmm, let me look things over to see if there's a way to resolve the conflict by further determining the difference or if it's inherently incompatible. Okay, this looks like the smoking gun. Now to figure out a workaround: INT 4B - Common Access Method SCSI interface (draft revision 1.9) ES:DI - CAM Control Block (see #03229 at INT 4F/AX=8100h) InstallCheck: test for the string SCSI_CAM eight bytes past the INT 4Bh handler Notes: the CAM committee moved the interface to INT 4F after revision 1.9 to avoid conflicting with the IBM SCSI interface and the Virtual DMA specification the only driver to date reported to use the CAM interface on INT 4B instead of INT 4F is from Future Domain (which has drivers for CAM on either interrupt) INT 4F - Common Access Method SCSI interface rev 2.3 - SEND CCB TO XPT/SIM AX = 8100h ES:BX - CAM Control Block (CCB) (see #03229) Return: AH = status 00h successful 01h invalid CCB address (h:h) Note: the SCSI Interface Module (SIM) may complete the requested function --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
At 02:58 PM 7/29/2005 -0400, Mark wrote: Does this provide a means of easily identifying the affected machines? How do I check the Haunted HP Pavilion? :-) Here's what to do: Go to ftp.devoresoftware.com/downloads/emm386 and download EMMBLORT.ZIP. Try that version of EMM386.EXE with your machine using VDS. I changed EMM386 to not report an error with function 0 on a VDS call. It's normally reserved and gives a VDS error condition, now it just chains it through with the carry flag set. Hopefully that won't upset things. Let me know if that fixes or modifies the current behavior with VDS parameter. (Oh yeah, lest it not be obvious, EMMBLORT is not an official release of EMM386. It is for testing purposes only.) --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
Michael Devore schreef: Go to ftp.devoresoftware.com/downloads/emm386 and download Let me know if that fixes or modifies the current behavior with VDS parameter. no change in VMware Workstation 4.5.2 (PC emulator, Intel P4 processor) booting from BIOS directly to harddisk. Maybe a floppy would be better :) We're keeping this on the user-list or going to 'devel' list? scenario 1 (works) HIMEM EMM386.EXE (no VDS) scenario 2 (works) HIMEM UDMA2 EMM386 scenario 3 (fails, complains about missing SHELL) HIMEM EMM386.EXE VDS scenario 4 (works) HIMEM UDMA2 EMM386 VDS scenario 5 (fails at accessing C:\FDOS\BIN\UDMA2.SYS because that requires accessing the harddisk to retrieve the file): HIMEM EMM386 VDS UDMA2 What's still strange is that UDMA2 somehow sets the right conditions for EMM386's VDS parameter to work without any troubles. Bernd c:\config.sys: SWITCHES=/F/N COUNTRY=031,858,C:\FDOS\BIN\COUNTRY.SYS SET LANG=NL LASTDRIVE=Z BUFFERS=20 FILES=40 DOS=HIGH,UMB DOSDATA=UMB SET DIRCMD=/OGN /4 MENUCOLOR=7,0 MENUDEFAULT=1,5 MENU 1 - Load FreeDOS with maximum RAM free, using EMM386 MENU 2 - Load FreeDOS including HIMEM XMS-memory driver 12?DEVICE=C:\FDOS\BIN\HIMEM.EXE 1?DEVICE?=C:\FDOS\BIN\UDMA2.SYS 1?DEVICE?=C:\EMM386.EXE NOEMS X=TEST VDS 1?DEVICE?=C:\FDOS\BIN\UDMA2.SYS 12?SHELL=C:\COMMAND.COM C:\ /D /P=c:\autoexec.bat --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
At 10:05 PM 7/29/2005 +0200, Bernd Blaauw wrote: Michael Devore schreef: Go to ftp.devoresoftware.com/downloads/emm386 and download Let me know if that fixes or modifies the current behavior with VDS parameter. no change in VMware Workstation 4.5.2 (PC emulator, Intel P4 processor) booting from BIOS directly to harddisk. Different issue entirely. Don't know what's going on in VMware, it may just not like VDS. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
Michael Devore schreef: Different issue entirely. Don't know what's going on in VMware, it may just not like VDS. very probably, yes, Michael. Mark, can you try loading UDMA2.SYS anyway (in front of EMM386)? DEVICE=HIMEM.EXE DEVICE=UDMA2.SYS DEVICE=EMM386.EXE VDS other_options if that works, then finally what happens for me in VMware isn't specifically a VMware bug :) for the record, the emulator uses a 'Phoenixbios 4.0 release 6'. wish I could load a proper Linuxbios bios imagefile, then see DOS fail miserably :) http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/udma/devel/Udma2_25.zip Bernd --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
At 03:07 AM 7/30/2005 +, Mark Bailey wrote: VOL C: works normally. Without device=a:\udma2.sys, vol c: hangs and forces a reboot. (That's the old behavior which I checked to make sure of the test case). This does not appear to be a seperate issue. Actually it muddies the waters by introducing another low-level driver into the test mix. I really need feedback on the test EMM386 without UDMA2 or something else in there. Basic clean room testing approach before expanding the universe. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
Hi Michael: OK, I have done so. The new version still reports version 2.04, July 6, 2005, but is much larger! I see no difference at all with that version, either with the development kernel/command.com or the stable kernel/ command.com. Specifically, with device=a:\himem.exe device=a:\emm386.exe x=test memcheck vds vol c: hangs. Remove vds, it works normally. (development) With stable kernel, I get screenfulls of garbage I can't read (no newlines) with VDS, normal operation without. UDMA2 still appears to fix it! I reported this before, but EMM386 reports the following: selected page frame e000 not available, searching automatically using PAGEFRAME e000: That looks a bit odd... Thanks very much for all of your help! Mark Bailey At 02:58 PM 7/29/2005 -0400, Mark wrote: Does this provide a means of easily identifying the affected machines? How do I check the Haunted HP Pavilion? :-) Here's what to do: Go to ftp.devoresoftware.com/downloads/emm386 and download EMMBLORT.ZIP. Try that version of EMM386.EXE with your machine using VDS. I changed EMM386 to not report an error with function 0 on a VDS call. It's normally reserved and gives a VDS error condition, now it just chains it through with the carry flag set. Hopefully that won't upset things. Let me know if that fixes or modifies the current behavior with VDS parameter. (Oh yeah, lest it not be obvious, EMMBLORT is not an official release of EMM386. It is for testing purposes only.) --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
[EMAIL PROTECTED] schreef: Hello all: As I mentioned before, remove the VDS parameter and see if things go better then. VMware suffers from incompatibility with the VDS parameter, maybe your system also. Maybe even a lot of systems, but that's a wild guess. IF things fail even without the VDS parameter, then please report to this mailinglist. ANY access to C: might cause trouble. maybe time for me again to make an experimental bootdisk and let people report to the mailinglist if things go OK or fail. Bernd --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
Hi Michael, et al: OK, I am back with the Haunted HP Pavilion (TM). Downloaded development kernel, command.com, and sys.com from fdos.org/kernel. Downloaded emm204x and extracted himem.exe and emm386.exe. Did a SYS: on a USB floppy from WindowsXP. Copied a random version of edit.com on the floppy. Baseline test: config.sys device=a:\himem.exe device=a:\emm386.exe x=test vds memcheck Booted. Edited config.sys. Entered vol c:. Machine hung. Three finger reboot worked. config.sys device=a:\himem.exe rem Edited config.sys. Entered vol c:. Worked fine, reporting Volume in drive C has no label Volume serial number is 2640-14E4 (correct serial number verified from WindowsXP). config.sys device=a:\himem.exe device=a:\emm386.exe x=a000-efff noems emm386 reports no suitable UMB memory block found. Edited config.sys. Entered vol c:. Worked fine. config.sys device=a:\himem.exe device=a:\emm386.exe x=a000-efff noems memcheck Same advisory from emm386. Edited config.sys. Entered vol c:. Worked fine. config.sys device=a:\himem.exe device=a:\emm386.exe x=a000-efff noems memcheck vds Entered vol c:. Hung. Three finger reboot worked. Okay, now what? Do I need VDS? :-) Eliminating that will be my next experiment with NTFS4DOS! Mark At 12:22 AM 7/28/2005 +, Mark Bailey wrote: Help! How do I start to debug this?!?! This is the same machine which has FDISK overwriting the partition table whenever it is run with EMM386. Exclude all high memory via X=A000-EFFF and add NOEMS option. Those two options only, unless your USB driver needs MEMCHECK (some do). Tells you whether you have an upper memory block conflict. So, try: EMM386 X=A000-EFFF NOEMS EMM386 X=A000-EFFF NOEMS MEMCHECK --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
Hi Bernd et al: I wish to thank all of you again for the wonderful support and help! I have been amazed at the responsiveness of the FreeDOS community! Back with the haunted HP Pavilion (TM). Development kernel, sys, and command.com from fdos.org/kernel. EMM386.EXE and HIMEM.SYS from emm204x.zip. Random edit.com. config.sys: device=a:\himem.exe device=a:\emm386.exe x=test memcheck A:\ vol c: works fine. Reports correct serial number. So, it does appear to be the VDS parameter. I can have that checked by a couple of people who are also having failure to boot problems with FreeDOS if we believe that it will help. Do I need VDS? :-) What does it do? How can I help identify the problem? I do have the Haunted HP Pavilion (TM)! Mark [EMAIL PROTECTED] schreef: Hello all: As I mentioned before, remove the VDS parameter and see if things go better then. VMware suffers from incompatibility with the VDS parameter, maybe your system also. Maybe even a lot of systems, but that's a wild guess. IF things fail even without the VDS parameter, then please report to this mailinglist. ANY access to C: might cause trouble. maybe time for me again to make an experimental bootdisk and let people report to the mailinglist if things go OK or fail. Bernd --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
At 11:53 PM 7/28/2005 +, Mark wrote: Do I need VDS? :-) What does it do? How can I help identify the problem? I do have the Haunted HP Pavilion (TM)! Turn it off if everything works without it. It's just for upper memory reporting of true physical address instead of logical address for DMA purposes. Maybe something is trying to use a function that isn't supported or ignoring a return code that a sub-function is not supported. You don't see any feedback messages when it's present do you? VDS will write to display a line about unsupported functions, but can't help if a program tries to use a subfunction that returns an unsupported code. Without the machine that croaks, though, not much chance I can tell you what's going on with the VDS problem. Could be the fault of either VDS support, or what's trying to use VDS. And no way of knowing here what or how to fix/work around it. I was going to make VDS a default, maybe I shouldn't. --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
At 12:22 AM 7/28/2005 +, Mark Bailey wrote: Help! How do I start to debug this?!?! This is the same machine which has FDISK overwriting the partition table whenever it is run with EMM386. Exclude all high memory via X=A000-EFFF and add NOEMS option. Those two options only, unless your USB driver needs MEMCHECK (some do). Tells you whether you have an upper memory block conflict. So, try: EMM386 X=A000-EFFF NOEMS EMM386 X=A000-EFFF NOEMS MEMCHECK --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
