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
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
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] Arachne v1.85;GPL,386+ released!
Florian Xaver wrote: Hi! There is a new version of Arachne! http://www.cisnet.com/glennmcc/arachne/ Bye, Flo --- 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 another Yahoo Group for browsing the internet using DOS http://groups.yahoo.com/group/InternetInDOS/ -- TomLeeM / BigWarpGuy * * * * * * OS2eCS.org Director of Marketing * * * * * * * OS/2 Warp - eComStation Org * * * * * * * http://www.os2ecs.org * * * * * * * * Supporting Past OS/2 Uers and Future eCS Users * * * * * * * * * * * * * * * * * * * * * * * * * * * --- 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] Arachne v1.85;GPL,386+ released!
Florian Xaver wrote: Hi! There is a new version of Arachne! http://www.cisnet.com/glennmcc/arachne/ Bye, Flo --- 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 also Arachneos at Yahoo Groups http://groups.yahoo.com/group/arachneos/ -- TomLeeM / BigWarpGuy * * * * * * OS2eCS.org Director of Marketing * * * * * * * OS/2 Warp - eComStation Org * * * * * * * http://www.os2ecs.org * * * * * * * * Supporting Past OS/2 Uers and Future eCS Users * * * * * * * * * * * * * * * * * * * * * * * * * * * --- 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
[Freedos-user] re: How to report a kernel bug?
Hm... why not ask on -kernel or at least on -devel? > I have a machine where to reproduce this bug, or a similar one. It's a > 286. Strangely enough, FreeDOS will boot from floppy and see C:, but > will refuse to boot from there (locks at InitDisk I think, I haven't > investigated into this). IF it locks in InitDisk then you will see the InitDisk string on the screen. If you do not, then you can try FDISK /MBR to replace the MBR program code by a fresh copy, and/or try a newer SYS version to install a newer bootsector on C:... If the MBR works right, then you should see at least the "FreeDOS" string displayed by the boot sector. If the boot sector works right, you should see, depending on how far you get, "123" or "InitDisk" or the drive list or the banner message, etc.! > I seem to recall that Arkady has a tool to inspect the MBR and > find possible problems, right? Arkady has BOOTFIX to analyze bootsectors. To analyze the MBR, use FDISK /SMBR [drive number, e.g. 1] to save the MBR to a boot.mbr file. You can also try MIRROR /PARTN ... or a debug script or other methods. Eric --- 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
[Freedos-user] re: FreeDOS FDISK issue with Windows Build
Hi Gerry, > The summary of the issue, is that Windows thinks there's a "previous > operating system" on the C drive, even though FreeDOS has _never_ been > installed on that C drive. It causes a "boot loader" menu to appear in > Windows every time the computer is started offering Windows or the > "previous o/s". To fix it requires changing attribs on BOOT.INI, editing > it, then re-apply attribs... You could write a small batch script to automate that... > FreeDOS Beta9sr1: > ... > 4. > 5. FORMAT C: Did you verify that the reboot is needed? I know we recommend it, but you never know... Well probably do DO need it. Just wondering ;-). > "This is not a bootable disk. Please insert a bootable floppy and try > again..." Default boot sector of FreeDOS FORMAT probably. Windows decides that this is not the default Windows or MS DOS boot sector, so it takes the safe route and assumes that anything other than Windows is another OS. OSCHECK is actually smarter in detecting other operating systems :-). > Now I'm wondering ... is that text string above FreeDOS related? If so > then it seems I'm correct about what's happened. I would recommend two things: Use FAT32/LBA partition type, and format with FORMAT C: /A for easier conversion to NTFS. This will also be a good test whether our FAT32 format is Windows compatible even for convert. > C:\="Previous Operating System on C:" > The last line should not exist, and would not be there under MS-DOS. You could zap it, but you could try if running MS DOS SYS C: to put a MS DOS boot sector on the drive makes Windows behave more as intended (assuming that it will not suggest Windows users to boot MS DOS ;-)). You can also use attrib and del after that to delete the MS DOS kernel: Microsoft always seems to use potentially bootable boot sectors, even if you do not use SYS, so Windows should be able to detect that this is a "MS DOS disk but not bootable because kernel is missing" when it sees the MS DOS boot sector. As MS DOS does not support FAT32, you can use Win98 DOS SYS instead. Eric --- 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] FreeDOS FDISK issue with Windows Build
> Perhaps a misunderstanding? I'm not using a Windows CD, I'm building > over the network. You basically put an image of your o/s with > customizations on a network share, boot to FreeDOS, create temporary > partition on the first physical hard-drive, then run the Windows setup > program. The setup program has to reboot to begin the next phase, and > this is the point where it would fail if there was no MBR. MS-DOS probably works then because Windows assumes that the user is upgrading. With FreeDOS, Windows doesn't know that. --- 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
[Freedos-user] re: FreeDOS FDISK another partition problem
Hi... > 2. FDISK /CLEARALL 1 > 3. FDISK /MBR > 4. FDISK /PRI:2000 That would be dangerous, I think. The bug report was just "it does not boot after fdisk and sys", not "I want to kill all my data". The solution FDISK /MBR will already be enough. > > run some heavy calculation job, FreeDOS surely will better than any > > Windows server, since DOS have no (or very little) overhead. > Yes, that's what I'm thinking. The problems will arise when you can't do > multi-tasking and multi-threading, and utilizing full power of load > balancing on dual XEON:( Sorry, DOS for heavy server work is like "who needs a building to run a power grid? It is much lower overhead to just hold those wires togeth... > Have you tried DR-DOS's multitasking? Even that will not virtualize the hardware - there is only ONE network card and DR DOS will still run on only ONE CPU (no hyperthreading either). If you use a multitasking operating system, then the kernel controls the network drivers, and it will be able to give several programs at the same time access to the network, by managing connection queues and whatnot. The small DOS overhead can be nice if you run a single program which has to crunch lots of numbers without getting disturbed by other running tasks and by a variety of gadgets that you have in RAM and maybe even eating some CPU time while your number cruncher does not need them at all. On the other hand, there are things for which DOS is definitely NOT best. Eric --- 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] FreeDOS FDISK issue with Windows Build
Hi Blair, But as far as I know FDISK /CLEARALL will remove the MBR. If I don't put it back, the hard drive will NOT boot at all when Windows setup calls the reboot code... The hard drive will not boot, but the Windows CD should be able to. Unless it is Win95. Perhaps a misunderstanding? I'm not using a Windows CD, I'm building over the network. You basically put an image of your o/s with customizations on a network share, boot to FreeDOS, create temporary partition on the first physical hard-drive, then run the Windows setup program. The setup program has to reboot to begin the next phase, and this is the point where it would fail if there was no MBR. -- Gerry Hickman (London UK) --- 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] FreeDOS FDISK issue with Windows Build
Hi Bernd, FreeDOS Beta9sr1: 1. FDISK /CLEARALL 2. FDISK /MBR 3. FDISK /PRI:2000 4. 5. FORMAT C: 6. Start real-mode windows setup program C: is NTFS, FAT16 or FAT32? If you look at Step 3 above, you will perhaps agree that C: is FAT32? Unknown bootsectors are indeed saved to file called BOOTSECT.DOS OK. FDISK only creates MBR. Format creates a filesystem. MS FORMAT creates filesystem, then puts a bootsector identical to that created by the FreeDOS SYS program on that filesystem. OK. FD FORMAT creates a bootsector which only reports something like "This is not a bootable partition". FreeDOS SYS creates a working bootsector. OK, so if I ran FreeDOS SYS program after the above, would this make Windows think it's a valid MS-DOS install? Can you test some mixed operating system utilities? please first obtain the FreeDOS SYS program (rename to FDSYS.COM) from: http://fdos.org/AutoIndex/index?dir=kernel/&file=SYS.dev.COM Scenario 1: DOS 6.22 procedure, but do FDSYS C: C: /BOOTONLY Scenario 2: DOS 6.22 procedure, but do FDISK /MBR (FreeDOS FDISK) Scenario 3: combine 1&2 Scenario 4: FREEDOS, then use MS SYS or MS FORMAT for formatting Scenario 5: FREEDOS, then use FDISK /MBR (MS FORMAT) Scenario 6: combine 4&5 Hmm, the problem is it takes 10 minutes to get to the dual boot screen each time! I'll print this out and try to work out if it's practical. I am most interested in scenario #1: FREEDOS SYS can create a bootsector for MSDOS, and I wonder what Windows thinks of it, and if it will create a dualboot then Ah OK, I think that's what I was saying above. That sounds like the first thing to try. If I choose this option "Previous Operating System on C:", I see the following text: "This is not a bootable disk. Please insert a bootable floppy and try again..." lack of a bootsector installed by SYS. Above text done by FD FORMAT OK, this is very helpful. formatted: Windows thinks there's a previous OS unformatted: Windows cannot install due to no space for temporary files not exactly a win-win situation :( It sounds like the root of the problem is that FreeDOS FORMAT does not do the same as MS-DOS format, and visa-versa? A possible scriptable possible solution (hehe) might be to rewrite boot.ini, or change timeout=30 to timeout=1 or something. Yes, it's an extra build step I could do without. It also slows the build down a lot because it waits 30 seconds on every boot WHILE it's building itself - I can't script it until it's built... At least this confirms Win2000 installs on FreeDOS :) Yes, it's like a dream on FreeDOS, except for this one thing...the only improvement I can think of, is to be able to install straight to NTFS using a FreeDOS NTFS driver and FreeDOS NTFS format program (when it's ready), this would enable creating an NTFS partition with 4k cluster size instead of 512b, but I don't know if Windows setup would allow such things during text-mode setup anyway. I assume you loaded SMARTDRV? No, I used LBACACHE, is that the right toy for the job? It went like a rocket. -- Gerry Hickman (London UK) --- 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] FreeDOS FDISK issue with Windows Build
> But as far as I know FDISK /CLEARALL will remove the MBR. If I don't put > it back, the hard drive will NOT boot at all when Windows setup calls > the reboot code... The hard drive will not boot, but the Windows CD should be able to. Unless it is Win95. --- 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] FreeDOS FDISK issue with Windows Build
Hi Blair, Blair Campbell wrote: FreeDOS Beta9sr1: 1. FDISK /CLEARALL 2. FDISK /MBR 3. FDISK /PRI:2000 Not sure if this is the problem, but try without fdisk /mbr But as far as I know FDISK /CLEARALL will remove the MBR. If I don't put it back, the hard drive will NOT boot at all when Windows setup calls the reboot code... Anyway, maybe Bernd's post over-rides this part of the puzzle? -- Gerry Hickman (London UK) --- 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] FreeDOS FDISK another partition problem
Florian Xaver wrote: Have you tried DR-DOS's multitasking? Actually no! I guess it's possible then? But at some point you have to look at the history of prot-mode, isolated processes, installable services, 32/64 bit architecture, self-headling file-systems, and decide how far to take it with something like FreeDOS. I see no reason an intense calculation program could not run under FreeDOS on a network server, but can it run 32bit/64bit and will the people who write it have a big enough market? Would it really run any better on a big server than on a high-spec single processor custom built computer? My guess is no... If you're going to invest in a big server, I think you need an o/s that can run many things at once, otherwise it will be sitting idle for a long time and won't be able to service many different types of request... -- Gerry Hickman (London UK) --- 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] Arachne v1.85;GPL,386+ released!
Bernd Blaauw wrote: What does it do? Arachne is a limited graphical webbrowser for DOS (and maybe Linux). Thanks, this was not clear from the original link. -- Gerry Hickman (London UK) --- 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] FreeDOS FDISK issue with Windows Build
Gerry Hickman schreef: FreeDOS Beta9sr1: 1. FDISK /CLEARALL 2. FDISK /MBR 3. FDISK /PRI:2000 4. 5. FORMAT C: 6. Start real-mode windows setup program 7. Windows is installed, but now it presents a boot loader menu every time it starts with a 30 second timeout. Windows has even "kindly" saved the booting information from my "previous" o/s to a file called BOOTSECT.DOS, and guess what's inside it...? C: is NTFS, FAT16 or FAT32? Unknown bootsectors are indeed saved to file called BOOTSECT.DOS FDISK only creates MBR. Format creates a filesystem. MS FORMAT creates filesystem, then puts a bootsector identical to that created by the FreeDOS SYS program on that filesystem. FD FORMAT creates a bootsector which only reports something like "This is not a bootable partition". FreeDOS SYS creates a working bootsector. Can you test some mixed operating system utilities? please first obtain the FreeDOS SYS program (rename to FDSYS.COM) from: http://fdos.org/AutoIndex/index?dir=kernel/&file=SYS.dev.COM Scenario 1: DOS 6.22 procedure, but do FDSYS C: C: /BOOTONLY Scenario 2: DOS 6.22 procedure, but do FDISK /MBR (FreeDOS FDISK) Scenario 3: combine 1&2 Scenario 4: FREEDOS, then use MS SYS or MS FORMAT for formatting Scenario 5: FREEDOS, then use FDISK /MBR (MS FORMAT) Scenario 6: combine 4&5 I am most interested in scenario #1: FREEDOS SYS can create a bootsector for MSDOS, and I wonder what Windows thinks of it, and if it will create a dualboot then If I choose this option "Previous Operating System on C:", I see the following text: "This is not a bootable disk. Please insert a bootable floppy and try again..." lack of a bootsector installed by SYS. Above text done by FD FORMAT Now I'm wondering ... is that text string above FreeDOS related? If so then it seems I'm correct about what's happened. yes Thing is, I never installed FreeDOS, I never used the SYS command, all I did was use FDISK, so it should not think there's a "previous o/s" on my C drive. formatted: Windows thinks there's a previous OS unformatted: Windows cannot install due to no space for temporary files not exactly a win-win situation :( [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect C:\="Previous Operating System on C:" The last line should not exist, and would not be there under MS-DOS. A possible scriptable possible solution (hehe) might be to rewrite boot.ini, or change timeout=30 to timeout=1 or something. At least this confirms Win2000 installs on FreeDOS :) I assume you loaded SMARTDRV? thanks for your testing efforts 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] FreeDOS FDISK issue with Windows Build
> FreeDOS Beta9sr1: > 1. FDISK /CLEARALL > 2. FDISK /MBR > 3. FDISK /PRI:2000 Not sure if this is the problem, but try without fdisk /mbr --- 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
[Freedos-user] FreeDOS FDISK issue with Windows Build
Hi, I've been testing FreeDOS as a Pre-build environment for server and client Windows builds. In general, everything with FreeDOS is far better than MS-DOS or real-mode Win95/98/ME. However, I'm now at the stage of actually building the "real" PCs and have run into a small but time-consuming problem related to how Windows "sees" partitions created by FreeDOS. The summary of the issue, is that Windows thinks there's a "previous operating system" on the C drive, even though FreeDOS has _never_ been installed on that C drive. It causes a "boot loader" menu to appear in Windows every time the computer is started offering Windows or the "previous o/s". To fix it requires changing attribs on BOOT.INI, editing it, then re-apply attribs, but if you're building a lot of PCs this is not ideal, as it's supposed to be "hands free". This does not happen with MS-DOS. Here are the steps, first with MS-DOS and then with FreeDOS MS-DOS 6.22: 1. FDISK (zap everything) and create 2Gb FAT16 partition 2. Format it 3. Start real-mode windows setup program 4. Windows is installed and starts instantly (no boot loader menu) FreeDOS Beta9sr1: 1. FDISK /CLEARALL 2. FDISK /MBR 3. FDISK /PRI:2000 4. 5. FORMAT C: 6. Start real-mode windows setup program 7. Windows is installed, but now it presents a boot loader menu every time it starts with a 30 second timeout. Windows has even "kindly" saved the booting information from my "previous" o/s to a file called BOOTSECT.DOS, and guess what's inside it...? The only explanation I can think of, is that FreeDOS FDISK has created a Master Boot Record, or Boot Sector that Windows does not recognize, so instead of just trashing it (like wot it does with MS-DOS) it decides to back it up for me and offer it as a boot option! If I choose this option "Previous Operating System on C:", I see the following text: "This is not a bootable disk. Please insert a bootable floppy and try again..." Now I'm wondering ... is that text string above FreeDOS related? If so then it seems I'm correct about what's happened. Thing is, I never installed FreeDOS, I never used the SYS command, all I did was use FDISK, so it should not think there's a "previous o/s" on my C drive. Here is the exact BOOT.INI file that Windows creates when built under FreeDOS (beware line wrap!): [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect C:\="Previous Operating System on C:" The last line should not exist, and would not be there under MS-DOS. -- Gerry Hickman (London UK) --- 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] How to report a kernel bug?
I have a machine where to reproduce this bug, or a similar one. It's a 286. Strangely enough, FreeDOS will boot from floppy and see C:, but will refuse to boot from there (locks at InitDisk I think, I haven't investigated into this). The bad point is that I wasn't able to investigate into this, my 286 is not handy at the moment. I'll have a window at the second week of August. I seem to recall that Arkady has a tool to inspect the MBR and find possible problems, right? Hopefully this may help to understand where and why kernel locks, and bypass this (I do not mean to mount the drive, but at least bypass the lock somehow, does it make sense to boot from a non-mounted partition). Aitor Mark Bailey escribió: Good morning: In all of my flailing around about MBR's, I do believe that I have found a kernel bug. The failure of the FreeDOS kernel to initialize with the "incorrect" MBR looks like a bug. It is impossible to use FDISK to correct the MBR when the kernel won't initialize. :-) (Yes, I can use a different operating system to fix it). How do I report the bug? I tried the bugzilla link from the freedos.org home page, but it won't let me create an account. The bug is that, with an apparently incorrect MBR, the development kernel refuses to boot. Thanks. Mark Bailey --- 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=7477&alloc_id=16492&op=click ___ 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] FreeDOS FDISK another partition problem
Yes, that's what I'm thinking. The problems will arise when you can't do multi-tasking and multi-threading, and utilizing full power of load balancing on dual XEON:( Have you tried DR-DOS's multitasking? Bye, Flo --- 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] FreeDOS FDISK another partition problem
Hi Johnson, Out of interest, I think you said it would not boot? Again, should be FDISK problem, seems it can't write the MBR correctly But you didn't tell it to write an MBR? (happen again today in other PII system!) Just a normal setup procedure after setting up the RAID-5: 1) FDISK, select maximize the partition and active 2) Reboot 3) format c: /s OK, but if there was no MBR, this may not create one. That's what my earlier post was all about. Can you try this (all data will be lost) 1. Boot FreeDOS on a floppy (or whatever) Make sure FDISK is 1.3.x or above 2. FDISK /CLEARALL 1 (that's a number one assuming your physical drive number is one) 3. FDISK /MBR 4. FDISK /PRI:2000 5. 6. FORMAT C: /S 7. What happens now? Iif the server can be like Novell, provide connection by TCP/IP and run some heavy calculation job, FreeDOS surely will better than any Windows server, since DOS have no (or very little) overhead. Yes, that's what I'm thinking. The problems will arise when you can't do multi-tasking and multi-threading, and utilizing full power of load balancing on dual XEON:( -- Gerry Hickman (London UK) --- 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] Arachne v1.85;GPL,386+ released!
> What does it do? It's a graphical web browser. --- 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] Arachne v1.85;GPL,386+ released!
Gerry Hickman schreef: http://www.cisnet.com/glennmcc/arachne/ What does it do? Arachne is a limited graphical webbrowser for DOS (and maybe Linux). 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] Arachne v1.85;GPL,386+ released!
Changes are listed at http://www.cisnet.com/glennmcc/arachne/changes.txt Bye, Flo There is a new version of Arachne! http://www.cisnet.com/glennmcc/arachne/ What does it do? --- 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] Arachne v1.85;GPL,386+ released!
Florian Xaver wrote: There is a new version of Arachne! http://www.cisnet.com/glennmcc/arachne/ What does it do? -- Gerry Hickman (London UK) --- 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] screen reader
Hi Mike, I think this is one area where a GUI system can be better than a text based system. The problem with many screen readers was that they did exactly that - read the screen, but under text based systems the developer does not design his applications with consistency - each has it's own menu system, hotkeys and so on. With a GUI like Windows, the screen elements are more defined, so it's very clear whether you're in a content pane, or interacting with a menu. The key bindings are also more consistent across multiple applications. I noticed that Office 2003 has built-in speech support, but I have not actually tried it. I also remember the problems with DOS/WP51 and Dolphin speech synthesisers, and as you say the lack of sound card support was a problem. We migrated our blind users to Jaws under Windows and it seems to solve a lot of problems, was quite expensive as I remember. This page may be a starting point, but I can't find anything specific for DOS: http://www.netserv.net.au/doonbank/speech.html mike coulombe wrote: Hi I am a blind computer user. Does anyone know of a freeware software package for dos. This way speech could be obtained threw the sound card and a external speech unit wouldn't be needed. Thanks Mike. PS incase you don't know what a screen reader is, it makes the computer speak the contance of the screen. X-Antivirus: avast! (VPS 0530-1, 07/26/2005), Outbound message X-Antivirus-Status: Clean --- 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 -- Gerry Hickman (London UK) --- 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
[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
OT Definitely, Was Re: [Freedos-user] FreeDOS kicks some serious Ass!
On Sun, 10 Jul 2005 01:06, Gerry Hickman wrote: > Hi, > > > This is a fantastic operating system. Image installed in my mind, feeble though it be :-) A furious guy named FreeDOS kicking a very, very solemn donkey, shouting, "Laugh, g'damit! My jokes _are_ funny!" Sorry, definitely OT, but I held out as long as I could ... ;) Wesley Parish -- Clinersterton beademung, with all of love - RIP James Blish - Mau e ki, he aha te mea nui? You ask, what is the most important thing? Maku e ki, he tangata, he tangata, he tangata. I reply, it is people, it is people, it is people. --- 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
[Freedos-user] Arachne v1.85;GPL,386+ released!
Hi! There is a new version of Arachne! http://www.cisnet.com/glennmcc/arachne/ Bye, Flo --- 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
