submix8c

Still may want to see about "recreating" that CD... ...and get from the "now running" the Install Key

What make/model laptop? Desktops usually have some way of clearing the CMOS (BIOS) and/or resetting the password (a jumper, remove the CMOS battery, etc.). Doubtful installing from floppies made from a CD if the largest CAB file is greater than 1676kb (exactly 1,716,224bytes). Could maybe use an EBD and use a Laplink cable + software (serial/parallel ports) via Floppies (connecting to a running desktop with install files on it) in DOS mode. Other alternative is external drive, still ther probelm is getting into the BIOS. There are some "supposed" "reset BIOS password" programs on the net...

Hope it goes well (MS quote) - Let us know, ok? (seems like it should work...)edit - if above is true (Vista having IE7?) may have to do IE7 first. Anyone else?

This one? "WinINSTALL/LE"? Lite Edition ("freeware license"). I don't see any other "free" useable versions. The other three are specifically Evaluation. Hmmm, 25.9mb, WinInstall_LE.... Did you get the documentation? (your user-id, etc. for the logon?). What does it say?

Including the WinInstall package? Message seems to indicate an Evaluation version. Many vendors only allow Evaluations just to get a feel for how they work and don't allow actual usage until licensed. HTH

Hmmm... post link given above seems to indicate potentially additional operations to "get things working" as well, in any case (don't have 64-bit myself).

FYI... http://www.msfn.org/board/index.php?showtopic=43605 Maximum-Decim Native USB Drivers.

Offhand as far as "permantly owned", no. However, you always have the alternative, albeit temporary, to get a Nero Trial (30 days?) that works with 64-bit and use ImageDrive. ...and FWIW, the source for VCD is available (somewhere) for any soul that wants to attempt to modify it to work with 64-bit. edit - maybe WinImage as well (?). http://www.winimage.com/misc/filedisk64.htm

Not quite, apparently... It's under a "new name" and not generally available. read here

REGEDT32, not REGEDIT32. It should be there... (?AFAICR) Permissions in the Registry. I think this is the procedure (roughly) - Right-click "section" on left, change permission to allow you (ADMIN sign-on only, otherwise won't work), delete key/value, then change permissions back to original. Can't remember exact details... also you may have to be in Safe Mode and maybe have to have Restore disabled temporarily. May (?) be the way to use CCleaner (Safe/NoRestore/Admin)... ? Are you signed on as Admin when you use CCleaner? Also, this is an ActiveX reference you see? FWIW, I have a reference to Flash9b.ocx (now using flash9h) but CCleaner doesn't seem to "see" it (???).

Yes, same module (just checked). This may not "cure" your problem, tho, as I (vaguely) remember moving a HDD from one PC to another and got that error. I also recollect some MS article about it. HTH edit1 - google for "ntldr missing windows-2000" yields several articles - a fix http://support.microsoft.com/kb/320397 How To Troubleshoot - http://support.microsoft.com/kb/318728 edit2 - if your server cd is "mostly" readable, it may be possible to create a new one for components corrupted from the pro cd. try using an evaluation version of isobuster to extract the files/folders (or just copy copy copy). then let me know which ones failed reading and i'll let you know whether they're identical or not. (i think that's legal/not violating rules...) big giant edit! @fdv Yeah, already did the check. any other info/links you could help OP with?

Erg... guess I need to get a USB stick for testing. I did say "rough" and "appears". Just attempting to guide the OP to the correct resources (via "seek-and-destroy" - that widdle box at the top) for further digestion. (sheesh!)

Never done it but maybe this way... Since this is a "stand-alone" program, you may want to make a "package" using both files, a MAKELINK command (search for it for an example and google on it; think it's on sourceforge), and a CMD file to be run (by the self-extracting 7-Zip?) during "installation". Haven't used BGInfo lately, but you may want to try running it first (non-destructive...). I think it makes the info in BGI file and it's may/may-not be "static" info. Just don't remember. It may just be what is initially set up in it and dynaimacally gets the info to display. The settings you want will be what you finally decide (when you play with it). Ennyhoo, that's a kind of a gist-of-it I'd suggest. Look around here; the remainder of info is there. HTH

Look the config.js script over. I think (AFAIK) it allows for several commands in-a-row to execute for a given selection. In addition, I believe each selection will be run-in-a-row. In other words, you can't "simultaneously" run several selections (WPI is sequential in nature?). And I agree, if you can Extract the Install, it would speed the process up. HTH

Sorry, but from what I understand (haven't used it), but it appears to be two different worlds. You can't just "change this to that". Rough (real rough) explanation - Procedure appears to be to Begin Installation (somewhere - a VM/VPC?), halt/do not reboot after a certain point (after Copying Installation Files?), Properly format the USB stick (methods given in the forum; a special "tweak" is necessary to make it properly boot), copy the halted installation over, modify whatever is necessary (this and last - order probably reversable), then carry the USB Stick to the PC and boot from it (will finish the installation). You have to do a little reading to understand this, as you probably had to do to set up an Unattended CD. P.S. the SIF file has (almost) nothing to do with it. Again, sorry, and HTH

C'mon! Rationale behind Kel's post (with explanation), is because if any other "bad" person got hold of the source, they might modify it (as was explained) and distribute it under the pretense that the original author wrote it, and BAM! Instant virii/trojans and who would be blamed? Bear in mind, that we have no "controlled" environment (except for our own self-control) like SourceForge has (read the GNU/GPL stuff). Someone writes, we test (on separate machine or VM), report back, suggest changes, and volunteer to directly participate (with author's consent and direct co-operative off-line sharing and not willy-nilly). Many of these projects are written in languages that others are not familiar with and may very well be complex. Again, in many cases (these included) it would be downright dangerous to "open source" it. No GNU/GPL provided, period! It is now (for these projects) simply a waiting game, so we wait...

My "differences" check (for Win98SE and applies to WinME as well) - Absent in Upgrade: OEMSETUP.BIN FORMAT.COM OEMSETUP.EXE It appears that you have an Upgrade Version. The Scandisk.pif can be recreated. If you need the info on each portion of it, I can give it to you. If a Supervisor or Moderator will permit it, I'll just upload it (no proprietary info there; right/wrong?). So... it looks like you may need a previous version. additional personal notes (may help determining exactly what you have) .\win9x\format.com (Not on UPGRADE; NOTE: format.com is in .\win9x\base2.cab\ebd.cab) .\win9x\oemsetup.bin (Not on UPGRADE) .\win9x\oemsetup.exe (Not on UPGRADE) .\win9x\precopy1.cab (see below - contents differences) setupc.inf (!!!! ADDITIONAL DIFFS !!!!) [Data] CCP=0 (in OEM) setuppp.inf (different/same time) [data] ProductType=2 (Upgrade/Step-Up) Line 422 UPI=79469-XXX-XXXXXXX (Upgrade/Step-Up) Line 423 setupx.dll (different/same time) Hex Offset 000A7B4B - 33 (Upgrade) Hex Offset 000A7B55 - 32 (Upgrade) -or- Hex Offset 000A7B46 - (x'05')52783(x'09')C83-00002 (Upgrade) Hex Offset 000A7B69 - 30 (Upgrade) Hex Offset 000A7B6A - 32 (Upgrade) -or- Hex Offset 000A7B68 - 102 (Upgrade) suwin.exe (different/same time) Hex Offset 0006B4F8 - 30 (Upgrade) Hex Offset 0006B4F9 - 32 (Upgrade) -or- Hex Offset 0006B4F7 - 102 (Upgrade) .\win9x\w9xsetup.bin (different/same time) Hex Offset 000223C2 - 30 (Upgrade) Hex Offset 000223C3 - 32 (Upgrade) -or- Hex Offset 000223C1 - 102 (Upgrade) ***** there are other differences between OEM and others... ** Note: ** x'30'=0 / x'31'=1 / (etc.)The above notes are not exactly complete but (mostly) accurate for your purposes. I have these because I sometimes repair other folks' PC's and need them for renstalls, etc. Yes, you can put it on the D-drive and install from there. Remember that EBD! Normally, the EBD.CAB is not expanded for an Install Floppy (slightly different). I can give you the contents (file list) of one and the actual modifications you may need to the CONFIG.SYS/AUTOEXEC.BAT (if you actually need it). Mostly, all you need is 1 - bootable floppy (MSDOS.SYS, IO.SYS, COMMAND.COM) 2 - since not from cd, SMARTDRV is unnecessary 3 - access to FORMAT.COM (put on D-drive folder; it's in the EBD.CAB also) 4 - boot, format C, ChangeDir to the D-drive-folder, run SETUP and Away You Go! - - note: be absolutely sure you're C-drive is the original C-drive!!! (FDISK Display and check for Active and the original size, then Exit) extra note - AFAICR, the majority of the CD-bootable (Retail) has nearly identical files as the Win98SE Bootable, and the Floppy Boot is nearly identical between them (no FINDCD hence AUTOEXEC and CONFIG is slightly different). HTH edit - Moderators/Supervisors - please check the WWW; most (if not all) of this info is already out there. I just compiled this for purposes of verification of what the "customer" actually had, so hopefully this won't be construed as a violation. If so, feel free (as you will) to edit/remove it.

11:38 A.M (EST U.S) link works. roughly 38mb. perhaps ftp site down or something else blocking it? Using FlashGet, 1 connection, roughly 5 minutes (ISP is Cable), so mileage will vary. The same file is indicated for Windows ME. This may be the one you already have, so may be no joy. Dates are 01-28-2000 (relevant ones). Check what you have...edit - downloaded the Win2K version (11mb/2min.; major size diff. appears to be a "samples" file). Read the INSTALL.TXT and there's an implication (on my part) based upon some filenames that will be required that this MIGHT work on WinME (appear to be present in ME and not 9x?). Remember that (no flames please; a "loose" statement) ME is a sort of "cross-breed" of 9x and 2k (a kind of "crossover OS" to help folks "over the hump" to XP Home - urg!).

Doubt if you'll have any "changes" made on nLite or vLite very soon. See this post by Nuhi - "On Pause - human.dll"

Hmmm, Resource Hacker? I take that back... no no no! pay for it and/or ask for it to be enlarged... (giganticus brain-farticus)

Would this help? (appears that the 8810 can use 8400b?) - http://www.chemusa.com/8400b_05.htm You didn't specify the version# of the driver... Worth a shot...

"On pause - human.dll" - well, yes! and working too (better'n a lot of us are doing)! I think an operative phrase would be "wait until I have time and inclination, so don't pester me". Happy for ya, Nuhi!

Ok... don't understand how you could have created and installed with nLite but... Brother's son removed the "sndrec32.exe" program from the PC (to remove it from his tray) and it displayed the same symptoms as yours. You must have created the nLited version from some original source CD (since you says it's nLited). You have apparently removed too much. I would suggest you reinstall from the original source CD and try the nLite process again. Without accurate info (re Components Removed), I can see no way of anyone assisting you. and here's the nLite website - http://www.nliteos.com/

Urg! Just realized; maybe related, maybe not (after re-reading first post)... Some MoBo's have a bad habit of assigning the same resources (e.g. IRQ, Memory) to several devices. If by some strange chance your Video is conflicting/sharing with the NIC's then you may be getting a Clobbered situation (timing?). Current MoBo doesn't do this (except for USB and Video), but I think my other one does (NIC and Video). Check for something like that in Accessories->System Information under Hardware Resources->Conflicts/Sharing.

As I understand it, it should be in the ROOT of the CD, if you correctly created the nLite image.