submix8c

? Disable it entirely in your BIOS, boot to SAFE mode, go the the Control Panel and remove all instances of it from the Device Manager. It better not be found again!

Not sure if this will work (FLV players). Now look at the bottom of that screen for - Here's for a SWF player and here for the VLC Media Player (you say you already have that).

At first I thought, why copy the win98 directory to the HDD to run it from there, why not simply run 'setup.exe' from the win98 directory on the CDROM? But I figure there'll be some reboots that would cause the 'setup.exe' in the root directory of the CDROM to be invoked, right?Also, if you format the HDD, don't forget the "/s" option to put the system files there. Finally, I presume using the UBCD in this way would be analogous to simply using a standard W98SE CDROM, albeit a bit less convenient. Joe. Ok, let me clear this up...UBCD 1 - Performs "MD C:\WINDOWS" then "MD C:\WINDOWS\SETUP" 2 - Copies CD's WIN98 folder to above 3 - Copies "COPYOVER" folder to above (for Phase One Basic Install/Basic Updates, named in MSBATCH.INF) 4 - Run each compressed Driver Module (which extracts to specific folders named in the MSBATCH.INF) 5 - Runs Setup 6 - After Phase One, reboots into subsequent Phases (accessing the CD) 7 - Last Phase runs WPI (accessing the CD, which incidentally Autoruns as well) Test it out... Install using UBCD, then interrupt the first DOS screen after "Running 98 First Time" reboot and take a look-see at the contents of the HDD; see all of those files just waiting to be installed? Inspect your UBCD disk, particularly the UNATTEND.BAT, PRESAVE.BAT, POSTSAVE.BAT and the DESKTOPn.BAT files; These are the bad boys that do the grunt work (and the initial specifications are in the MSBATCH.INF - look inside it) OEM/Standard 1 - Performs "MD C:\WINDOWS" then "MD C:\WINDOWS\OPTIONS" then "MD C:\WINDOWS\OPTIONS\CABS" 2 - Copies CD's WIN98 folder to above * - note - Additional INF's/Drivers may be placed in that folder as well 3 - Setup is run * - note - may be done via a Special OEM Boot Disk (DRVCOPY.INF is used to get the CD Driver over to HDD; never played with it much) It's worth noting that I have "altered" the UBCD to allow for running directly from the HDD. It requires understanding all of the batch (BAT) file constructs. Also, just make a W98SE EBD, copy XCOPY over to it, do the OEM/Standard method as follows - 1 - MD C:\WIN98 2 - XCOPY x:\WIN98\*.* C:\WIN98 <--x is your CD 3 - CD C:\WIN98 4 - C: 5 - SETUP Voila! Installing from HDD, and no reboots to access the CD. This info is all over the internet. It works for 2K/XP/2K3 as well (provided you FDISK/FORMAT as FAT32). This is the method I had proposed. You don't need the "/s" option as it only copies system files to the C-drive. Simply FDISK/FORMAT will create the MBR/PBR. All you need is to make the partition ACTIVE. The act of switching to the C-drive takes care of it. Yes, UBCD and Standard CD are analogous. The difference is, that UBCD does some OEM-style install and then some. Running from CD does not copy the WIN98 folder over; UBCD and OEM-style does (no more need for CD in ADD/REMOVE). HTH your understanding... edit - and for reference (re. KernelEX and RP ). Also try looking (again) at this thread. You may not be changing the correct parameters for memory allocation in SYSTEM.INI. And (noting you have a 140-GiB HDD) look here.

Oooo-Tay!!!! Googling on "HDX INF" tells me these are for x64 machines. These are not suitable for Win9x. The "HDA.INF" are for 2K and up and also not suitable.Do these really have "Chicago" as a signature? If so, they might work. Doubt it... Probably will have to use the AC97 drivers (WDM_A406.zip). BTW, "Chicago" is valid for 2K/XP. And the INF's may be interpreted different between 9x and 2K/XP. I seem to remember that some NTx.x INF's would not work on 2K/XP (and vise-versa).

Hmmm... D000 used to be generally used for an add-in NIC (ISA, specifically ) or other add-in card.

Example from VIAMACH.INF - [VIA_SYS] %PCI\VEN_1106&DEV_0305.DeviceDesc% = VIANO_DRV, PCI\VEN_1106&DEV_0305PnP info (I believe...) Can you give an example? Rename "problem example" xxx.INF to xxx.TXT then ZIP/RAR/7z it (whatever) and attach it so we can have a look-see. (err, no need to rename if it's compressed to xxx.ZiP, whatever...) Some INF's are not really for installing PnP drivers; worse some drivers are NOT PnP and have to be "force installed". What driver are you attempting to integrate?I had to "force" a non-PnP driver for several older NIC's (ISA) that weren't PnP via the MSBATCH.INF ad the associated INF in that "copied-over folder of drivers" (ref. my example). Here are some examples (commented) from MSBATCH.INF - [Network] ComputerName="COMP-NAME" Workgroup="WORKGROUP" ; Description left blank Description="" Display=0 PrimaryLogon=Windows Clients=VREDIR Protocols=MSTCP Services=VSERVER Security=SHARE ; added from here... ; DO NOT USE for the SMC Ultra; this is a PnP-ISA ; DO NOT USE if No NIC INSTALLED ; IgnoreDetectedNetCards=1 ; netcards=*pnp80d6 ; LinkSys (hard-set these since non-PnP in a PnP environment; still gets picked up) ; These cards have "jumpers" ; irq=10/io=340 ; [*pnp80d6] ; InterruptNumber=10 ; IOBaseAddress=340 ; ...to here...Note they are "commented" (kept there for archival purposes). Each card has it's own way of being defined via the associated INF file, hence the difference. INFINST was not meant for non-PnP installations, another reason it to do an "OEM-type" install (see previous posts). It takes "generator software" out of the equation.

OK, so you have TWO separate issues. Each should be tackled one at at time. (reference this)

Have you tried installing to your 40gb HDD with just the original CD (e.g. the win98 folder). Try booting to the UBCD, Select DOS, format the HDD, MD (Make Directory) on that drive a WIN98 folder, XCOPY the contents of the CD's Win98 folder (including subdirectories) to it, switch to the C:\WIN98 folder (where you xopie'd to), and run SETUP.EXE. This gets you a non-UBCD'd install (i.e. as if you used the CD). Based upon your specs, you SHOULD be able to use it. You may lack correct drivers and will not have the Upadtes (etc) as in the UBCD, but at least it proves you WIN98 Source (the CD) is good. Is XP on the first partition? Normally, XP is installed after 98SE. UBCD would have done that for you (referencing your first post linking to GT1Gib topic) As I said, you don't want to install those until you are sure your normal install is stable.BTW, you are aware that UBCD is in English Only (as is AutoPatcher). If you use any other language package, they will be fake. If you try to use any other language of 98SE neither UBCD or AutoPatcher will work. Curiosity, what type of keyboard/mouse are you using?

UBCD98SE vs AutoPatcher - UBCD installs the OS, Updates, and Drivers in one "shot" (multiple ?5? reboots to accomplish Updates). Any "software" was in the MS-DOS "boot" selections (not installed). Some "software" was not "freeware". Did not include the aforementioned items. You couldn't "pick and choose" anything to install or not install - they all installed. AutoPatcher installs Updates and Software (via a "special" WPI) only and after OS Install. The "software" is "freeware". Did include the aforementioned items. In addition, some items (if selected) would "re-install/rename" previously installed items if selected in subsequent runs which would goober the system. and not allow uninstall of said items. Partial "select/don't select" is available. I would surmise that the "redistributable licenses" were inspected in UBCD and found wanting (not to mention the OS Product Key embedded). edit: Scratch that - UBCD indeed has the "additional WPI items" (last reboot or "autorun", which I believe is where you are in trouble). Hang in there... when I get time, I'll look at the RP and KernelEX that you indicate and see if they can be "backed out". FWIW, you COULD re-install "over-the-top" from the UBCD and see if that "fixes" you (basically overlaying the problem modules). You take your chances on doing that, tho. And (can't remember) you might have to reinstall any other software you had installed.

??? Unattended Boot CD for Windows 98 Second Edition (UBCD 98SE). Topic Removed... (see my previous post)BTW, the method works for any Win9x/ME... (except for certain MSBATCH.INF parameters)

Network Logon, not Windows Logon (for 9x). Windows Logon does not allow access to NT-type systems. In addition the User has to be defined on the NT system and there must be an associated password. The reverse is not necessarily true as there is no facility in Win9x for particular users or groups (activated via the Sharing/Security in a running NT system). Access this direction is "wide open" (see the Win9x Folder Sharing tab and compare to an NT Folder Sharing tab). Simple File Sharing only for Win9x. Also note USER.PWL in the Windows folder (9x) compared to NTUSER.DAT (NT). Not sure where a "password" would be stored for Win9x (never tried it that way). XP Home/Pro and up (and Vista/Seven) non-Server allow "fast user switching" for "more than one user". Servers only allow for a single logged on user (like Win9x). Not far off course on this info (but probably not entirely accurate).

The INF's and associated Files are installed during Unattended Install. That's what the INFINST program is supposed to setup for you. The MSBATCH.INF is the "driver" for other INF's (under an Install section somewhere?). If you simply (I believe) place the INF's (better look inside them; the actual Folder for the Diver Modules may point to "elsewhere") and Modules can be placed in the folder where you are installing from (e.g. WIN98). Look in the sample MSBATCH INF provided with the "kit" for more info on how to automagically install them (OEM-style). Mind you, they have to exist in the Exact-Path specified. Easier to just ensure that the INF contents point directly to "current-folder" (where-modules-are) along with the INF's and place them in the WIN9x folder (e.g. on CD). Give that a shot (remember, look in the individual INF's; may require modification). Part of my MSBATCH INF as example: [Install] AddReg=OEMDrivers,OPKInstall,RunOnce.BatchDelay,Run.Installed.Components,Skip.PCMCIA.Wizard,Registry.WinUpdate,PreSaveSettings,PostSaveSettings [OEMDrivers] ; Add additional driver paths for OEM specific drivers ; Ensure each entry is separated by a semi-colon ; HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion","OtherDevicePath",,"C:\DRIVERS\VIDEO;C:\DRIVERS\AUDIO;C:\DRIVERS\MOUSE;C:\DRIVERS\1394;C:\DRIVERS\MODEM;C:\DRIVERS\IDE;C:\DRIVERS\LCD;C:\DRIVERS\MONITOR;C:\DRIVERS\NETWORK;C:\DRIVERS\SCSI;C:\DRIVERS\STICK;C:\DRIVERS\SONYPI;C:\DRIVERS\UFDD;C:\DRIVERS\UMOUSE" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion","OtherDevicePath",,"C:\Windows\setup\D\1;C:\Windows\setup\D\2;C:\Windows\setup\D\3;C:\Windows\setup\D\4;C:\Windows\setup\D\5;C:\Windows\setup\D\6;C:\Windows\setup\D\7;C:\Windows\setup\D\8"Portion of ViaGart INF as example: [SourceDisksNames] 222=%DiskDescription%,,0 [SourceDisksFiles] Viagart.SYS=222,D\4\viaHyper [Strings] DiskDescription = "AGP GART Miniport Driver Disk"Note that the actual module is in subfolder "viaHyper" (see the D\4 and relation to MSBATCH?). Never bothered with CUSTOM.INF and not sure how it comes into play. (Above is from UBCD...) Again, usual method is to copy the Install (after Boot To CD And Install) to Windows\Options\Cabs and use the above to "point" to the correct location. Edit: Sheesh, too bad UBCD info is gone; revisiting methodology a lot lately. Maybe if I have time (and a Mod approves) I could sort out just the "legal" stuff and upload example portions.

Haven't tried any of this additional functionality.Look Here for BlockPost Plugin info and Here for the Outpost Guide. I think this may be what you want. In particular Here (basic test of plugin appears to block the IP/HostName in an Untrusted Zone only, not the Port). Try that and see if it fulfills your need HTH edit: and FWIW look here. Appears to be a 6.5/6.51 Free version...

FWIW, "CabPack" utilizes MakeCab and also does not include Quantum as an option. Perhaps Quantum was available in Diamond but not used. Why do I say this? If you look in the Headers of the Cabs they seem to indicate MSZIP (AFAIKR; been a while since I "decoded" them). Or, perhaps it was available (and used) but the "flag" was set to MSZIP?Note to Self - seems to a subject of a different topic as it appears that a dual(or more)-pass was done to construct the "installation set" (since LAYOUTx.INF is in PRECOPYx.Cab). Never got the hang of reconstructing CAB's (the DDF's must be correctly constructed to replicate, using MakeCab). Thx for additional info (already have the rest tucked away - somewhere?).

??? Install it, look in the BAT files to see the sequence of installs and reboots. Everything is there! Just be aware you must understand BAT coding. In the case of GT-1GB RAM, this may be a separate issue that would need to be addressed (don't remember). Look in the Stickies and do a little reading, particularly that single GT 1GiB thread...BTW, AutoPatcher topic still exists (a long read) and no particular info was given for the "how it's done"; it assumes knowledge of BAT files (an entirely different subject).

UBCD for 98SE was a project involving "merging" AutoPatcher + Drivers + Other "software" (this being the reason for closed topic, some drivers/software was "not free" and/or "not redistributable" I believe; better left alone on that issue). It includes (as does AutoPatcher) an option to install those particular items. Browse around MSFN and you will see that there were "conflicts" between them and other official/unofficial patches. Certain "bugs" would arise (read the loooong AutoPatcher thread for some potential details, or even the Unoffical SP's, etc.).As for UBCD, it's possible to "reconstruct" the Project (afresh, I dare say), by simply taking info previously included to "roll your own", as it were. This info (if you still have UBCD) is within the TXT files (folder "instruct") on "what got included from AP98SE". Simple methods (via BAT) for including Drivers, Patches (official/unofficial), and Software (DOS-mode Executable during Boot From CD and Installed via a particular version of WPI as last sequence). The BAT files, Lists (TXT-files), How-To-Make-Boot-Image, and some basic instructions would be all you need. 'Nuff said (don't want to bring out the butt-spankers...)!

... or Virtual PC (free from MS).

I assume you mean UBCD v4.8... "Kernel EX" and "Revolution Pack" might cause problems when used before/after UBCD (no longer supported and topic removed - don't ask why...). Just read the info in the "package", look over the fixes included, and visit MDGx' site for "no-no's" when installing those additional packages. I don't use them (installed 98SE with just UBCD and a minor "tweak" for "Greater Than 1gib Memory" topic (see stickies). No problem here... edit - Seems you have this same problem noted here.

Well, don't thank me, thank soporific (ref. AutoPatcher 98SE). It is pretty basic and kind of mirrors a router (and then some). I kind of like it too (use it on my 98SE in dual-boot environment). Have to play with it, though... not for the "noobie" since you have to know how to set it up...

? Irrelevant (I think...). I have dual-boot with a Lite-On DL DVD (no LiteScribe) seems to work fine. But... maybe because I have 98SE with all the patches (official/unofficial) via AutoPatcher 98SE (see MDGx' post/website)?

I have no idea where to find it, the date seems "the same", but the size is much smaller. jaclaz TYVM (and redistributable, to boot! never saw that...). Odd about the size, tho... Missing "code"? Maybe just certain files within not present? LoneCrusader, got time to test it for the 'CompressionType=Quantum" (ref. specific posts jaclaz presented)? Got a little busy with payin' the bills, so not much time nowadays... Ummm, is there an INF to DDF utility somewhere (not sure, may have seen one somewhere)?"Out with the bad air, in with the tolerable.." - Happy New Year!

HUH! Found DIAMOND.EXE 1.00.0530 (03/29/95) which was used for Win95 CAB's (look inside LAYOUT.INF to see the version). Do a google on "mcabin10.zip" (with the quotes). HTH...

Ok... my .02cents.... Using a Gateway USB Keyboard with "extra USB plugs" (for plugging in e.g. a USB Mouse close to you) will install another set of USB hubs/ports. At least it is/was there on mine. As far as the Via Controllers, there are probably 2 on your MoBo. How many "ports" do you physically have? I have an internal Header for getting several more "plugs" by putting in an add-in connector. No magic, just hardware...

".Net Runtime Optimization Service" in Services. It's running and won't quit until it's finished "optimizing". Google it... The suggested "fix" is to disable it immediately after install and before reboot. V-2.x started installing this...

Agree with the "need"... whatever your "need" is. Router usually does the trick. But (FWIW) here is Agnitum Outpost Firewall Free...