Content Type
Profiles
Forums
Events
Everything posted by LoneCrusader
-
Problem? I don't see "IDE" anywhere in what the OP had posted, and somehow I don't think SATA "RAID" is going to help run Windows 9x.
-
No problem. I will be most anxious to hear your results. As I noted I have not been able to get that installer to run on a 98SE system (and I was using an Intel-manufactured i865 board when I tried to run it). I don't remember the exact problem now, I think it was a "Device attached to the system is not functioning" or a "missing export" or something like that when it refuses to run. Don't think I ever tested it on Windows ME. I reverted to the older one that works and haven't experimented with it since.
-
Yes. 98SE Support continued until AT LEAST the 875 Chipset (using version 6.3.0.1007 of the INF Update utility), because I have several 875 Chipset motherboards that work with 98SE. 95 and 98FE support ended with the 845 Chipset (and version 3.20.1008 of the INF Update Utility). There is a package at Intel's Website that CLAIMS to support Windows 98SE/ME and claims support for up to the 925 Series Chipset, HOWEVER, I cannot get the installer to run on a 98SE System. I've been meaning to dig deeper into the issue, but haven't had the opportunity. Maybe someone would care to inspect the file and see if there is anything useful for Windows 9X in it?
-
To use Windows 95 on >2.1 GHz processors you will need my FIX95CPU patch. As previously noted it is in the "member projects" section. If you can set your SATA Hard Drive to IDE compatibility mode, then you may have some chance of loading the OS. Otherwise you would need RLoew's SATA patch. You will have to live without drivers for your motherboard as there are no Windows 95 drivers for Intel Chipsets later than 845.
-
If you can figure out which updates are language specific, you can try requesting the HotFixes through MDGx's HotFix Request Form. Just enter the MSKB article numbers from the language specific updates and when you're redirected to Microsoft you can choose Swedish if they are still available. Good Luck!
-
Well, there is a free version of 98Lite, but its capabilities are limited. RLoew's tools are not free. So you're left with this. W98_Slip. Good Luck!
-
There is 98Lite, which claims to support WinME as well. Other than that, the only tools that I know of that could be used for this are "slipstreamers." This would be a very complicated and involved way of achieving what you want, as it must all be done by hand, editing INF's, running & editing batch scripts, etc etc. No fancy GUI app with checkboxes. There was an attempt to create a 98SE slipstreamer here on the forum, but I don't know if all of the required components are still available, or how much success it achieved. I have a special set of slipstreaming tools that I have purchased from RLoew...
-
How to launch a customized version of MSBATCH.INF
LoneCrusader replied to Alb's topic in Windows 9x/ME
I have no experience with VIA Boards; or with systems using a combination of IDE & SATA drives (at least not yet ) so I don't know how much more help I can give you. You should check the settings for the IDE & SATA controllers in the BIOS. I would think that if you can use your optical drives in Linux, then this should not be a problem, but the Secondary IDE channel may be disabled, or otherwise set to something that Win98SE sees as a "non-standard" setting. -
How to launch a customized version of MSBATCH.INF
LoneCrusader replied to Alb's topic in Windows 9x/ME
I assume you have already created, formatted, and set active a partition as outlined by submix8c. First - after the first reboot of SETUP, you do NOT need to boot from a floppy or the CD. SETUP should have made the hard drive bootable. If you reboot from the floppy or CD and run SETUP again, it will start from the beginning. Second - you say you copied the contents of the Win98SE CD to a folder called C:\WIN. You do NOT need to copy the entire CD. You only need to copy the \WIN98 folder to the hard drive. If you copied the entire CD, then called SETUP.EXE in C:\WIN, then you are running the SETUP that is in the root directory of the CDROM, not the SETUP from inside the \WIN98 folder. (I've never seen this done, so it may not matter, but it also may be contributing to your issues. ) -
How to launch a customized version of MSBATCH.INF
LoneCrusader replied to Alb's topic in Windows 9x/ME
You must place your customized MSBATCH.INF in the \WIN98 folder with SETUP.EXE and the .CAB files. If you have done this, SETUP will use it automatically without specifying it as a command argument. -
Just a quick thumbs up from a Windows 9X DieHard. More power to you all for hanging on to what you like and refusing to simply go with the flow. This is the greatest obstacle for us 9x'ers as well.
-
Actually, chances are it won't fail me. Because after that particular learning experience and the mess that MKISOFS made of my project, when I'm creating a CD/DVD that I plan to use (or use part(s) of) in DOS I PLAN AHEAD and use 8.3 filenames and so forth.
-
Really? Not this argument again! I'll stick with MSCDEX until it fails me, which it has not. And MSCDEX should already be on the OP's system as opposed to looking for a 3rd party tool.
-
You can load MSCDEX.EXE to access optical drives. There are DOS USB Drivers, but having never used them myself, I will leave that one for others who have more experience with them.
-
Because NUSB 3.5 (and by extension the Service Pack) replaces all of the USB Driver stack files. That includes ALL USB devices, not just storage. If one installs either of these packages without first removing devices, it can lead to problems, such as those described by Drugwash in the NUSB thread.
-
The key word is Remove followed by the word (ALL)I believe the confusion arises from the differences between NUSB 3.3 and NUSB 3.5. NUSB 3.3 and EARLIER only require removal of USB2 and USB Storage Devices & Drivers. NUSB 3.5 and likely any FUTURE versions require removal of ALL USB Devices, period. @PROBLEMCHYLD Might help to quote maximus-decim on NUSB 3.5 instead of 3.3.
-
For the record I do sympathize with you on this. I have often been irritated by downloaded files not having their original file attributes, as it is useful for version control or to differentiate between different sets of files with the same name downloaded from different sources. (Example - recently I was searching for the absolute oldest USB2 driver stack that existed, with the hope of finding a stack that could be loaded on Windows 95. I found several older stacks on various FTP sites (files dated late 2001- early 2002) that I needed to keep organized by their original attributes, but when downloading, the dates were naturally set to the current date. Very frustrating, and an organizational nightmare! ) As you encountered file timeout errors, I would suggest setting your software to only download one file at a time, especially for "forensic accuracy." My FileZilla was set to download one file at a time, and I encountered no timeouts or errors of any kind. (Of course it is possible that there were unreported issues, as you pointed out.) If this does not prevent the errors and/or changed attributes, then I would suggest trying to re-download the affected files separately.
-
Confirmed as counted from the \Win98 folder. Confirmed as counted from the \Reskit folder. I also downloaded with FileZilla 3.5.3 under XP.
-
The fact that few people do this does not make the error less significant. That is all a matter of opinion. I don't use nVidia cards, so I can't address this specific issue. But if I encountered such problems with my ATI cards, I would certainly not be happy, and probably would not consider it "minor."
-
Hang on a sec, I think I may have misread. I thought you had found a newer Win2K "USBHUB20.SYS." If it is indeed just "USBHUB.SYS" it will replace a 98SE USB1 driver stack file. Not to say that it may not work fine under 98SE, just needs more extensive tests. Trust me, I've been seeing a lot of headache with USB driver stack files lately. Not as much as someone else I know, but enough.
-
The specific bug I saw mentioned in those links seems to only apply to a USB1 modem under Win2K. Windows 9x has it's own native USB1 driver stack and AFAIK does not use the USB2 drivers at all for USB1 hardware. Probably needs further/broader testing. EDIT: Misread. See next posts.
-
No Classic Start Menu! At least Vista has this You bet I'm doing it already. Just bought a pair of never-used A7V600-X motherboards (I love those boards) for a trifle (DDR, no SATAII, who, but one of us, would want them?)! Yes, I too have accumulated quite a stockpile of Windows 9x compatible hardware. Motherboards I think I have covered. (My girlfriend called me a "motherboard hoarder" the other day LOL ) High-end AGP video cards and RAM are my biggest concerns right now. Especially given the fact that Kingston DDR RAM is NO LONGER AVAILABLE from Newegg
-
Unforeseen Problems? Such as? What documentation do you have of this? I am well aware of discrepancies in various KB articles, but, until I see documentation stating otherwise, I will accept Q282901 at face value. Well, since Petr did not state that he didn't have the files in English, then I'm not convinced that he does not. :angrym: If I were Petr, I wouldn't send you any HotFix that I had after the "less than courteous" way you reacted to his solving the Q312108 issue. You were blatantly incorrect, as I have now proven.
-
(FIXED + SOLVED) The NTKERN.VXD, MMDEVLDR.VXD device loader(s)
LoneCrusader replied to PROBLEMCHYLD's topic in Windows 9x/ME
Wow... I was just shooting in the dark with that. Almost didn't post it, I figured people would think it most illogical. Anyhow, you're welcome!