K e n

Not just Google, I have all my machines set to Google Suggest

I did this some time ago for a custom CD I made myself.. I did it by 1st installing the tools from the 98se CD.. Tools\Reskit\Setup.exe When deploying the tools there was a program that generated inf files called infinst... This is the readme.txt from infinst... 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.

I'm currently on a fresh install of XP for the same reason.. every 2 minutes a popup add would appear without me even browsing the web. One of the adds actually had me in stitches though, it was an MS mouse that had the top half open up like the back of the cover was on hinges with 2 eyes staring at me from within the darkness inside the mouse, then a caption displayed with the words " Do you feel your computer is spying on you" Appropriate I thought, being that just seconds earlier I thought to myself - " ****, I think I'm infected with spyware" Lucky enough , formatting & re-installing once a month is a ritual for me as I tend to test way too many tweaks & programs on offer around the scene.

As Jlo555 mentioned.

I remember reading that a tweak was applied to the system.ini, just could'nt remeber what it was.. This system was always OK at 1st with the later USP's, that is until a bunch of apps were eventually installed over a 1 month period, then the greif started, Yet whenever I set a win98se system up using the 1.5 usp then go to windows update I never have a problem. 1.62 was the worst for me, it would bsob within the 1st week guaranteed, & had no eyecandy appearance tweaks like 1.5.. I'll reboot into the 98 system & post the system.ini for the original poster later..

I just downloaded that file you posted , I like to see how others tweaks work.. I tried to run it & had the firewall pop up telling me that an HTML application host from your computer wants to connect to www3.telus.net [161.184.2465.22] port 80 I clicked deny.. Then norton had a fit when running it...

I currently have 98se running on a system with 768mb no probs, It crashed multiple times during the rebooting after installing drivers though. I ended up reinstalling it with just 512mb of ram , installing the unofficial service pack 1.5,, {{1.5 because it was the most stable & had the most eye candy relevant to tweaking the appearance}} Then after installing the service pack put the extra 256mb in & ran sweet, has never seen one bsod or crashed now for over a year, although I have to say the extra ram made no difference to the speed or running of apps in any way though,, & the only reason I upgraded was the system dual boots with 2000 Pro,, which runs many apps at once during the day. I could post the system.ini file if that helps you at all,, that is , I'm thinking thats where the tweaks were applied for the extra ram... & please dont get into a post bashing about service pack 1.5 as all the later builds ALWAYS bsod'd at least once a month on this system, 1.5 has NEVER bsod'd for me...

After typing "Bush is smart" in google & pressing the search button I found THIS...

Hey I like some of them tweaks guys, don't mind if I knock a few off I hope.... I don't use the $oem method of adding registry entries however, I edit the appropriate hive---.inf file , usually hivesft.inf... I think cluberti originally showed me that way as an alternative a while ago.. cluberti, I notice in yours you state to make sure when saving the txt file to make sure the word wrap is off, man I learnt that the hard way.. I'd been adding the registry entries for the last 20 or so mods this way but suddenly started to get errors about the setup being unable to install the catalogues with an error that went something like 8001b0001.. Just out of curiosity I turned word wrap off after killing a dozen or so attempts & was back to working fine when saved after editing the hivesft.inf. I was starting to lose faith in my ability to do anything there for a while until that was found..

I recently used nlite to reduce the size of the 1st disk so as to fit the entire 2nd disk on the 1st as I also have a tablet pc key.. I never edited the winnt.sif as you explained, I edited the txtsetup.sif & found it worked perfect, I never added the key to the unattended setup of course as I like the option to use either key to make it either MCE or Tablet.. The txtsetup.sif originally looked like this below... I removed most of the languages I would never use,internet games plus the tour & found it reduced from 773mb to 680mb... [SourceDisksNames.x86] 1 = %cd2name%,%cd2tagfilei%,,\i386 2 = "%cd2name%","%cd2tagfilei%",,\cmpnents\tabletpc\i386 3 = "%cd2name%","%cd2tagfilei%",,\cmpnents\mediactr\i386 4 = "%cd2name%","%cd2tagfilei%",,\cmpnents\netfx\i386 I just removed the number 2 from the above to look like this below & had no problems installing either Tablet or MCE.. Just another way though, your way no doubt still works... [SourceDisksNames.x86] 1 = %cdname%,%cdtagfilei%,,\i386 2 = "%cdname%","%cdtagfilei%",,\cmpnents\tabletpc\i386 3 = "%cdname%","%cdtagfilei%",,\cmpnents\mediactr\i386 4 = "%cdname%","%cdtagfilei%",,\cmpnents\netfx\i386

You will need to partition it 1st before any Windows OS will see it in my computer, when you have partitioned it just boot back into Windows & format it from there... I have a Partition Magic boot-disk if you can't find one to do the job. I'd post a link to it here if need... lmk... Asv far as setting it up in the bios goes, you may need to, but most bios's these days are set to auto detect, it would'nt hurt to boot into the bios just to confirm it did find it though, unless you can see it on the post screen...

winnt.sif isn't the only file meant to be on the floppy, it should also have a winnt.bat. If you use the setupmanager that comes with the support tools on your XP cd it creates both the winnt.sif plus the winnt.bat.... I have a link stored in the million or so favorites from ms that backs that up.. can't find it ATM, however I found the webpage that I saved offline, i'll copy & paste what it says below, hope that helps you... Also, you can download the latest support tools from MS for the service pack of XP that your'e using , be it either Sp1 or Sp2.. Part B: Create a Winnt.sif Answer File 1. After Windows is installed on the master computer, build an answer file for unattended installation of Windows by using the Setup Manager Wizard (Setupmgr.exe). The Preinstallation Tools are located in the Support\Tools\Deploy.cab file on the OEM Windows product media that comes in every OEM three-pack from your local Microsoft OEM Authorized Distributor. To install the Setup Manager utility, follow these steps: a. Open My Computer, and then open the Support\Tools folder on the Windows XP CD-ROM. b. Double-click the DEPLOY.CAB file to open it. c. On the Edit menu, click Select All. d. On the Edit menu, click Copy To Folder. e. Click Make New Folder. Type the name that you want for the Setup Manager folder, and then press ENTER. For example, type setup manager, and then press ENTER. f. Click Copy. 2. Open the folder that contains the Setup Manager files, double-click Setupmgr.exe to start the Setup Manager Wizard, and then create a new answer file. For additional information about how to create an answer file, click the article number below to view the article in the Microsoft Knowledge Base: 308662 (http://support.microsoft.com/kb/308662/EN-US/) Use Setup Manager to Create an Answer File 3. Follow the onscreen instructions from the wizard to create the answer file: a. On the Product to Install page, click Windows Unattended Installation. b. On the Distribution Folder page, click No, this answer file will be used to install from a CD. 4. When you reach the Windows Setup Manager dialog box that prompts you for a location in which to store the newly created file, insert a floppy disk into drive A:, type a:\winnt.sif, and then click OK. You receive the following message: The Setup Manager Wizard completed successfully. The following file(s) were created: A:\WINNT.SIF A:\WINNT.BAT 5. Click Exit on the File menu to quit the Setup Manager Wizard, and then label the floppy disk that you created as "Windows Unattended Disk." If you want Windows Setup to delete all partitions on the hard disk, and to create a new partition, you must include the Repartition command in the Winnt.sif file. To do this, follow these steps: a. Start Windows Notepad, and then open the Winnt.sif file that you created. b. Under [Unattended], insert a new line, and then type the following code:Repartition=Yes c. Save the changes to the file, and then quit Notepad. Back to the top This is the contents of the Winnt.bat that resides on one of my floppies created by the setupmanager...As you'll notice E:\ drive is where i'll be installing XP from... @rem SetupMgrTag @echo off rem rem This is a SAMPLE batch script generated by Setup Manager. rem If this script is moved from the location where it was generated, it may have to be modified. rem set AnswerFile=.\winnt.sif set SetupFiles=E:\i386 E:\i386\winnt32 /s:%SetupFiles% /unattend:%AnswerFile% /copysource:lang I used the setupmgr as MS intended & this picture below is as MS said it would be..

Iv'e had the same problem for about a month now, it was due to expire on january next year but seeing it has had a problem for the last month I uninstalled it, a full legit purchase too, the only time it ever found anything though was when the definitions were updated, which got me a little suspicious as I also have AdAware pro installed , which hardly ever found anything, which made more sense to me - for a system that was used about 10 times a month just to visit forums & do netbanking..all up about 10 hours on the net, yet the stuff spysweeper found was a little hard for me to accept as true....who knows..

Interestingly enough, I was just browsing a computer in a local retailer (I believe it was an HP model) that was running on Media Center. I noticed in the C:\ directory a folder called CMPNTS (or something like that). Within that folder were three others: one was labelled MediaCenter; the second was TabletPC, and ... well, I don't remember the third... I actually own a genuine set of holographic OEM MCE2005 CD's bought off ebay, came with a peice of dead ram. The 3 folders your'e talking about are = mediactr, netfx, tabletpc, all 3 of those folders have an i386 folder in them. What I would like to know is what file on the 1st CD determines whether or not the setup becomes Tablet instead of Media Center, if possible that is. The reason I ask is I own a genuine VLK MSDN set of XP missing the disk 1 of Tablet PC but own disk 2, to my knowlwedge disk 1 is just XP pro similar to MCE setup disks.

You can add the second cd to the first cd by editing the txtsetup.sif file editing the entries that say %cd2name% change to %cdname% then copy the files and folders to the root directory of the windows cd and it will not ask for the second cd anymore.

I find both Yahoo & Google to be pretty good, But, Google Suggest Beta is what I have all my systems home page set to via a registry mod... It rulze

One detail in this picture gives it away, can you spot it. EDIT: Sorry people. It seems the moderators of this board consider that anything they don't believe to exist to be warez. Thats twice now I've posted that desktop & twice I've been warned. It had the classic start menu showing home, had the "windows has already been activated" dialog, & showed the system properties with the corp pid. Man , this place is run by the gestapo.

For the record, for those of you who like to prove a point... XP home corp DOES EXIST as I own a copy..

That was an interesting read, it seems that MS are setting their standards as to what they consider a threat & ignoring the standards led by other leading antispyware makers.

We cant talk about such because most in power here will suggest were engaging in pirating software when the mention of NO ACTIVATION is mentioned.

Has anyone noticed he's trying to slipstream sp2 into a folder that has sp1 already integrated into, don't shoot me but i'm pretty sure thats a no no.. It has to be a non service pack installation to slipstream sp2 into..

Wow, I can't believe I finally found someone else with the same problem as me.. My system is also an athlon XP2400+ with 764mb pc2100 ram & ati 9200se graphics... I have installed Vista twice now with the same outcome as you although it took 4 hours both times for me... I have run into this problem before when I installed 98se when I only had a single 40gig hard-drive on the primary IDE channel. I would install the OS & all would be fine until I installed the motherboard drivers, then it would do the same as this vista install, the ide light would flash every second & the mouse would only move the same time the ide light would flash. So I formatted & started again, all would be good until the motherboard drivers would be installed.... Then I installed XP pro thinking 98se was too old for the system & it did exactly the same thing although on 1st boot, didn't even get the chance to load drivers. After 3 days of persevering I found that if I piggy backed another drive set up as slave on the primary ide channel it fixed it... So now I removed the slave & altered the jumper settings on the master & started re-installing the OS's again, but still ended up slow no matter what configuration of jumper settings were made on the master.. I tried Cable select, master without slave, master with a slave & even jumpered across the master/slave as some western digital drives used to be jumpered but still no good.. As soon as I added a slave to the same channel all would work perfect, yet for some reason on vista it makes no difference.... Now i'm thinking it's a MoBo problem { Epox 8KMM+} As a last resort I have a 120gig drive i'll be using as the master & will piggy back another brand of drive to the slave on the primary channel. As these 2 40gig seagate drives have died totally, won't even detect on bootup, any wonder, the amount of times I formatted & re-installed...

Thankyou prathapml Those links are about what I was looking for. I did a search when 1st joining but after 20 or so links figured I was using the wrong search terms & thought it would be easier to ask. EDIT: The project was a success, thanks again prathapml The cabpack from MS was a bit vague on the instructions though. I found more info relating to the cabpack outside of MS than I did searching within MS themselves..

I'm Hex-Editing various files on a couple of old Beta OS's then need to repack the files back to cabs. The files i'm hex-editing wont be any different in size as i'm over writing with the hex editor - not adding to the files..

Hello folks.. I'm here to ask for someone's help with regards to extracting files from cab files then repacking the files back to cab format back to the original size the cab was prior to extracting it, plus I'm of the understanding that the cab has a checksum which needs to be restored.. I downloaded the Cabinet Software Development Kit from MS but was hoping to shortcut learning the hard way by asking the advice of a professional or someone learned in the area.. Thanks. Ken. P.S. I can extract the cabs OK with winrar , just need advice on the repack with the checksum intact.