LoneCrusader

What can I say, another brilliant release! Working perfectly here:

I tested rloew's PTCHCDFS on Windows 95 C with CDFS.VXD 4.00.1113, the file is patched correctly, but I discovered a few minutes ago that if the DVD contains >4GB worth of files, the "Used space:" and "Capacity:" byte counts on the General Properties tab only show as "---". If the DVD has <4GB worth of files, the byte count shows up correctly. I have not used this patch yet on Windows 98, so I do not have a reference, but I assume this is not a problem in 98. EDIT: Bizarre error not reproducable, works properly now.

Thanks for clarifying this, I wasn't sure about it.

I knew there had to be a way. I just wish I had the know-how.

I think if you deleted AUTOEXEC.BAT then Windows would generate a new blank one (not sure about that). It's never foolish to be sentimental, haha, I still have the hard drives from my first Win95 computer, the partitions died on them, but I never formatted over them or used the disks again in the hope that one day I could resurrect them. But anyhow, glad I was able to help you.

He's talking about a blank new line, as in a carriage return, or "Enter". DOS treats a blank new line as a carriage return, it's like pressing ENTER at a C:\> prompt without typing a command, you just get another C:\> prompt. For example this empty blank line ^^ in my post would produce another C:\> prompt. Check your AUTOEXEC.BAT in Notepad and Delete/Backspace out any blank lines. Or, since your AUTOEXEC.BAT is blank, click Edit > Select All and then press Delete. Once you have done this you should not be able to move the cursor from the upper left corner with the arrow keys.

I should clarify this section from above: Yep. I said Yes, meaning that I have one of these things; folders/files that would require Joliet or UDF; not meaning that I have all of these things. Here is the deepest folder: D:\DRIVERS\Video\ATI\ATI Radeon\Windows 95\8500\Install\Gart\IntelGart\setupdir\0007\Readme.txt which is 10 directory levels deep. Here is the longest path: D:\DRIVERS\Motherboards\Soyo\SY-P4I845PE ISA\Drivers\V1.0 Boards ONLY\Realtek Audio\WinNT4\SoundMan.exe which contains 103 characters. I do not have any Unicode file or folder names, and I do not have any "ridiculously long" filenames. I do however have file and folder names that have multiple periods . , Spaces, and the charcaters I mentioned before, & ! - etc. Thank you for the file, the information, and the potential solutions. But this does not have anything to do with UDF or the problem we were talking about. It is useful for the DVD boot issue, but that had already been solved back on page 3. The IS a very simple difference, addressed back on page 3 by cdob. Windows 95 does not support UDF, and therefore is not reading the UDF long filenames. And, as dencorso and I said before: Solution: Include Joliet on the DVD instead of or along with UDF. We have been arguing about this for no reason other than you keep "a$$-u-ming," as you say, that I don't know what I'm talking about when I (and others above) said my DVD would require Joliet. Any suggestions you may have for the other thread would be appreciated, should you desire to give them. That is your choice. so (...and the others as well).I don't dare risk too much from UBCD (obvious reasons) for fear of being banned. I'm already treading heavily with this "conversation" (self-warned...). Great-grandpappy always said "don't go away mad, just go away". I'm gone, but pretty p-o'd! I truly wish you success in your endeavor. Have a great day... I fail to see where you think that I am implying that you are "twisting my arm." My point is that we have been arguing for no reason about things that have already been solved or are not relevant to the problem at hand. EDIT: Found a longer path.

I apologize for the snippets, but I feel I need to address each issue separately. No I haven't. Because I just said several times above that I am running some experiments and I am not ready to create the DVD again yet! Here are two screenshots. The first one is from Windows 98 Second Edition and is properly displayed. This is what it is supposed to look like! The second one is from Windows 95 C OSR 2.5 and is truncated/translated. This is the problem! This is the whole point of the UDF discussion above! This project and this thread have nothing to do with the UBCD! I am not trying to create something similar! I do not plan to install anything from DOS except Windows, or DOS programs! Who said anything about renaming anything during installation!? You are getting off on tangents that have nothing to do with the problem at hand! Yes, jaclaz and I mentioned that earlier. I asked a question about it and DirectCD that no one has attempted to answer yet. I appreciate your suggestions and assistance. I just feel that you are not paying close attention to what has been said. For example, once again this has nothing to do with the UBCD! You keep returning to that and it has nothing to do with what I am trying to accomplish here, or the problem I am having, because the problem is 95 specific! Check screenshots above. Do you happen to know the answer to my question about this UDF reader and DirectCD that I posted above?

Yep. Apparently I only need Joliet, like I said, ImgBurn chose UDF on its own. The only reason I have been discussing UDF is for exploring the possibility of adding a UDF driver to 95. I thought I explained the problems very clearly... I won't know whether or not the problem will be cured until I actually make another version of the DVD/ISO, which I am not ready to do yet. Right now I am just experimenting with some other functions, and working on the final selection of files to be included on the second copy of my disc. Yes, the DOS Boot Floppy is only for Windows installation and running DOS tools. I am not using GRUB4DOS for this project, as I finally got the DVD booting with a normal DOS floppy, which was my original goal. But my floppy is heavily customized using those files you mention. No. But neither am I. It can be very easy to get confused trying to understand other people's projects and methods, as you don't actually have a copy of it in front of you to see what's going on. Yes, why can't things just work or at least be simple? Haha

:wacko: I repeat, my DVD WILL REQUIRE JOLIET OR UDF unless I go back an manually rename a bunch of files and folders! There are OTHER files and folders on this DVD besides just files from the 9X install CD's! Drivers, Software, Tools, etc etc. Some of them have long folder or file names. Some of them are more than 8 folder levels deep. You didn't think I got over 4GB of data just from 3 9X install discs did you? This has nothing to do with Windows setup/installation. I have had no problems with Windows installation from this disc, only reading the disc IN Windows 95 AFTER installation. I am using VPC5 because M$ disabled 9X support in their versions. You are trying to over-simplify this. If I had just copied the 9X install CD's, then the DVD would probably conform to ISO9660 and there would be no problem, But that is not the case.

I created the ISO and DVD with ImgBurn as suggested by jaclaz. ImgBurn chose ISO9660 and UDF on its own, I did not choose them. I assume UDF was required because some of my files or folders did not conform to ISO9660. I plan to recreate the DVD eventually, but as of right now I am only working with the existing one. These are just experiments, I am checking to see if everything works before creating a final product. As I said, I have found 2 problems: 1. VPC 5 will not capture the ISO, or the DVD itself. No idea on this one. 2. 95 does not properly read some of the file/folder names on the DVD, even though it previously read a CD with the same file and folder names. Logically this must be due to a lack of UDF support in 95. (CD probably had Joliet, not UDF) Solution: Include Joliet on the final version of the DVD. I plan to do this. In the meantime however, I am simply exploring the possibility of adding a UDF driver to 95.

For the heck of it, I tried adding UDF.VXD 4.10.1998 from the 98 FE cabs to the VMM32 folder, and added it to HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\VxD to see if it would load on startup. I got an error saying that UDF.VXD was damaged. I wonder if there are any earlier versions of UDF.VXD to be found, maybe from some of the 98 Betas? I turned up the UDF reader link in a search I did the other day, and also read something about DirectCD enabling the use of UDF. I have never used DirectCD, as I read a long time ago that it causes a lot of problems, but I do remember once having it installed on a 95 machine. I wonder, does DirectCD install a standalone UDF driver that might somehow be extracted from it, or is it just the same as the UDF reader?

It is possible to create a Bootable Floppy Image on a CD/DVD of up to 36MB. The required geometry is 1024 Cylinders 2 Heads 36 Sectors. I use my own CD/DVD burner. I do not know if any other CD writer will support this. FIX95CPU and DUN14-95 could both fit on a 2.88MB floppy, so as long as one was using strictly floppy or cd images for their setup, it would not be a problem. However, it would be a problem for anyone who actually needed to write FIX95CPU to a floppy disk.

I plan to recreate the DVD eventually anyhow, as I left out some files to make it <4GB before I knew ImgBurn could split ISO's into multiple files. I will see if I can get Joliet included, last time it chose ISO9660 and UDF 1.02 on its own. I don't think I will be going back and renaming >4GB worth of files with 8.3 filenames though. I find this particularly interesting. How would one do this, theoretically? EDIT: @dencorso I originally posted this thread here because of the DVD boot issue, but since the issues and discussion have dealt only with DOS & Win9X, it might fit better in the Win9X forum. If you agree, please move it for me. Thanks

Could you post the Instructions in a .TXT file? I did not have 95 or 95A to test either, however rloew confirmed that the new method for the B & C patch does not work on the older systems because WININIT cannot be called manually. I kept v1.1 in the package for anyone who might want to experiment with it on the older 95 versions, or who may have not got the 1.2 disk inserted before the IOS error is displayed (WININIT is called before/during this). There is no 2.1GHz "IOS" error, it is the "NDIS" error. To reproduce it, all you need to do is try to install 95 on a >2.1GHz system using only the AMDK6UPD.EXE files, and leave out the NDIS.VXD from DUN14-95.EXE.

Copied CDFS.VXD from 98SE (Which had a version number of 4.10.1998, guess it was not updated for SE?) and substituted it for the Windows 95 one (4.00.1112). This resulted in the DVD Drive showing up as a "Removable Disk" like a USB stick in 98SE w/NUSB, and when I clicked on it said the drive was not formatted and it asked me if I wanted to format it. EDIT: Obtained CDFS.VXD 4.00.1113 from MDGx, (Last version I could find a reference to for 95) this did not correct the error either.

Well, I'm back again everyone. After using my new DVD for several days, I have only discovered two odd problems. I have found no problems with booting the DVD or with JO.SYS, etc. I have found no problems accessing the DVD is DOS with MSCDEX or using any of the DOS tools. I have found no problems with the DVD in Windows 98SE or Windows ME. However, I am having a strange problem with the DVD in Windows 95C. In Windows 95, and only 95, some of the names of the files and folders are truncated (not like DOS with a ~, they just stop), and some of the characters in the names of the files or folders are changed, ( ex. & , ! , and a Space changed to _ ). I have previously used a CD in Windows 95 that contained these exact same files and folders, with the exact same names, and they were properly displayed. What would cause it to be different now? The second problem - VPC 5 will not capture the DVD or the ISO at all, but it functions in a real environment.

Yes, it can easily be added to the floppy and even the script, provided one already has a copy of PATCHMEM. I was mainly addressing the distribution issue.

R. Loew Electronics Consulting

How about MegaUpload (or anything other than stinky RapidShare)?Had DUN14-95.zip already tucked away... edit - oops, sorry - I see new link above... Heh, yes, RapidShare is very irritating. I only link to it until MDGx gets a chance to update the patch on his site, which he did last night.

Yep. The only limitation is the lack of drivers for 9X.

This is all very interesting I'm open to any suggestions for improvement, but I don't want to bring any moderators down on our heads. I was not around before the UBCD project was removed, and I don't know much about what happened. Feel free to PM me or email me from my profile if you wish.

I can't speak from experience on the VPC issues, however I think he is referring to VPC7 for Windows 7, not VPC2007. The MS AMD Patch works for many processors besides the 350MHz. I used it for years on AMDK6-2 550MHz systems before being forced to upgrade to 98 because of a game I wanted to play. It is also required for Pentium 4 processors, and I have used it to successfully install 95 on a P4 2.0GHz system. Above 2.1GHz, Windows 95 will crash with the NDIS error referenced in the first post. MS claimed there was no fix for this in 95, but issued a HotFix for 98FE that contained an updated NDIS.VXD. It just so happens, the NDIS.VXD contained in the DUN14-95 update also fixes the error. MS neglected to mention this. The reason for this particular project is that you cannot boot into Windows (not even safe mode) to install the MS patches. Windows will crash on the first reboot during setup. This project manually copies the AMDK6UPD files and the updated NDIS.VXD into Windows so that Windows Setup can continue normally. It may be possible to use MSBATCH to install DUN14-95 during Setup, (as discussed with BeatZero above) but you must first be able to continue setup, if the updated files are not copied after the first reboot, Setup will crash. And, if the updated files are simply placed in the \WIN95 folder before setup, or copied before setup, WININIT.EXE will crash and not properly compress VMM32.VXD.

Thanks for the feedback. Spread the word in the virtualization community that 95 is now working again. DUN14-95.EXE is too large to fit on a floppy disk, so there is no way to have it on the same "Disk" as the batch file. One solution to this might be to use an ISO editing program and add DUN14-95 to the bootable FIX95CPU.ISO so that it would be in the root of the CD image and could be accessed from there once the Windows desktop has loaded. However this would require recapturing the ISO image, as you must release it after the patch is applied to allow Setup to continue. I considered doing this, but I felt things were getting a little redundant, since I had to include two versions in the new package, and both versions contain copies of DUN14-95 in their ZIP's. While I agree it would be convenient to have the CPU and RAM fixes combined, RLoew's RAM patch is not free, so it cannot be distributed in such a manner. It is the only method of installing more than 512 MB of RAM on a 9X system that I personally recommend however. I have been using it for over a year on my 98SE system with 1.5 GB of RAM. If you decide to purchase a copy, it is worth every penny.

*** UPDATE 2-23-2010 *** FIX95CPU.ZIP Versions 1.1 and 1.2 Released! Less typing required, and a bootable ISO is now included for VM users. The First post in this thread has been updated and describes the differences in these two versions. Get the new version here: FIX95CPU.ZIP