submix8c

Malware/Trojan! It may have been "blocked out/deleted" by an AntiVirus software and this is a "leftover" registry entry. Suggest scanning with a/the AntiVirus again (check any logs IF you have Antivirus), MalwareBytes, and maybe SpyBot. Hopefully, this will "fix" it. If any/all "bad stuff" has been finally removed, then the entry may need manually deleted from the registry. edit - Hmmm... MalwareBytes post on it. Another reference (RootKit?)

Google term (copy/paste0 - share printer "logon script" Locally, just share the printer for "basic" sharing (intranet). The remainder depends on what you want to do.

Get really confused (mine agrees with above re - XP SP3) Ver 6.0 for XP SP2 (w/link at bottom to 6.1) Ver 6.0 2k3/XP x64 (w/link to 2k3sp2 6.0) Hope this un-helps...

Or make a LiveXP from (if you have it) an XP Install CD, boot to it, and run RegEdit. Also allows for Explorer. Bootland WinBuilder (used to build the CD) LiveXP file list (used by WinBuilder) (sites are currently down?)

Security (AntiVirus, Trojan, etc) is a different subject than Backup. You will need several "packages" (e.g. Firewall) to do the job as no "single package" is capable of this. Note that some vendors supply multiple functions in a single package but they do not completely cover everything. Suggest re-reading the stickies and try for yourself. Some are free, some are pay-for. Pick your own based upon your personal needs as everyone has different preferences (as do I, so I won't recommend, nor will others probably). It also depends on the hardware/OS as well, so....

Look here (nLite).

Which WinPE version? Have you looked at LiveXP for a sample? Explorer has several dependency modules when included will allow Explorer to function (no, don't remember which - it was trial-and-error; use Process Explorer to find out easily).

Uhhh - you are here. Did you read the stickies?

If you have full access (irrelevant as to method), just load the file SYSTEM into REGEDIT and try what I said above. (in ControlSet001/ControlSet002). Fair warning, this can't be done against a "running system" (SYSTEM hive is usually "locked"). HTH

Suffix of all Outlook/Outlook Express email is DBX (eg Inbox.dbx). Documents and Settings / <username> / Local Settings / Application Data / Identities / <odd-number folders - may be several> Address Book suffix is WAB. Documents and Settings / <username> / Local Settings / Application Data / Microsoft / Address Book

First, do us all a favor and stop quoting every single post as it's unnecessary. Second, please use the "edit post" function as to not clutter up the topic with additional unnecessary posts. Third (here ya go...) - This may or may not help you (as I don't know if HIVE's are thesame in Vista/Win7, but suspect they are). This Linux bootable CD tool purports to allow editing a Registry HIVE from the LiveCD-Boot. The theory I propose is to download it, burn it, boot the "black screen" PC with it, load the SYSTEM HIVE on the HDD, find the offending Hardware, change a value, unload the HIVE, then reboot to the HDD. I cannot vouch for this as I haven't tried it - use at your own risk! The example I present is based upon a NIC that I have "disabled" (attached zippe'd Registry TXT file so it's readable). Notice the "ConfigFlags" field's value (a d-word "1"). All other "enabled" devices have a d-word of "0". So... one might be able to load the HIVE, change the value, unload the HIVE, and voila! Device Enabled! HTH edit - an article indicating using a Knoppix Live as well - Here ___________________JUNK.zip

Any "serial cable" (i.e. "COM Port Cable") will do. Just "tear it open" to get the connectors off/out... (note - you might want to get one that isn't encased in "plastic")

Video appears to suggest using USB connection with Nokia CA-42 USB cable (a cell phone adapter) Amazon-dot-com $1.99 USD RS-232 is just a Serial Port connector. The pins inside are what's used to make the "splice" connection. Do read the topics given...

From here... (google) Appears that it still wouldn't fix your Colors anyway without modifying the checksum. Appears that no source code available. Wups! Alternative here (Kel's link)

Ummm, really confused here - Per the MS Article - "APPLIES TO Microsoft Windows 95 Microsoft Windows 98 Standard Edition" Looked high and low on my 98SE (clean install) and it does not exist. The following PIF's do, however, exist - DOSPRMPT Exit to DOS <--- this is the booger here (replaces DOSSTART?) MS-DOS Mode for Games with EMS and XMS Support MS-DOS Mode for Games Do another search on "*.BAT" on a Clean Install... what do you find? We are talking 98 Second Edition, aren't we??? Just right-click on te PIF's and click "Properties"... Soooo, what am I missing? Searching on "string" "DOSSTART" on a C-drive with 98SE install yields several references, among them WIN.COM. I'm thinking that this file is more of a "carryover" from Win95 (specifically Upgrades - see SETUP.TXT, also noted in WinME)... Anyone??? Besides, isn't it faster to just use a PIF with embedded directives? I can click on those MS-DOS games (ProgramTab w/Close On Exit -plus- Advanced w/Suggest MS-DOS Mode as necessary), play them, then when I exit the program, Windows... Restarts! Same methodology applies... I will, however, concede that since WIN.COM has some kind of reference that it probably internally "calls" it when selecting "Shutdown/Restart MS-DOS Mode" if it exists, but why get complex? Description of MS-DOS Mode edit - see dencorso confirmation post below... whew! pick yer pizen/method is the game... ("I am not krazy, I am not krazy" <- yeah rite!!!)

PageDefrag (includes link to ContigDefrag) Sysinternals/MS. HTH edit - may not as you want it to happen during Install... edit2 re jaclaz above... very true! Pagefile is just that - a PAGE file (Mainframe, anyone?)!

In addition, perhaps this will help "starting MS-DOS Mode" (see attached zipped jpeg). You'll note that starting the "MS-DOS Prompt" (DOSPRMPT.PIF) in the Start Menu/Programs is "built" the same way (a PIF!). If you were to copy it under a new name and alter it, i.e. in Advanced force to MS-DOS Mode then add BAT and SYS lines (they get "embedded"), that it will indeed completely bypass "normal" boot (please note the DEFAULTS under Advanced; look familiar?). I would recommend (again) testing DVD access with an EBD, using whatever you deem acceptable/functional, then just make a new PIF. (Note the good info in all preceding posts.) Guess that makes a "dynaload" unnecessary... PIF_Example.zip

Ever heard of DOSSTART.BAT? http://support.microsoft.com/kb/135174/en-us jaclaz Uhhhh, where did I fail to post what needs to be done??? Another alternative is to create a PIF for a specific program with specific BAT/SYS files/parameters (works the same way as DOSSTART). I built an older PC that had both Windows and DOS-mode games (for a g-son) that does just that. When the MS-DOS game completes, (with an EXIT at the end of BAT), it "automagically" restarts Windows...C'mon, guys, nothing special here, except for using the superior SHSUCDX. Please note that there's (minor) "patching" needed to be done for SMARTDRV+mem-mgrs. This process was extensively researched during the UBCD98SE (just mentioning it, ok?) project and it worked well. If allowed, I'll post the Autoexec.BAT and Config.SYS variations used, which will also list the other components necessary... edit - I don't remember the module name offhand (perhaps jaclaz can find it) that will dynamically load a Config.sys-style driver during Autoexec.bat phase (useable in the DOSSTART maybe)... Also, AFAICR, it does no harm to the Windows to put the driver (oakcdrom) in the standard Config.sys and the MSCDROM(whatever) in DOSSTART. Glad to re-test all of this for you if you like, fred (got a dozen moldy-oldie pc's sitting right here! dis-as-sem-bled)...

AFAICR, it's irrelevant whether CD or DVD as the internal "pointers" are what truly matters. Test it out with a Boot Floppy (ie EBD) and if it works with that (pop a DVD in), just modify accordingly. Bear in mind that if you have multiple CD/DVD drives, you'll have to have multiple lines in the BAT/SYS... I stand corrected (jaclaz below, and yes the utility shown works...)

Right here... You need the drivers loaded...

Xp installed after 9x (mine works the same way as herbalist')...Glad ya got it going, herbalist! Kinda similar to my "info" post (following jaclaz'). Those links were just what you needed! Kinda thought it might be possible easily (after my grub4dos "complicated"). Slick idea using "debug" and a script to extract the boot sector, I must say (never even dawned on me...). Now I can go ahead and "fix" mine!!! Thx, jaclaz (duh! on me...)! Sadly, for you though, many items in ADD/REMOVE in the XP may not be available, since you don't have the I386, but hey, what's there is there. Just don't use the Add/Remove Windows Components part... (err, is this info in cannie's topic? should be if not...)

Have you tried - -clone,mode=create,src=n,dst=x:\backup.gho src is the source disk#, dst is the path/name of the cloned disk image This is what Ghostcast is automatically inserting, so... And as I remember, restoring to a different size HDD worked (not sure if it handles smaller). This assumes you're not backing up a "running system" and not backing a disk onto itself (naturally). My understanding is that only Ghost System Suite can back up a "running system". Look into the docs on the "clone+mode" switches to see if this works better. (?Checked and I believe your version is GSSv2.0?) Kind of confused as to the errors (don't use the other software mentioned)... HTH

The update inside the ZIP/EXE also has a set of silent switches. When you set up the "Command/Program To Execute" while creating the EXE those switches need to be in that line.

Specifically, "Verify Against Image File"? edit - haven't tried this and not sure exactly how/how-much it compares, i.e. the data in each block (e.g. CRC flags). edit2 - confirmed! scenario - 1 - write CD1 from ISO1 using Nero 2 - write CD2 from ISO1 using Nero 3 - create ISO2 from CD2 using DVDInfo 4 - Verify CD1 against ISO2 using ImgBurn (fairly fast) It appears to work just fine (strictly sector-by-sector compare).

Page 17 of the PDF file indicate that you can't run this from AUTOEXEC.BAT when using Win98/ME. Page 16 "implies" that it can be run from COMFIG.SYS, but it only specifies when booting to Pure DOS. So if you want both Win98 and a reboot to DOS for access, it appears that you will have to use two types - the Paragon version for Win98 and the Avira version for "raw DOS". When I get a chance, I'll try it (unless you can beat me to it). It'll require an understanding of the boot process, mind you (only one can be running at a time)... (You did RTFM, right? I still don't understand the point of pre-loading...) edit - BTW, you misunderstand what these things are... they are not drivers...