Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

glaurung

Member
  • Posts

    35
  • Joined

  • Last visited

  • Donations

    $0.00 

Everything posted by glaurung

  1. The office integrator forums (http://cpu.reboot.pro/ ) appear to have been abandoned to Russian spammers. Just a few months ago, the links to various hotpacks of office updates maintained by TwoJ were live, but now they are all dead, as are the links to the "office updates downloader". Since I stupidly managed to delete the hotpacks for Office 2003 during a spring cleaning of my hard disk, It would be very helpful if I could download them again.
  2. Yes, the problem appears to have finally been solved by doing the SP3 slipstream under XP instead of 2k. However, I very much appreciate your reply because now I know how to fix it manually -- thanks!
  3. It's a customized winnt.sif - nlite doesn't have the ability to set some allowed and documented settings in winnt.sif, so I put it together myself by hand. I was just drag/dropping it into the 1386 folder before hitting the "make ISO" button. I'll try running Nlite under VPC later today or tomorrow, once I get a working XP installation (which may take a while).
  4. ETA2: The problem was not with my winnt.sif - Evidently Nlite is not able to handle integrating XP SP3 under Win2k, and the only indication of a problem is that the updated source will throw these file missing errors after install completes. I created a slipstream inside a VPC running XP and it worked correctly. Edited to add: Have now tried a virgin copy of XP SP2 with no updates and no alterations except for the winnt.sif file - still got the error. This makes no !@# sense. I've rolled back to virtualpc 2004 and am trying it again. If that doesn't fix this problem, my next recourse is to try it without an unattended file and see what happens then. @#$%^&*! Arrgh! I've been getting the framedyn/srclient not found error. I've been paring back the things I've added/changed from the base install in an effort to figure out what is causing it, to no avail. Latest attempt: I told nlite to integrate SP3 into a clean copy of XP Pro SP2, then dropped my winnt.sif into i386 and told nlite to make an ISO. I did NOT use any of the other options - no tweaks, no reducing, no switchless installers, nothing. Installing from ISO under virtualPC 2007 on a computer running windows 2000, I got the dreaded Framedyn/srclient error. Google tells me that this error was cropping up a lot a few years ago, but mostly for people using RyanVM or doing other complicated stuff. I haven't done any of that - the only thing I can think of that's causing it is either a) trying to do the slipstream for XP on a computer running windows 2000, or B) using virtualpc 2007 instead of an older version (up until now VPC2007 has run fine for me, but you have to hack the installer to get it to run under win2k). Was the source of this !@#$% annoying issue ever found? Is there a fix? Attaching my session.ini file and my winnt.sif Last Session.ini winnt.sif
  5. Some of the hfcleanup file names are a bit cryptic, and Google has not always come through for me. 1. What does "osoptions_spmessages.rem" remove? 2. How about "driver_portableaudio.rdv" - is that sound drivers for laptops, or something else entirely? Also, I'm thinking of hacking the english-only files. I do want to be able to see Russian/Hebrew/Chinese/etc fonts correctly, but I don't want or need keyboard support or anything else for languages other than the default. Besides keeping the .tt_ files for the languages I want to be able to see, are there any other files normally removed by the english-only reducers that I need to keep to ensure that codepages will display correctly in Firefox?
  6. glaurung

    FDV fileset for XP

    Seconded. Lack of Fisher-Price icons is nice, but far more annoying, for me, are all the various training wheels that are turned on by default and which I have to switch off every time I reinstall.
  7. Originally (win 95), double clicking on the system clock brought up the UI for changing the system time. When you changed the system time on it, you were resetting the system clock. When MS realized that lots of people were using it as a calendar to look up dates, they said "oops" and issued a fix (in win 98) that made it so that the time was not reset unless you clicked apply. I know this because Raymond Chen wrote an article about this a couple of years ago; searching his Old New Thing blog will probably turn it up. It looks like you have just discovered that their "fix" was a hack that reverted to the original time when exiting the dialog, and what is actually happening when you page through the calendar is that the system time is still being changed every time you change the month on the calendar. So, if you're going to browse through the calendar while writing an email, what you need to prevent this problem is an actual stand-alone calendar app.
  8. Outlook and netmeeting and VPN work just fine after using 98lite to strip out IE, because all they require is IE's HTML rendering engine, which 98lite leaves intact. I'm pretty sure 98lite supports removal of IE6 via the add/remove windows components control panel, so if necessary you can install it, install your other software, and then uninstall it. If I'm wrong, the standalone IEradicator (http://www.litepc.com/ieradicator.html) definitely supports removal of IE6.
  9. If the goal is to have a small win9x install to use for emergency recovery and legacy software, and a main 2k/xp install to use for everything else, you don't have to muck around with installs on the D: drive despite what Microsoft says. The reason MS says you can't install two OS's to the same drive is primarily because of incompatible file versions in Program Files, especially in Program Files\Common files. So the easy, simple way I found to put both 9x and 2k or XP on drive C:, without any troubles, is this: 1. format drive C using FAT32. 2. Install 9x. Specify Win9x as the install directory. 3. Make an unattend.txt or winnt.sif file to automate 2k/XP install, and include the following in it: [unattended] ProgramFilesDir="c:\Program" CommonProgramFilesDir="c:\Program\Common" TargetPath=winNT Now all the 9x common files are segregated from the NT common files, and you have achieved once again what MS claims is impossible: two fully funtional OS's installed on the same partition. Granted I'm not switching back and forth between the os's on a daily basis, but it has worked fine for me so far. The downsides I am aware of are 1) if you want software to run under both OS's, it will have to be installed twice (manually specifying the location the second time), and 2) you won't be able to run certain low-level disk software (like defrag) from win9x without killing the 2k/xp installation.
  10. Download the free version of 98lite from http://www.litepc.com/get98lite.html. It will make IE an optional component on either an existing installation or on a new install, for any of 98fe, 98se, or ME. You don't need any windows 95 files to use 98lite, despite the impression you might get from the directions - that part only applies if you want the "sleek" desktop. despite the name, the "chubby" desktop (no extra files needed) works perfectly well and is quite fast.
  11. Sorry to take so long getting back on this - my spouse has been sick. Yes, your answer was helpful helped. I remembered to look in the other zip files and found the ZZZZ_OSOptionsMDAC.REM remover in the "this will break MS office" zip file. So, let me see if I have this right: ZZZZ_OSOptionsMDAC.REM will totally rip out everything MDAC, thus breaking add/remove and MSoffice. OSOptions_MDAC_WITH_IE6.rem will take out what can be dispensed with without breaking things. If that's correct, then, another question: do you know if OSOptions_MDAC_WITH_IE6.rem will work safely if I have not slipstreamed IE6? And finally, what things can I expect to break if I use ZZ_Service_WMI_WBEM.rem? Thanks again for taking the time to answer.
  12. I've been going through the hfcleanup reducers provided on the hfslip.org website. Most of them have pretty descriptive filenames, or else I can figure out what they do by either googling the name or by looking up the annotated list of components in Nlite. One exception is "OSOptions_MDAC_WITH_IE6.rem" - I assume that if I have IE6, then this will take out MDAC. But, what if I'm using Win2k and have not slipstreamed IE6 - in that case, is this unsafe to use, or can it still be used to remove MDAC when you only have IE5? Another question - ZZ_Service_WMI_WBEM.rem. Does this remove everything WBEM, or does it leave behind the files that are needed for things like the add/remove control panel?
  13. There is a way to make it do this, but it's very poorly documented. "custom.inf", like msbatch.inf, is a "special" filename - if it exists in the setup directory, setup will automatically load it and copy the files it names to the locations it specifies. custom.inf is designed for OEMs to preinstall drivers for hardware in the systems they make. It's been a while since I had to do stuff with it, but IIRC, it has two operative sections - the first, [Custom_Precopy], copies files to the temporary setup directory during the precopy phase; this guarantees that the driver infs will be seen during the initial hardware detection phase of setup. The second is a standard [baseWinOptions] section that can be used to copy files to the inf directory during the regular file copy phase (so the infs will be seen after the first reboot). here's a skeleton custom.inf (nicked from intel's installer for my motherboard's chipset), with my annotations [Version] signature="$CHICAGO$" [DestinationDirs] ; 2 is the temporary setup directory where the contents of precopy*.cab get expanded to before the actual filecopy phase starts. 17 is the normal inf folder. PreCopyFiles=2 ; Windows temp setup directory PreCatCopyFiles=2 ; Windows temp setup directory InfCopyFiles=17 ; Windows \inf directory CatCopyFiles=10,CATROOT ; Windows \CATROOT directory ;this section is automatically loaded and the copyfiles sections named in it are executed during the precopy phase. ; normally it's used to copy driver infs to the temporary setup directory ; since the registry doesn't exist during the precopy phase of setup, I doubt you can do much of anything else with it [Custom_Precopy] CopyFiles=PreCopyFiles CopyFiles=PreCatCopyFiles [PreCopyFiles] foo.inf bar.inf ;I don't know if you have to segregate cats from Infs like this unless you work for Intel ;I usually just delete the cat files and comment out references to them. [PreCatCopyFiles] foo.cat bar.cat ; I have played with this section a little - you can use it to copy any files anywhere, not just infs. ; I haven't tried putting an "addreg" section here, since msbatch.inf works just fine for doing addreg stuff. [BaseWinOptions] InfCopy [InfCopy] CopyFiles=InfCopyFiles CopyFiles=CatCopyFiles [InfCopyFiles] foo.inf bar.inf [CatCopyFiles] foo.cat bar.cat ;I once tried compressing the driver infs into a cab. I ran into problems, ;but I think it was because I had made a mistake somewhere. [SourceDisksNames] 1="Intel Chipset", "", 0 [SourceDisksFiles] foo.inf=1 bar.inf=1 foo.cat=1 bar.cat=1
  14. 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.
  15. 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.
  16. 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.
  17. 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.
  18. 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.
  19. (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.
  20. Does anyone know if there is a registry hack for 2k/xp that will prevent Windows from remembering what I did last time I used the shutdown dialog and "helpfully" suggesting that as the default action the next time I ask it to shut down? In other words, I want the default action on shutting down to _always_ be "shutdown," for example, even if last time I used the dialog I asked it to "restart." I can understand why this "feature" was implemented starting in Windows 98; one of the developers never shut off his computer but instead always put it in suspend mode, and they wanted to not have to select that every single time. But it's implemented incredibly stupidly, because what I did last time isn't a good indicator of what I usually want to do.
  21. I don't think you can. The first phase of the windows setup wizard (where you choose the windows directory and all the files are copied) is a windows 3.1 program, which means it cannot understand or use long file names. So windows will always be installed to a short name directory.
  22. Say I have two folders, \A and \B. Folder B has files also appearing in A, but also has some files that do not appear in A. I can generate a list of files in B that are also in A, using: cd B for %%F in (*.*) do dir ..\A\%%F /b >> ..\duplicates.txt I also want to generate a list of the files in B that are not in A. It seems to me that this should work, but all it does is put a single file name in unique.txt: cd B for %%F in (*.*) do if not exist ..\A\%%F echo %%F >> ..\unique.txt I've also tried replacing the "echo %%F" with "dir %%F /B" Same result. First, what am I doing wrong, and second, is there a simple way to do what I want? Am I not allowed to do a for-if combination, or is there some quirk about redirects that I don't know about?
  23. So far I haven't gotten feedback from others who have tried it, but I did my best to design it to be error free, and I was able to use it to integrate the updated files from the unofficial service pack and do a maximum install with no errors whatsoever.
  24. I have created a slipstreaming tool called w98_slip which will update and totally repackage the setup cabs without any spanning. You can find it in the unofficial service pack forum here.
  25. Googling cabman2003 gets me a number of pages in Chinese and Russian, which I can't read: can you point me to the home page of the software? I could build the ability to slipstream the win95 explorer into w98_slip, but It's not high on my priority list because I no longer use the 95 shell myself. I used 98lite's "sleek" shell for years, but recently I've finally moved on to the "chubby" shell because now that I have a DVD burner, I'm occasionally dealing with multiple gigabytes of files, and the 95 explorer can't handle large directories well; between 2 and 3 gigabytes, it starts reporting the size of the selected folder or files incorrectly. Seeing the pie chart in the disk properties isn't important to me; seeing the actual size of the files I've selected is. If you're just replacing a file with another version of the same file, the only .inf files you need to worry about modifying, in my experience, are the layout* files. If you're adding a file, things get a more tricky: I think the only places you need to insert the new name are layout*, copy*, and the inf file whose filecopy section you want to add the new file into, but I could be wrong. Agreed the 1760kb size is not important. Actually, come to think of it, w98_slip's use of .new cabinet instead of .set maxdisksize eliminates file spanning completely, which would then make it easier to undertake the kinds of experiments you're doing.

×
×
  • Create New...