LoneCrusader

No. Read my first post that started this thread. As for why did I use a custom floppy? 1. The original intent was to have a standard El Torito emulation DVD that would load the floppy image on boot. 2. I wanted JO.SYS so that I did not have to remove the DVD on each restart during an OS install or update install, or go and change a BIOS setting every time. 3. The CONFIG.SYS / AUTOEXEC.BAT menu was heavily modified so that I could just choose a number and install a given OS. I had created this prior to learning that for some reason my DVD does not work with standard emulation. Here is what my floppy disk menu looks like: Microsoft Windows Startup Menu ------------------------------------------- 1. Command Prompt with CD & DVD support. 2. Command Prompt without CD & DVD support. 3. Manage partitions with FDisk. 4. Run Partition Magic 8.05. 5. Run DriveImage 2002. 6. Run TestDisk 6.11. 7. Install Windows 95 C OSR 2.5. 8. Install Windows 98 Second Edition. 9. Install Windows Millennium Edition. For example: Choosing "Install Windows 98 Second Edition" starts the computer with CD & DVD support, creates the folder C:\WINDOWS\SETUP, copies all of the files in the \OPSYS\WIN98 directory on the DVD to that folder, and then calls SETUP.EXE from there. This works perfectly on a CD, and I spent a lot of time getting it working, so I plan to keep using it. jaclaz I apologize for missing that when I read your batch file. However, I say again, why did you not just say this to begin with? I posted the syntax of the mkisofs command that I used, which included -iso-level 4. If you assumed that I was using a standard boot floppy, this would mean that I was using MSCDEX. You could have just said "-iso-level 4 does not work with MSCDEX."

No problem. Good luck!

Uh-uh!!! (Probably) Won't work!!! Original is only (proabably) good for CD's. Have you tried the Bart's JO.SYS Replacement? Not sure if this will work, but hey (and I believe it WILL work)...It does work On CD and on a floppy disk. All you need is the w98btfix.zip on that page you linked to. If this is the case then why did you not say that to begin with? And technically it is still NOT working, only partially working. I don't mind giving it a try, but I have never once had a problem accessing a DVD with MSCDEX. I can read the DVD, I can see and navigate through all of the directories, and I can type DIR and list the contents of those directories, but I cannot get any programs to run. @All I apologize for it taking me so long to respond sometimes on this thread or to run new tests, I have several projects going on at once.

Welcome to MSFN Have a look at dencorso's thread on large hard drives.

Bizarre. Logging in again fixed it, but the "Log me in as invisible" box was not checked. And I had to already be logged in to post. Thanks

I have noticed the past few times that I have visited the forum that my name has not been showing up in the users list, and if I am viewing a topic it says "1 Anonymous User." I am logged in and can post and access all of my controls, but I do not see an option/checkbox for this anywhere. Wondering how this got set that way, and how to fix it? I'm sure it's going to be something really simple that I am overlooking somehow Thanks in advance

This sequence of commands made the files/tools on the Floppy Image (Drive A:) work, but the same "Bad command or file name" error still exists for DOS tools on the DVD (Drive D:). It also bypassed JO.SYS, which allows choosing to boot from the DVD or from the HDD. (I tried "chainloader /jo.sys", but it produced an error, said the kernel must be loaded first.) Broken media or broken writer. Use high quality media. It's possible that the burner may have a problem, however if so the problem exists only for DVD±RW's. It burns all other media properly. I have been using Maxell (Nero Info Tool lists manufacturer as RITEKW01) DVD-RW and Memorex (Nero Info Tool lists manufacturer as CMC MAG W02) DVD+RW discs. This indicates hardware too. Try another hardware. *It should be noted that this problem was encountered prior to using GRUB4DOS, and is not related to the GRUB4DOS/mkisofs problems.* I have tested that particular disc in 4 different computers. I know that I do not have 4 computers all with faulty DVD drives. It may be possible, as jaclaz said, that the BIOS of these computers has trouble with Floppy Emulation on DVD's but not CD's however. I will attempt this (with a DVD RW) on another machine. I'm getting tired of wasting discs, haha.

***UPDATE 2-10-09*** The first post in this thread has been updated with new information/methodology pertaining to Windows 95 Setup. A new version of FIX95CPU.ZIP is available. Slipstreaming as discussed by BeatZero and myself above does not appear to be a viable option for applying this fix. I remain open to suggestions for improvement however.

I already answered most of those questions above. I posted the exact mkisofs syntax that I used for the last test here: I had not posted my MENU.LST, however, I did not have a problem with it, or GRUB4DOS, just with mkisofs. Here it is: As for the floppy, it is customized version of a standard Windows 98SE Boot Disk from Microsoft. Not one created in 98 that uses a ramdisk, or one from BootDisk.com, but a factory one. I added JO.SYS from the bootable 98SE CD, some files from the WINDOWS\COMMAND folder, and DOSKEY to it, along with customizing the AUTOEXEC.BAT/CONFIG.SYS menu. It works perfectly on a floppy, and also works perfectly when imaged and written to a CD using El Torito emulation. Here is a snapshot of the contents: All of this testing is being done in a real environment. I said above: and then later (after these errors Im referring to) I said to dencorso:

I'm not using ISO's on the DVD itself, just making an ISO of the DVD to mount in a VM or burn. So mkisofs is really the issue, not GRUB4DOS. I'm only using GRUB4DOS to chainload an image of a DOS floppy boot disk, then the floppy disk takes over. I actually would prefer not to have to use GRUB4DOS at all, and just use standard El Torito floppy emulation on the DVD, but as you saw above, it doesn't work for some reason. I'm not knocking GRUB4DOS though, I see a lot of potential uses for it, and I'm not as opposed to it as I originally was when I started this project. I'm very much beginning to detest mkisofs however. Normally I prefer simple things, and usually the command line is about as simple as you can get, it either works or it doesn't. But I would pitch mkisofs into the proverbial trash can. Several attempts at creating an ISO with it produced errors about filenames, and this idiotic "RR_MOVED" directory inside the ISO that should not have been there. I have created several ISO's with graphical tools and never had problems like that. Then, after finally solving the filename and RR_MOVED issues,(see syntax above), the resulting ISO/DVD had the most bizarre errors. For example: GRUB4DOS functioned properly, and chainloaded the floppy and mapped it to fd0, drive A: In the root of that floppy is FDISK.EXE, (and PATH=A:\ in AUTOEXEC.BAT) If I typed FDISK from the A:\> prompt, i get "Bad command or file name" No matter how I entered it, FDISK, FDISK.EXE, fdisk, fdisk.exe, it would not work. The same went for TESTDISK and some other DOS tools I had included.

Blu-Ray? Maybe someday, who knows? haha Seriously though, it was maddening my DVD project is 4.33 GB in size, it will fit on the DVD but I can't build the ISO in 98. And then it was all for nothing, it didn't work when I burned it to DVD. I'm going to have to set up some kind of reliable VM.

Yes and No. Those are settings that could be allright for your present purpose, but that are by no means the "right" ones for a more "complete" grldr CD (like various NT based OS, PE's, etc. A "better" example is in the given link. jaclaz jaclaz, I looked at your mkisofs command syntax. I'm pretty comfortable with command lines, but I was wondering, would you mind to explain what each one of these individual switches do, or give me a link that explains them? I understand things better if I know what's going on Also, I assume there are several different versions of mkisofs. How do I know that I have the latest and/or best version? BTW, I have now moved my project to a XP/NTFS partition so I can avoid the 4GB limit. *** EDIT *** Nevermind the switch info. I found it, just had to dig a little deeper. Trying mkisofs with the following syntax:

Nero appears to burn the entire disc, and then during the lead-out phase produces an "Invalid write state" error. I don't remember exactly what output MagicISO gave. The discs then sometimes appear to have the files on them, but they are corrupted, or the disc appears blank, but is not, and cannot be "erased" with Nero. I turned up a thread somewhere that advised making sure your DVD drive was in DMA mode, and gave some instructions for doing this. I looked into it, but I am using the Intel Application Accelerator and my settings are different than a system without it. The IAA software says my DVD drive is operating in UDMA-2 mode.

I apologize for bumping this old topic back up, but I just discovered something that I found to be hilarious. While a visit to MySpace with Windows 98 SE, Firefox 2.0.0.20, and Flash Player 9 will get you the error that is pictured above.... A visit with Windows 95 C, Firefox 1.5.0.12, and Flash Player 7 produces no errors at all.

Thanks for the links, I had been wondering whether or not I had the last 6.x version of Nero. Ill try them out, but this problem exists in MagicISO as well, and I have the latest version of it.

Woohoo I thought you might have that in mind

**EDIT 2-10-2010** In RE: Slipstreaming this Fix It appears that this issue cannot be fixed by slipstreaming. Slipstreaming does not allow the VMM32.VXD system file to be properly compressed during the first reboot. If the updated files are introduced to the system before the first reboot and the IOS error take place, WININIT will fail to combine various VXD's into VMM32.VXD. Text of this post left for further reference. I thought about adding some other things, but I don't really want to go overboard. I prefer to keep things simple. Adding important Microsoft updates I agree with, but I don't want to get into the realm of a "Service Pack," there's already one of those listed on MDGx's website. Also if we did that, I would want to have a method to select which things are installed and which ones aren't, that has always been my complaint with "cumulative" update packages. I do have some ideas though, and I will look over some of the other Microsoft updates for 95 to see what might be added. On the memory issue - there may be ways of tweaking it to work (per the methods given in dencorso's thread). However, I was never able to get any of those memory tweaks to work on my 98SE system. I purchased RLoew's patch, and I've never had another problem. I know some people out there have a problem with paying for a patch, but personally I only recommend this method. I have no problem whatsoever giving someone fair compensation for good work and the time they put into it. I should also mention an experience that I had when I was first looking into the 98SE RAM issue. I set up my system with 1.5GB of RAM, and I tested both Gape's Service Pack and RLoew's demo patch in separate 98 installs on the same machine. Gape's Service Pack did not correctly display the amount of RAM installed, I think it showed 1224MB or something like that (it's been a while), and the system seemed to be unstable. RLoew's patch worked flawlessly however, so I decided that I would buy it. Later I also tried installing the demo patch to the same 98 system as Gape's Service Pack, and the two seem to be incompatible, the amount of RAM was still incorrectly reported and the system seemed unstable. I do not mean to disparage Gape or his Service Pack in any way, Ive got a lot of respect for him because he spent his time making something like that to distribute freely.

**EDIT 2-10-2010** In RE: Slipstreaming this Fix It appears that this issue cannot be fixed by slipstreaming. Slipstreaming does not allow the VMM32.VXD system file to be properly compressed during the first reboot. If the updated files are introduced to the system before the first reboot and the IOS error take place, WININIT will fail to combine various VXD's into VMM32.VXD.

Lite-On DH-20A4P Using Nero Ultra Edition 6.6.1.4 / MagicISO 5.5. Build 276 Using maxell DVD-RW's and memorex DVD+RW's.

Im GLAD you brought that up. That's a whole other problem. For some crazy reason I cannot burn DVDRW's. I have the hardware, and the software, and the discs, but something just isn't working right. I didn't know who or where to ask about it, unless I asked one of you guys (since I'm running 98), so I just figured I would work around it.

Bought a copy of Virtual PC 5.0 (Build 350) on eBay the other day. I have installed it on 98SE, but haven't had much time to play with it yet, so I can't yet report on its functionality. In reference to the OP and some of the earlier discussion about 98SE compatibility, here is an excerpt from a document I found online (I dunno, this may have come from one of jaclaz's links, don't recall now) : So if you're trying to use VPC 5, make sure it's 5.0 or 5.1.

@ jaclaz Ok. I read through most of the GRUB4DOS Wiki, and the GRUB4DOS Tutorial at Boot-Land. Downloaded grub4dos-0.4.4-2009-06-20.zip. Downloaded bcd111.zip from here to get mkisofs. Unzipped grub4dos to its own folder, and put mkisofs in that folder as well. Following the instructions on this page, I assume: 1. That the iso_root folder must be in the dame directory as mkisofs, and should contain grldr, menu.lst, and all of the files & folders to be included on the CD/DVD. 2. I need to run the command mkisofs -R -b grldr -no-emul-boot -boot-load-size 4 -o grldr.iso iso_root from the GRUB4DOS directory in a DOS box. 3. This will create a bootable ISO that I can burn to a disc or load in a VM. 4. Only the size of the iso_root folder will affect whether or not the ISO is a CD or DVD image, otherwise there is no difference. 5. I can edit the ISO image with MagicISO or another program after it is created. Please correct me if any of my assumptions are wrong. Since you said mkisofs is the worst part of this, I decided to try to learn it first. Then I'll worry about my menu and so on. If this works, I can use a CDRW to test with until I get it perfected.

No problem. Thank you for spending time helping me with my pet project

**EDIT 2-10-2010** In RE: Slipstreaming this Fix It appears that this issue cannot be fixed by slipstreaming. Slipstreaming does not allow the VMM32.VXD system file to be properly compressed during the first reboot. If the updated files are introduced to the system before the first reboot and the IOS error take place, WININIT will fail to combine various VXD's into VMM32.VXD.

Better late than never... I can confirm ALL of your results Petr. NDIS.VXD v. 4.00.1113 from DUN14-95.EXE fixes the Q312108 error on ALL versions of Windows 95, and when combined with the AMDK6UPD.EXE HotFix can be used to run Windows 95 on >2.1GHz CPUs. I have created a scripted installer for all of these updates, FIX95CPU, which can be found here. FIX95CPU can update all versions of Windows 95 now, thanks to your patched files for 95 RTM. Thanks for all your efforts!