submix8c

@LoneCrusader - OK, but again... it should be "doable" using the UBCD98SE method. It installed from Boot and included the necessary patches using a "special" Boot Image and the contents of the CD during Text Mode (which is not affected as you are in the process of installing). Agreed that the AMD Patch actually fixed other CPU's. Too bad the UBCD thread was totally eliminated. There was a wealth of information there applicable to nearly any Win9x-series. Perhaps (?) it could be reloaded from archive and all links/attachments removed... (probably not and not worth the effort)... If no Moderator has any objections, I'll extract the BAT's (all home-grown) and the contents list-only of the Boot Image so you'll see what I mean... (Never was a UBCD for Win95, but the concept is the same...) @dawong - thx for the explanation edit - errr DUN... will try a "basic" UBCD-95 in spare time just to test... Theoretically, the actual components could be extracted, placed in the WIN95 and alter the LAYOUT.INF accordingly (if other methods fail).

You might want to check that Key and "certain files" (another thread on MSFN re. installing OEM Pre-activated) and compare them to the CD. You might also want to get the Key from the running PC before-hand as the Key on the PC Case will cause Activation request (and probably won't work on any other PC). I successfully re-installed a friend's using that method. There's also a thread on using a Dell CD. Using it (the CD) in a "generic" way may or may not be good on another PC (using any legitimate key). edit - just following Ponch's line of reasoning (correct, I might add).

? I am soooo confused... VPC2K7 doesn't mount floppies without VB(what version)? Maybe I installed all of the VBx's on my XP/2K3's... I installed Win95RTM (no IE at all!!!) from... FLOPPY IMAGES!!! Then mounted the VPC2K4SP1 ISO add-ons and installed, then used Shared Folders, installed the DUN then IE. My CPU is a Sempron on the Host and I limited the RAM in VPC. No problems whatsoever. AFAIKR the MS AMD Patch was specifically for the 350mhz (although heard reports of others). Not slamming the project as it sounds great and should "cure" any problems with installation on "real" PC's. May try installing Win95RTM/OSRx.y onto a "real" partition just to give it a go (yeah, I have all of them in some form or another). Just wondering about the statements in the posts above (downloaded the DOC and see nothing about VB-scripts mentioned)... BTW, installing the DUN (and other items) should be able to "integrate" into actual install using the MSBATCH.INF (remember your other thread?) the same way as UBCD98SE did. If need be, I'll scrounge up the "basics" of the how-to to assist. Not much on projects nowadays except to fix my own up and relative's ignorance. I could at least supply the "raw files" (if not too large for a ZIP) used (the actual process files, not the remainder/proprietary EXE, etc.) to let you late-comers peruse (lots of BAT files too).

Move the Hard Drive from another PC? Only way to "fix" that is to Reinstall "Over the top" via Booting to the Install CD. HAL info - Standard PC (irrelevant - works on any, I think) Advanced Configuration and Power Interface (ACPI) PC - halacpi.dll (renamed to hal.dll) - ntkrnlpa.exe - ntoskrnl.exe ACPI Uniprocessor PC - halaacpi.dll (renamed to hal.dll) - ntkrnlpa.exe - ntoskrnl.exe ACPI Multiprocessor PC - halmacpi.dll (renamed to hal.dll) - ntkrpamp.exe (renamed to ntkrnlpa.exe) - ntkrnlmp.exe (renamed to ntoskrnl.exe) uniprocessor Ntoskrnl.exe ntkrnlpa.exe multiprocessor Ntkrnlmp.exe ntkrpamp.exe Please provide the Date(s) on the CD in question and I'll tell you what SP-level it's at (should all be the same, otherwise provide the highest date found in the I386 folder). (p.s. if it's already been nLited, you won't be nLiteing it again as this causes major errors).

First, "soporific" is a long-standing member here (although disappeared for a while). The downloads you used may be one of - a - UBCD for Win 98SE (thread has been removed from MSFN due to a licensing restriction in the "package") b - AutoPatcher for Win98SE (thread is still here and links still exist "somewhere" to get it) Package "a" uses components from package "b" to "silently install/reinstall and upgrade" 98SE to the latest available patches and to install all needed drivers. I'm running on it now (please don't ask where to get it). The problem with the licensing may have been to proprietary (e.g. you didn't pay for the right to use it) items in the (maybe) drivers, (maybe) several utilities, and (possibly) several modules used during HDD setup. Package "b" does not include drivers but does include all of the latest available patches. The patches are all listed (and links given) in the "stickies" in this forum (Latest Hotfixes). Also includes an older version of WPI (an MSFN Member Project) that installs a ton (exaggeration) of freeware/shareware software. I have the latest of this also. Neither would cause the problems you suggest. If you look through the threads, you'll find limitations to highest version of any given MS Updates/Fixes/Patches that can be used on Win98SE (or any of the 9x families). Bottom line is that using either package, you will be at the highest level of "fixes" available to 98SE and to install any "updates" beyond that will hose you really bad. Notice that you could install the "fixes" manually simply by downloading them (ref. the "Latest Hotfixes" thread) and running them. Both of the above simply automate the process for you. As for the "noise", take the side off of the tower and when it starts, carefully listen to see which component is making it and replace it. a - Power Supply (dirt - dry-air blow it and maybe a touch of WD40 on the fan-culprit) b - CPU Fan (same as Power Supply) c - Case Fan (same...) d - HDD (back it up and replace it) If "noise" persists in any of the above, replace the component (fans may be replaced in any of above as long as the same type). Otherwise, you might have installed something that is thrashing the heck out of your HDD (possibly a trojan). Try a "clean" install (after backing up your valuable data elsewhere) and run an Online Virus scan (many are available on the internet) but be wary and use only an online site that is trusted and don't click on their website until you know they're safe. If you get no "noise" and/or no functional errors after a period of time, then it's something you "did wrong" (whatever...). Also be aware that in the AutoPatcher some FreeWare no longer functions (support dropped, e.g. AVG7). - edits - And the files for install (ref. the CAB files) are usually in the folder "C:\WINDOWS\OPTIONS\CABS" and if UBCD was used (probably not) then in "C:\WINDOWS\SETUP" unless an unorthodox install was used. You might also try CCLEANER and SpyBot (if you can get them downloaded and run them) to perhaps ensure that you don't have any any Trojans etc. If you leave Temporary Internet Files/Cookies uncleaned and/or the Temp folders uncleaned (undeleted) "bad stuff" tends to continue. Also try using FireFox 2.0.0.20 (last version working for Win98SE) to maybe help with pop-ups (and find/get NoScript add-on installed while in FireFox). Note - also using FireFox on this 98SE as we speak. To get into "Safe Mode", just press the "Shift" key (automatic) and the F8 key is for getting a Selection List (Safe Mode is one of them). I believe "WINHTTP.DLL" is for NT-type operating systems as this 98SE has MSXML4SP2 (KB925672) installed (the correct version from the UBCD/AP/MSFN-Hotfix-list) and there's none on mine. I'd say your trying to upgrade (something) to a version not supported on 98SE. Tip - If you go into "Programs-Accessories-System Tools-System Information" and look under "Software Environment-Software Updates" you'll see every (?) single Hotfix installed. As for uninstalling the MSXML4, you can if you want to (it's an MSI package) but probably not the problem. BTW, if you can "find" your Install Files (ref. above) then there's a thread on MSFN on how to create a second partition, install a "basic" 98SE on it, and use it to access the internet in lieu of the "hosed" one. - end edits - HTH

I noticed the "links" visibility "problem" too. I resorted to "bold" to make it recognizable.

There's a Boot Order in the VM's "bios". Reboot ("start") selected VM, press "Del" key, change it (just like a "real PC"). Now, load the "ISO image", select "Save BIOS Settings" and continue. In any case, you must press "Del" and "Capture" the ISO or Floppy before continuing to boot otherwise... (at least using VPC2K7 installed on XP/2K3)

Nope... says so right here.

My bad... 1 - Boot to Primary. 2 - Edit BOOT.INI in secondary to copy the line - multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows (whatever)" 3 - Edit BOOT.INI in Primary; paste it below the line that "looks the same" 4 - Change the pasted line value "rdisk(0)" to "rdisk(1)" (the HDD "pointer") 5 - Save it and reboot. Noticed the OP had "swapped drives" and both worked. Lucky, IMO, that it worked (basic MoBo must have been the same) in the first place. Unfortunately, the OP had already chosen to "repair install" (must have edited the BOOT.INI wrong). So sorry jaclaz/tech4niq for my own personal shortcomings/haste (been a rough millennium)... Oops... forgot to mention the net result above is the same as my previous post...

You should make that partition active, edit boot.ini file and set properly booting device, and then try boot Windows.Uhhh, no... Info in each individual registry precludes that.You could set one primary, one slave (both set active). -BIOS both AUTO + Boot HDD1 : primary will boot (as C) and see secondary (as D). -BIOS both AUTO + Boot HDD2 : secondary will boot (as C) and see primary (as D). Only other option is to copy the Primary's BOOT.INI entry and modify to point to Secondary and reinstall "over-the-top" to secondary (no data loss). There's also a topic here that may help immensely as another alternative.

You can try create a new profile and transfer all data from old profile to a new one.s-1-5-18: NT AUTHORITY\SYSTEM (???) s-1-5-19: NT AUTHORITY\LOCAL SERVICE (folder LocalService\NTUSER.DAT?) s-1-5-20: NT AUTHORITY\NETWORK SERVICE (folder NetworkService\NTUSER.DAT?) So... suggestion probably won't fix missing items. Try to get the stuff from the "backup" and start over. Don't know if contents of Windows\Repair would help or not...

?Have you tried gParted Live?

If you want to "install in order" (by "hotfix creation date") it's laborious, but doable. I install Flashget (download manager), get the "fixlist" (from wherever), go to MS Downloads for each individually, select download, cancel the download, when the next screen appears righ-click on the "if it didn't download, click here" and select "download using Flashget". The original date is then retained (as opposed to using Browser download) that can be sorted by ascending date and added accordingly. If the "fixlist" has a direct link to the MS file, just right-click on those instead (same difference but faster than the aforementioned MS-method) into Flashget. HTH (works for me)

FWIW (and FYI), in nLite the HotFixes (etc.) will show but are not uninstallable (only an entry is placed there), whereas in HFSlip they won't show at all. Try it and see...

You can't. Everything was "slipstreamed" (just like a Service Pack). Only other option is to run the Installers post-OS-install or separately during install so they will be "seen and uninstallable". I believe this may be an "option" in both nLite and HFSlip (not sure); check the documentation on How-To.

PENetwork is a tool used with WinPE (or LiveXP) that will automatically configure your Network Card(s) based upon a created Script ("driver") for PE-bootable CD's, thus installing/starting Services necessary for Networking (TCP/IP, Shares, etc.). Don't know about using it in PE 3.0, though (it should work). Be aware that you should have the drivers installed before running it (and associated "services"/"services software"), otherwise your card(s) will not be "found" and/or there will be no Network support. This "tool" is generally used with LiveXP (a Bootland project built using Windows XP CD), a variation of WinPE.

You didn't specify what models.Can you access the Local Network (internal PC's, i.e. your Workstation) with the Libretto? If not, better check with the Network Administrator. Since this is a Company LAN and the Workstation has a "fixed IP" (does it?) then there's a good possibility the Company has a fixed set of "Allow" IP addresses, of which the Libretto is being "blocked" (not in "the list").

Curious - anyone try Opera on Win9x and access MSFN (re: "speed")?

Have you tried looking in the nLite section? This is also where your other (and this) topic should be (not in the Unattended section) as both topics refer to using nLite. I will assume that the folders refer to the SATA and PATA respectively. Within those should be some INF (suffixed) files. These are the ones. Here is a fine example of what I stated. Please read the first post (pretty clear).

I already have the IEAK4 software, just not the customisation code.Also, the link with the download points to a page on Microsoft's web site that no longer exists I think I said that (see quotes). IE4.01 SP2 (AFAIK) was the last version of IE4 in existence. IE4DOM could raise it to 128-bit (starts as 40-bit). Get that, overlay the appropriate files in the DOWNLOAD folder (may/may not work) and customize it. You do not need to "synchronize" (no longer available, dude) the files.I just did a new install of Win95 4.00.950 (original RTM, no IE), installed IE4.01 SP2, then IEAK4, and it works just fine as I said in last paragraph. For that matter, why do you even need IE4? It's useless since IE5.5 SP2 works on Win95, Win98, Win98SE, WINME, WINNT4. (...And what do you mean by "customization code"???)

Google search IEAK4 - 125mb CD (zipped) is available (first one listed) - just unzip and make an ISO/Burn. Don't know if the IE4 component sites on MS are still available though...

@Tarun - Using "newer" Windows, FF, and the "Script Blocker" mentioned. All is well for me here. Just need to remember to use FF from now on (and get used to it, I guess). Still have ye-olde IE6sp1 + all MS-OS/Browser Updates. However, the fact of the matter is many (?) folks won't have PC's that will aloow for any more that an older OS/Browser. Leave it at that (flame-wars?) and just say "Sorry, you will just have to bite the bullet until/unless solutions can be found". Remember, some are Normal/Supreme Sponsors...

JFYI (in case you didn't know)... In Win9x, there's an Explorer Folder Option "Allow Uppercase Filenames" that, if not set, displays/creates "Abc", as opposed to "ABC". In addition, in Windows, if only ISO is used on a CD, only ISO names will be displayed (uppercase, hopefully), and if Joliet is used, then the Joliet names will be displayed (ignoring the ISO "directory" on CD). For the purpose of Bootable Image, you need the ISO "directory", as DOS can't access Joliet "directories". This is true (AFAIK) for all bootable CD's (at least Windows). ...And I'm under the impression (?) RockRidge is not very useful for Windows.

???"added the sp3"???1 - make a folder 2 - copy [files] to it 3 - copy I386 folder to it 4 - run nLite 5 - in nLite, point to the folder 6 - in nLite, point to the SP3.EXE (to Integrate) 7 - DONE!!! Surely, you aren't copying the SP3.EXE Service Pack File to the "folder"... NO NO NO!!! You will be unnecessarily adding roughly 300mb to the CD! nLite INTEGRATES it into the I386 (replaces the older files with the newer SP3)!!! (There's your extra megabytes IF you are...) Go here and do a little reading...

That's the "original" RTM (5.1.2600.0). It didn't have the .Net folder and [files] is undoubtedly the other Root files. Yes/no/maybe? Shouldn't copy over anything but what you need (same size). Try making a folder (anywhere) and copy only the I386 folder (the whole folder) and the [files] to it then try again. "Folder" should be less than 400mb. These are all that are necessary.