[Eck]

Yep. And I even have about a week left on a RapidShare premium account I bought when I wasn't patient enough to wait for somebody's huge file split into a bunch of 100MB parts. I could have just uploaded it.

Still, all's well since I don't think he needed all that stuff.

[reno7]

Hello ,
to use W98_slip , on my XP'computer ,I delete 2 lines:
if not exist %windir%\system32\extract.exe goto instructions
if not exist %windir%\system32\xcopy.exe goto instructions

and I copy extract.exe and xcopy.exe in the same folder as W98_slip.bat
and IT RUNs

PS: sorry for my english , ...

[iWindoze]

Have there been any updates on this? Version .002? Or have any such projects ever actually completed?

--iWindoze

PS: I managed to slip the unoffcial SP for Win98SE using the method posted by reno7, but still saw some errors in the actual install, though they mostly seemed to revolve around the ISPs (like AOL and MSN, etc) and did not seem to cause any actual issues while installing except redundent error messages like the one about missing amsn.dll or some such.... Has anyone made any progress since?

This post has been edited by iWindoze: 29 July 2007 - 06:35 PM

[iWindoze]

/BUMP

Is glaurung still around?

--iWindoze

[Jaymo]

hmmm... i feel the need to bump this.

i really like the idea of a fairly updated 98; and although soporific (which i do feel gratitude for all your hard work) has come up with the Unattended Boot CD, i like throwing my stuff on cd... i also copy my win9x files on for se2me & revolution.... and there's not a whole lot of room left. i generally use sesp for simplicity's sake, & tack on some Maximum-Decim stuff. i've tried Auto-Patcher some & have the Unattended Boot CD (haven't used it yet).

i used to use bart's old isolinux multiboot (which doesn't work on xp) to give me the option of booting up with a home brewed presizer\savepart floppy image or 98 install image; yet defaulting to harddrive. created the iso... burned the disk... yeah... it was nice; but now outdated.

i also have an issue with redundancy, and keeping multiple versions of files where the old ones will almost surely NEVER be used (with programs that can be different).
i've dabbled with inf files some, and more or less stopped when i realized there was se2me & revolution. finding the cabs were linked and wouldn't work unlinked... bummer. i have info somewhere on what ones were linked and what each generally contained but i've let things collect i guess. need to sort.

i have no intention to take over, i just can't see this fade away so easily.
hopefully i will be able to talk with a like minded individual. maybe we can figure out somethin'.
i have seen several update packs, and like ideas i see, although i have to admit that it has been a while since i've tried some of the different update packs out there or tried to figure out their workings (life happens), so i readily admit ignorance.

i don't feel there will ever be a magical "coming together for the sake of 98" that would really benefit.
i'm not all knowing... or any other such nonsense. i just know some guys here have killer scripts; batches; infs; and whatnots. they all have their knowledge (and modesty ). i've used some of it here and there in my own installations. (don't even ask; mine is far from good enough to share.)
but i believe i still have my resources of which there were a few different sources. perhaps i'll start organizing them so i can either add them to this post or bump as need be. at least throw some ideas on the table. i even had W98_Slip once... just didn't find the time to dabble with it. -jaymo

[galahs]

I agree this project has great promise.


I am looking for a method to Slipstream gapes unofficial service pack + 98SE2ME + NUSB + LLXX's 137GB + patch


this might just be the tool for it.

makecab.exe can be found here: http://support.microsoft.com/kb/310618


I also found this information that might come in handy

Quote

Infinst.exe

What Infinst.Exe does:
It adds an inf file and the associated drivers to a Windows 98 setup share.
When Windows 98 is installed on other machines from the share, the added drivers will be
installed as if they were part of the original Windows 98 setup. These drivers may be for
any type of hardware or for additional network clients, protocols or services.
To automatically install network clients, protocols or services you will need to add them
to your msbatch.inf. This can be done using Microsoft Batch 98.

How to use Infinst:
Note: the tool requires a Windows 98 setup share with write permissions.
It will not add files to a CD-ROM.
1. Start the tool by double clicking it.
2. Enter the path and filename of the inf you wish to add to Windows 98 setup.
3. Enter the path and filename for Setup.exe on the Windows 98 setup share you wish
to add the inf to.
4. Click Add Inf.

Infinst does the following when adding an inf:
* It copies the inf and the driver files needed (listed in the CopyFiles= sections of
the inf) to the Windows 98 setup share. If a catalog (.cat) file or
layout (.inf) file is specified in the inf, Infinst also adds it.
* It adds the appropriate entries to the following files: all previous inf files with
matching PnP IDs, the Custom.inf, and the Infinst.log. The files are changed as
outlined below.
Note: Infinst copies all files listed in the inf's CopyFiles= section to
the setup share; however Infinst does not automatically process any infs listed in
the CopyFiles= section. These infs may need to be added manually for setup to
complete successfully.

How Infinst.Exe works:
1. It creates two directories in the Windows 98 setup share. One (Oldinf) is for infs
that are replaced by new infs of the same name, and one (Wininf) is for storing
the infs included with Windows 98.
2. It checks the versioning of the infs to be added (only infs with version $CHICAGO$
should be added, although Infinst.Exe will correct certain versions to $CHICAGO$
automatically).
3. It searches the inf to be added for its PnP IDs (Plug and Play IDs).
4. It compares the found PnP IDs of the new inf with the PnP IDs contained in all the
infs that are in the Wininf directory.
5. If an inf with a matching PnP ID is found, Infinst.Exe copies it to the directory
containing the Windows 98 setup files, as long as there is not an inf file of the
same name there already.
6. It compares the found PnP IDs of the new inf with the PnP IDs contained in all the
infs that are contained in the Windows 98 setup share.
7. If an inf with a matching PnP ID is found, the matching PnP IDs are commented out.
8. It copies the new inf and all necessary driver files to the directory where the
Windows 98 setup files reside.
9. It edits the Custom.inf file. Note: Infs and drivers of install media classes
(such as net) are added to more sections of the Custom.inf than those of other
classes, because they may be needed earlier in setup.
10. It appends to the Infinst.log.

Infinst.Exe can add infs for single or multiple PnP device(s), whether or not they are
supported by Windows 98. Drivers added by Infinst.Exe should install properly whether
Windows 98 is setup locally or across a network, regardless of whether it is a clean
install or an upgrade. In other words, you can install all the infs you want and run
setup any way you want.

Design Limitations:
1. Adding an inf with the same name as one included with Windows 98 or one previously
added will eliminate all functionality of the previous inf, regardless of PnP IDs.
2. You must have write permission to the location of the Windows 98 setup files for
Infinst.Exe to work. (I.E. it will not work on a CD-ROM).
3. Adding an inf containing the same PnP IDs as an inf already included in the setup
share will result in eliminating those PnP IDs from the already included inf.

Trouble Shooting:
1. When adding an inf to a Novell server, Maximum File Locks per Connection must be
greater than 600 or infinst will be unable to add the inf correctly.
2. All infs and drivers being added must not be marked as read only.

This post has been edited by galahs: 08 December 2007 - 05:10 AM

[galahs]

I am on the quest to build a slipstreamed version of the best Windows 98 Second Edition I possibly can.


I am thinking of one that has all the official MS hotfixes, all critical Unofficial hotfixes, + compatible WinMe files + adding Native USB support + copy2GB patch + 48bit LBA for larger disk drives over 137GB


Being an industrial designer, I love to make things simpler and easier to use. I find having to apply a series of updates to get Win98SE back in shape after a reinstall frustrating to say the least.

I know there are other unattended installations around (but they all add 3rd party apps) but I want one that just installs the most up-to-date Win9x Operating System possible. Nothing more, nothing less. No IE6, DX9 or WMP9. These should be left to the user to decide on.

Now my problem is I need to work out how to slipstream additional files not originally included in Win98 CD (ie. adding new files, not replacing existing ones). Do you know how this would be possible?

[galahs]

These threads have some more interesting ideas.

http://www.msfn.org/...-CD-t33815.html

http://www.microsoft.com/technet/archive/w...8.mspx?mfr=true

http://www.hermit.cc...win/hobat98.htm


Even more reading...

http://www.microsoft.com/technet/archive/w...d.mspx?mfr=true

http://support.microsoft.com/kb/214727

This post has been edited by galahs: 08 December 2007 - 08:31 AM

[computerwizkid]

How can I modify this for slipstreaming files into Windows ME since I need to because of my Win2k8 Project at WPC?

[glaurung]

galahs, on Dec 8 2007, 07:49 AM, said:

Now my problem is I need to work out how to slipstream additional files not originally included in Win98 CD (ie. adding new files, not replacing existing ones). Do you know how this would be possible?

(I answered your PM, but figured I should reply on the forum as well)

I haven't had time to do any further work on the w98_slip project for quite a while.

Adding extra files is complicated because the install process depends on the file being referenced in at least three different places: layout*.inf, copy*.inf, and the individual inf file that actually covers the components you're adding. Plus, of course, you have to include any necessary registry keys (especially instructions for self-registering files) for the new files.

Layout* and copy* appear to need to be parallel (so a file referenced in layout1 needs to appear in copy1, it can't be in copy2 or the initial file copy phase of setup will fail).

You could in theory avoid the requirement that the new files appear in both layout* and copy* by forcing the file copy process to happen after setup reboots (using a runonce command), and creating your own additional layout file that points to a cab where all the new files are stored. But making everything go through runonce adds a layer of complexity.

Alternately, you could use custom.inf. There is basically no documentation on this online that I can find, but if a file named "custom.inf" appears in the setup directory, setup will perform any file copy commands contained in it automatically, expecting to find the files whereever custom.inf tells it to look. (Custom.inf was originally intended for OEMs to allow them to automatically install drivers and driver infs). So just put the new files in a new cabinet, create a custom.inf that grabs those files and puts them where they belong. I'm not sure if custom.inf supports adding registry entries, I'd suspect it doesn't. You can find a model custom.inf in the intel motherboard drivers for win9x; the main wrinkle to using it is that for at least some files (including disk driver files and all infs, IIRC), you have to specify them being copied twice, once to setup's temp directory where precopy is expanded to (there's a special section for that in Custom.inf), and again to where they are supposed to ultimately go.

Either way, my thinking on this, before I set it aside, was to create a few new files in the setup directory: a newstuff.cab (containing all the binaries we're adding), newfiles.inf (layout file), and newstuff.inf (containing either just the registry information, or registry information and file copy directives), plus custom.inf if I decided to use that. Doing it that way rather than trying to shoehorn things into the existing layout* and copy* system would, I thought, be more flexible and also easier to script automatically, since we'd be building the inf files from scratch rather than trying to amend existing ones.

[glaurung]

computerwizkid, on Dec 8 2007, 12:50 PM, said:

How can I modify this for slipstreaming files into Windows ME since I need to because of my Win2k8 Project at WPC?

First, Considering that W98_slip has lain fallow on my hard drive for over a year now, I doubt I will ever have the time or inclination to adapt it for an OS I don't own. That said, since I don't own ME, I have no idea of what problems would arise from trying to apply this slipstreaming method to it. If ME's setup files are digitally signed, for instance, then you're probably SOL.

THe place to start in adapting w98_slip to work with ME would be to look at my first follow up to the original post in this thread, in which I described some of the ins and outs of SE's cab files. Read up on Cabinet files and makecab (the Cabinet SDK documentation isn't the best but it's still the place to start) so what I said in that post makes sense, and then experiment with ME's setup files and see if they behave the same way as SE's file do or not. The size of the cabs doesn't matter so much as whether they are linked in a chain or not. If ME's cabs are not linked in a chain the way SE's are, then you'll have to do significant extra modifications to make W98_slip work for WinME.

Assuming that the ME cab files are chained together, then making it work with ME shouldn't be too terribly hard; the main thing you'll have to do is modify the scripts that generate the makecab directive file so that they create cabs that break at the breakpoints you find in ME rather than the breakpoints found in SE.

The hard part, of course, is finding all the little quirks that need to be addressed. For instance, a short file name in SE contains a parenthesis, IIRC, which is a character that Minitrue treats as special; the entry for that file in the file list had to be specially handled to take out the parenthesis before I could use Minitrue to process the entire file list. ME may or may not have similarly named files, but you can be quite sure it has something quirky.

W98_slip is not nearly as hard to hack as, say, HFslip; as batch files go, it's pretty basic, and the hardest part for me was learning to use Minitrue to do the donkey work of manipulating file lists into makecab directive files and layout*.inf files. That will be the hard part for you, too -- fortunately, minitrue's documentation is fairly complete and well-written, and you'll have my original minitrue scripts to crib from.

[galahs]

I noticed with Gapes Unofficial Service pack, he claims tou can semi slipstream some updates by simply putting them in the Win98 setup folder.

Does that mean Windows 98 has a built in support for slipstreaming newer versions of existing files?

[galahs]

I also note that you can create a bootable cd of 98lite


Maybe it would give some hints as to how we could make a slipstreamed win98SE. IF 98lite unpacks all the files, then installs windows, it might be possible to replace the existing files with newer versions, this would basically be a slipstreamed version of Windows.

Quote

There is a trick to do that, but you can only choose one version (micro, sleek, chubby etc.), as all the win98 files will be changed to install only one of the 98lite enterprise license version

First boot from floppy disc (assuming you have the latest 98lite on floppy):

* at the A:> dos prompt type "98pro47" this will start the installer up..

* select "install"

* type in your key code to allow the installer to decompress

* use the default path for the files if you want, namely "c:98setup"

..at this point the installer should decompress and dump a few files onto the clean hard disk in the c:98setup folder.

* at the A:> dos prompt type "C:" to change to the C:> dos prompt.

* at the C:> dos prompt type "cd 98setup" to change to the 98setup folder. The dos prompt should now be C:98setup>

* at the C:98SETUP dos prompt type "98lite /cd" [You can pass a switch command to the installation, for older hardware ie: /NM switch - this is passed to the windows setup and means "no minimum", or /NG switch also (no VGA graphics in 98lite) just to lower the burden on the system. or any other switch ] to start 98lite - it should fire up and show you a couple of screens of disclaimers etc and then stop with a menu of options with the first option being "1. Clean Install"

* press the "1" key to choose the clean install

* 98lite will then ask you to insert your win98 CDROM and it will copy all of the windows setup files from the CDROM to the c:98setup folder

* 98lite will then ask if you want to copy the win95 explorer files to the hard disk in case you want to use the MICRO or SLEEK desktop option. This is an optional step - but if you insert your 95 CDROM or tell the installer where the files are (e.g. you may have them on a floppy or another hard disk) the files will also be copied to the C:98setup folder

... at this point you should now have a C:98setup folder that contains:

1. the 98lite program files

2. the win98 installation files, and optionally,

3. the win95 files (explorer.exe v4.00.950, Shell32.dll v4.00.1111 and Comdlg32.dll v4.00.951)

... 98lite is now ready to install windows for you and it will start the process itself - you can also stop here if you want, and make it a bootable CD.

* if you have the original bootable CD for windows 98, use Winiso or other program to make an ISO file, and edit the ISO image, then rename the folder in C: drive from "98setup" to "win98" and replace it into the ISO image (delete the original win98 folder in ISO image). burn the image to Disc.

That's all!
now you have a bootable CD with your 98lite installation.

I have also been looking around for EXE and INF tools (because I sure don't want to learn too much coding)

I found that Windows 2000 and XP have an EXE maker built into them called Iexpress.
There is an older version available here: http://support.microsoft.com/kb/237803
A guide to using Iexpress can be found here: http://babek.info/libertybasicfiles/lbnews...34/iexpress.htm


For creating your own INF 's I found this handy freeware tool. INF-Tool --- http://www.inner-smile.com/dl_inf.htm
Some good information on INF files can be found here: http://www.ryston.co...NF_web/main.htm
More info here: http://msdn2.microso...y/ms790220.aspx


And here is a good guide to making Batch files (.bat)
http://home.att.net/.../dos_batch.html
The only decent Batch Creation utility I have found is Shareware (15 uses) called Easy Batch Creator --- http://www.octosoft.co.uk/ebb/



Hope this is helpful.

This post has been edited by galahs: 09 December 2007 - 08:04 AM

[glaurung]

galahs, on Dec 8 2007, 11:06 PM, said:

I noticed with Gapes Unofficial Service pack, he claims tou can semi slipstream some updates by simply putting them in the Win98 setup folder.

Does that mean Windows 98 has a built in support for slipstreaming newer versions of existing files?

Yes; there's no need to use w98_slip unless you want to have a neat and clean looking setup folder... which some people enjoy having. (also if your setup cd is jammed with extras, integrating updated files into the cabs takes less room).

If you just put the updated versions of the files into the setup folder, setup will preferentially grab files from the folder before rooting around in the cabs for the same file. This behaviour is the basis for how 98lite does its magic; it modifies existing *.inf files and drops them in the setup folder.

[glaurung]

galahs, on Dec 8 2007, 11:12 PM, said:

I also note that you can create a bootable cd of 98lite

Maybe it would give some hints as to how we could make a slipstreamed win98SE. IF 98lite unpacks all the files, then installs windows, it might be possible to replace the existing files with newer versions, this would basically be a slipstreamed version of Windows.

98lite only unpacks some of the inf files (about a dozen or so), which it then modifies to make certain components removable. You can do much the same thing yourself if you've learned how to hack inf files. Removing some unwanted components is childishly simple (comment the relevant files out of setuppp.inf), while removing others takes a lot of work (eg, de-integrating internet explorer).

Because 98lite is payware, it puts code in the updated infs that causes them to be automatically deleted once setup has completed. "98lite /cd" just tells it to not automatically launch setup once it creates the modified .inf files, which means the modified files remain on disk for hacking, integrating into the precopy*.cabs with w98_slip, burning to cd, or whatever.

[galahs]

Thanks for the info glaurung and replying to my PM's


My biggest concern has been that I wanted to ensure ESDI_506.PDR (LLXX's edited Version .2225) was slipstreamed into my Windows 98 SE cd allowing Win98 to support Hard Disks bigger than 137GB. So if I just copy that file into my Win98 folder and burn it to a disk it should slipstream into the installation replacing the original version?


If just updating the original files with newer versions was all that was required your slipstream method would be perfect. Unfortunately many updates need to include additional files.





The 2nd best option would be a 1 off post install update that installs IE6SP1 and cumulative updates, DirectX 9.0c (December 2006), Windows Media Player 9 and all of Windows 98 SE's hotfixes (Official and Unofficial)

Microsoft produced an update cd in 2004 that did this. If it could be updated with all the future releases it could be perfect. Read more on the CD here:
http://www.msfn.org/board/MS-Windows-Secur...04-t108981.html

[glaurung]

galahs, on Dec 11 2007, 10:13 PM, said:

Thanks for the info glaurung and replying to my PM's

My biggest concern has been that I wanted to ensure ESDI_506.PDR (LLXX's edited Version .2225) was slipstreamed into my Windows 98 SE cd allowing Win98 to support Hard Disks bigger than 137GB. So if I just copy that file into my Win98 folder and burn it to a disk it should slipstream into the installation replacing the original version?

Yes, it should.

As you say, adding additional files is the tricky part. For files that don't need registry entries, like tweakui or extra fonts, custom.inf is the way to go. For files that do need registry entries, the easiest route is to copy the files with custom.inf and insert the registry entries with msbatch.inf (for some reason, I have never been able to get MSbatch to both create registry entries and copy files; don't know why, but it would do one or the other but not both). Msbatch can also automatically invoke exes to run after setup ends, which lets you integrate IE and DX9 and the like. The "Unattended Boot CD for windows 98" project uses that method, although I don't know if they use custom.inf or not.

The reason I wrote w98_slip was not because no other options existed, but basically just an attempt to make the setup directory be more orderly and neat, and also because, having seen the hfslip project for win2k/xp, I wanted to see if it could be done.

[wrayal]

Hey everyone,
I'm playing with this slipstreamer a bit at the moment - congratulations glaurung - it's incredibly useful! I wanted to make an all-in boot disc for 98 - 98SE2ME, 98MP10, kernelEx, USP etc. But, if you don't slipstream them natively, then tend to take up a rather large amount of space, which is a pain as I'm trying to shoehorn it onto an already crammed multiboot dvd! So I was wondering if anyone had looked at any of this?

At first, I'm looking at 98SE2ME as it seems the majority of the files for that are simply replacements - so I take it they could be put in the updates folder, and then run the slipstreamer and install as normal?

Anyone else interested in something similar?

Wrayal

[glaurung]

wrayal, on Dec 14 2007, 06:39 PM, said:

Hey everyone,
I'm playing with this slipstreamer a bit at the moment - congratulations glaurung - it's incredibly useful! I wanted to make an all-in boot disc for 98 - 98SE2ME, 98MP10, kernelEx, USP etc. But, if you don't slipstream them natively, then tend to take up a rather large amount of space, which is a pain as I'm trying to shoehorn it onto an already crammed multiboot dvd! So I was wondering if anyone had looked at any of this?

At first, I'm looking at 98SE2ME as it seems the majority of the files for that are simply replacements - so I take it they could be put in the updates folder, and then run the slipstreamer and install as normal?

Anyone else interested in something similar?

Wrayal

Thanks, I'm glad you're finding it useful.

The 98se2ME thing: look carefully at the installation scripts for that; IIRC, it uses a batch file and some inf or reg files, so figuring out what's going on shouldn't be too hard.

Files that are simply copied over will probably work if you dump them in the updates folder. Files that need to be self-registered, and files that need separate registry entires, might pose a problem. You'll have to check to see if 98se self-registers the same files that ME self-registers, and then you'll need to make sure you add in any missing registry entires. 98lite's method of adding extra registry entires ought to work for you -- add a new entry in setuppp to invoke a new .inf file, and use the new file to do all the extra stuff that needs doing (leaving it in the install directory alongside msbatch.inf). Judicious editing of the 98se2ME installation scripts should make creating that file fairly easy.

[niknak]

Microsoft in their er "wisdom" did list the files that were in the CAB files on the Windows 98 SE CD, which might help those considering a large file replacement.

The relevant Knowledge base documents are:-
238664 Windows 98 Second Edition CD-ROM Directory List 1
238666 Windows 98 Second Edition CD-ROM Directory List 2
238668 Windows 98 Second Edition CD-ROM Directory List 3
238728 Windows 98 Second Edition CD-ROM Directory List 4
238729 Windows 98 Second Edition CD-ROM Directory List 5
238730 Windows 98 Second Edition CD-ROM Directory List 6
238749 Windows 98 Second Edition CD-ROM Directory List 7
238767 Windows 98 Second Edition CD-ROM Directory List 8
238771 Windows 98 Second Edition CD-ROM Directory List 9
238775 Windows 98 Second Edition CD-ROM Directory List 10
238809 Windows 98 Second Edition CD-ROM Directory List 11
238811 Windows 98 Second Edition CD-ROM Directory List 12
238813 Windows 98 Second Edition CD-ROM Directory List 13
239011 Windows 98 Second Edition CD-ROM Directory List 14

If there is a typo - one document did lead to another.
Hope this is of use to someone.

This post has been edited by niknak: 07 February 2008 - 02:23 PM