Jump to content

jimmsta

Member
  • Posts

    391
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by jimmsta

  1. An NTFS read-only driver is fine for reading ntfs volumes. I went ahead and researched to see if it would be possible to run 9x on top of an NTFS filesystem. In short: maybe. Long version follows:

    First and foremost, a lot of this research was conducted over a year ago, so I might be a bit rusty bringing all the things I learned together into a simple, easy-to-read post, but here goes... If we were to write an NTFS driver for Windows 9x, we'd have to be able to add it as a service (or VxD), at vmm32.vxd's load. This means that we'd have to write a simple DOS-based NTFS read/write driver (TSR application), and a corresponding 32-bit VxD to be loaded within Windows. The problem with this approach, however, is that you're still relying on DOS to handle loading the OS through NTFS. I got to thinking about this issue. I know that right when win.com is called by io.sys, Windows loads vmm32.vxd, which loads up a 32-bit dos layer on top of the 16-bit dos. From there, it loads up any remaining VxD files found in SYSTEM\IOSUBSYS\, and loads user.exe/user32.dll, krnl386.exe/kernel32.dll. So, there's a space of time where the system is in 16-bit mode, then loads up VxD services, and enters protected mode. A hack to win.com would be preferable, possibly re-packing vmm32.vxd with an NTFS driver would work, but I haven't the time nor the patience (or know-how) to try that out. There's also the possibility to replace the io.sys DOS layer with a 32-bit DOS layer, created by taking certain files from a Windows 95/98 installation, and making the system to boot directly into 32-bit mode (DOS VM mode, to be precise). Then, from this 32-bit environment, patch win.com to load only the krnl386.exe file and all remaining startup items (as vmm32.vxd and all system services are loaded as part of the 32-bit dos layer.

    So, to conclude, yes, there's probably a way to update Windows 9x to support NTFS. It's not probable to happen, though, especially since it's very complex to implement (and probably very very incorrect according to my post here).

  2. Cross posting this one. I posted to main thread by accident.....

    Is it me or is something wrong in SVCPACK.inf? Using 1.6.3rc1 (also same with 70814a):

    [SetupHotfixesToRun]
    HFSLIP.CMD
    0_RogueSpearsRuntimesCF.exe
    oemscan.exe
    VMwareTools.exe
    HFSLIP.CMD

    I'm also attempting to track down an issue where permissions are being changed on "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies". Could HFSLIP be the culprit? I'm not pointing fingers yet, I am still backtracking to get a good build first. Only changes that come to mind are versions of HFSLIP and versions of RogueSpear's runtimes (RogueSpearsRuntimesCF & RogueSpearsRuntimesPart2) used. AND OF COURSE any additional MS Hotfixes that I added.

    Take a look at the contents of HFSLIP.CMD. In mine, I've got this line: "IF EXIST %SYSTEMROOT%\HFSLIP.TMP GOTO :PART2", which indicates that the script is supposed to be run at least once already. I think what you're seeing is normal. Also, even though I know this issue has been addressed to death, but having underscores in addon names could be causing problems. I myself use RogueSpears' runtimes, and haven't had any problems in the local policy settings. Strange.

  3. I'll just give you my 2 cents: For older systems that need new drives, due to drive failure, or low disk space, I will sell an 80GB drive, and clip it using the jumpers on it. If the system is so old that it does not allow 32GB clipping, I will use the Drive Overlay software, which usually comes with all retail packages of hard drives. The Drive Overlay software is software that will translate the full hard drive's size in LBA back down to CHS measurement. It does have the side effect of costing a few more CPU cycles for every byte read, but provides the end user with the ability to handle at least 128GiB - and with the 48-bit LBA patch, I'm somewhat certain that you could see the whole drive for what it is. Albeit, formatted with FAT32.

    I realize that this doesn't help any, especially if you're really after the older 10-20GB drives. I've been unable to get drives that small for years now. Perhaps grabbing a few 2.5" notebook drives + adapters would be appropriate - you'll probably have better luck finding a new 20GB 2.5" IDE drive than a 3.5" drive.

  4. I wandered into VMWare and ran a Windows 95B virtual machine. I enabled debug logging, and watched the log fill up - it seems that VMM32 is what controls the CPU functionality in 9x. There's this topic over on boot-land: http://www.boot-land.net/forums/index.php?...d&pid=15326 which is essentially how to make your own 32-bit DOS using Win9x files.

    I went ahead and created this 'new' DOS... When used, it is essentially what happens when you create a dos-box in Windows 95 - Windows 95 initializes a new DOS session, in protected memory. An actual multi-tasking 32-bit DOS. Of course, the limitations are still present - it seems that the services within VMM32.VXD in windows 95 hold the key to how the kernel gains access to the CPU. I'm certain that such a project IS possible, but it would take YEARS to get it working. And what definition of 'working' do I mean...

  5. Hey. I just came across this pack via referral to another unofficial support project.

    I have a computer with a dual-boot (via Bootmagic) of Win98SE, and WinXP Pro+SP2. I'm glad to have run into this site. :D

    Anyway, I just have a couple questions about this power pack.

    1. Does it support Revolution Pack ver 7 (98se) and 98SE2ME? (If 98SE2ME is, should I install it first or the power pack?)

    2. Is DOS support still intact?

    3. Is there a FAQ I can refer to for this?

    4. Would it be possible to slipstream this into a Win98SE installation CD or will it have to be a seperate product to use?

    5. Is that full download v5.05?

    Thanks in advance.

    The Power Pack is just a collection of patches. Nothing much more than that. It contains the Revolution Pack 7, and various other patches. It is considered to be a package for those in a hurry, or those that don't want to go through the stickys and grab the right files for their OS. It can also be easily updated through its W9xBuild.bat script. It is a separate product, intended for use on a separate CD from the Windows CD.

    I hope that I've answered all your questions.

  6. Personally, I prefer RogueSpear's .NET 1.1/2.0/J++ package, plus his .NET 3.0 Lite package. The main reason is because all the new .NET patches from Microsoft for version 1.1 and 2.0 have been slipstreamed into the pack, so there's not as many conflicts or screwups that can occur when installing those patches. RogueSpear posts on ryanvm's forums as well (I think).

  7. I've released a new version to correct some broken files and various little bits that needed updating. This new version also adds the unofficial nVidia drivers that have been released for all nVidia GeForce cards.

    To update from an older version: Run W9xBuild.bat, and type 2 at the prompt:

    post-54728-1185062391_thumb.jpg

    Press enter, wait for the ~4kb patch to download and extract, then choose option 1 at the prompt:

    post-54728-1185062446_thumb.jpg

    Wait a bit, and it'll be ready for use in a little while - the total patch size is approx. 20MB in size.

    You can also grab a base version to build a new copy of the software off of, here- http://www.win9xpp.org/library/w9xppv505.zip. Follow the instructions in the original post for more info.

  8. It may be that Windows setup is tripping over the underscore, or the combination of the number with the underscore. Does the problem persist if you remove it?

    Works fine now. Thanks for the heads up on the underscore - that was certainly the issue... although, despite the fact that the files in the original build were in the HFGUIRUNONCE folder, they ran at T-13, instead of first bootup. Now, with the new build (see attached hfslip logfile), it all runs at the proper time - on first bootup, with no errors at all. * I did replace the older Dot Net 1.1 + Dot Net 2.0 exe files with RogueSpear's integrated 1.1sp1/2.0/j++ package, and renamed that to dotnet.exe. *

    Again, I praise everyone that is developing this script. It's truly a timesaver, and despite the issues I've had with it, I will continue using it for a long, long time to come. :P

    HFSLIP.zip

  9. Is there even a DOS out there that supports multiple CPU's? I'd think that that'd be the first place to start. Obviously, MS-DOS does not support that functionality, and you'd need to re-write the entire 9x kernel to support multiprocessing, as it was not designed with MP in mind. I'm betting that someone, somewhere, in the mid-90's created a driver for 9x that enabled the use of 2 or more processors, but there's a good chance that it was not free, and was not intended for use with today's 'x86' CPU's.

    * Most x86 CPUs nowadays are virtualized x86 implementations on top of another architecture - Intel has the Core/Core2 arch, and AMD utilizes the DEC Alpha 9 arch.

  10. Hmm... I'm having an issue getting silent installers renamed from their original names to their HFSlip'd names. As in, the original file name was 0_dotNET11SP1.exe, in the (HFGUIRUNONCE folder) but in I386 of the SOURCESS folder, it is changed to HFGUI1.EXE. The only problem is that the setup files still have the original file name, instead of the HFGUI1.EXE, so setup fails to load the files properly.

    Attached is my hfslip.log, zipped up.

    HFSLIP.zip

  11. Thanks MDGx!

    A small patch has been released to offer Maximus Decim's IE6 Cummulative update v1.5e, which he released today. I've also updated the RP7MM executable on my server to reflect Tihiy's latest release.

    You can grab the full base package here: http://win9xpp.org/library/w9xppv501.zip

    And you can patch your copy of W9xPP to the latest version by running W9xBuild.bat, and select the Update option. This option requires a 4KB download, versus the full base package's size of 739KB. After the 4kb download, you will want to run the Build option, so that you get the latest files into your package. This option will be automated in a future release.

  12. I learned the hard way that you cannot *just* update gcc using synaptic. If you try, you will end up updating your whole distribution, even if you've already got the latest packages. I'm guessing that I only found the main breaking point in Ubuntu. Otherwise, I still use Ubuntu for the server @ work (and had a horrible problem yesterday where the /etc folder grew to 14 Octabytes in size, and became unreadable).

  13. Why not download all those new hotfixes, and compare the file versions, then create a new topic (or add to one of the stickies) a list of hotfixes that are 'safe' to use on USP5?

    On the same subject, I'm thinking that if I can figure out what Gurgelmeyer did, I'd be happy to try my hand at updating the USP.

×
×
  • Create New...