submix8c

1. <snip>i created a bootable windows usb<snip> 2. Booted the Windows installation as you said, from the USB<snip> 3. <snip>i solved after downloading another x64 imagex from microsoft<snip> 5. Restarted the laptop but nothing happened. Booted again into my friend's "clean" windows installation.<snip> =========== Partition 1: 400MB "invisible" partition with 100% free space - Healthy (Active, Recovery Partition) as stated in Computer Management - Disk Management Partition 2 (C:\): 349.61GB visible partition Containing the OS - Healthy (Boot, Page File, Crash Dump, Primary Partition) as stated in Computer Management - Disk Management Partition 3 (D:\): 348.63GB visible partition containing just a HDDRecovery folder with subfolders containing the imagex and .swm files - Healthy (Active, Primary Partition) as stated in Computer Management - Disk Management =========== I'm not getting a couple of things. 1. By what method and using what "source"? 2. I'm guessing you mean your "source" is an Install ISO source and not a Repair CD/DVD? 3. Um, how did you do that? You got the AIK ISO? 5a. "nothing happened"? 5b. Your "friends" is from an Original Windows 7 Install DVD? Partition 1 - a UEFI/GPT HDD, right? (apparently...) Partitions 2/3 - how ODD the partition sizes. ~700GB HDD? You got that info from the "clean install"? Where's the "System" flag/indicator? *Side notes - I don't have a "Recovery Partition" flag/indicator but did apply "Reagentc /enable", FWIW. Also booted to a Console with the created x86 Repair CD and specifically used "DISKPART" for listing as well, that you haven't done. Indications are that you have a 64-bit OS, since you needed an x64 "imagex". That "magically appearing" folder/file is the Recovery Environment that - "C:\Windows\System32\Recover\ReAgent.xml" should have an entry for. The WIM is undoubtedly "adapted" for the OEM Restore. I'm not understanding why the BCD Store in the 400mb "hidden" partition is failing to "see" the ("System") OS. Something seems amiss (a/l to me). Please bear in mind I have a Win7 Pro OEM (should make no difference?) "clean" (meaning from a totally empty HDD) install. It therefore shows (in a Winbuilder LiveXP) a "C:\Recovery\{guid}\WinRE.wim" instead. It appears that the F8 then "Repair" yields pretty much the same as the Bootable Repair CD except it required me to logon to an account.

V6 doesn't work either. Repeat - MS has totally abandoned Win9x/ME and has (again) -wiped- the Fixes. The best yo'll get is a list that -may- contain a filename that you -could- use in a search that -may- xist on -someone's- server. MDGX website apparently down. Many files no longer exist there either. Here is another potential listing for those fixes filenames. http://erpman1.tripod.com/w9xmeupd.html AGAIN, there -is- an Unofficial WindowsME Pack (guess you missed that?). http://www.msfn.org/board/topic/61407-service-pack-for-windows-me/ And AGAIN, the MDGX website -appears- to be down ATM. This is the filename (and I have it) - MESP202B8.EXE (21,935,104 bytes) It -seems- that WinME didn't get patched as much as older Win9x. Basically, due to LAWS, they weren't "unofficially" retaining "official" updates. This Forum is based in the USofA. Please understand that and check the Rules (click the "MSFN Etiquette" link at the top). I gave you the two options and I give you a third one. This (fourth) one may or may not be useful. http://www.hpcfactor.com/support/patching/winme/ The -best- you get is a Filename and -hope- you can find it tucked away somewhere. Please don't get huffy. We can only help so much as to what -may-still be available. You're waaaay too late in the game. Heck, it's even difficult to find pre-WinME fixes, or for that matter MS is intentionally scrubbing Win2k/WinXP Updates. http://www.washingtonpost.com/wp-dyn/content/article/2006/06/30/AR2006063001587.html The Updates website has been -gone- since around end of 2009. @All - Anyone want to get this Unofficial ME SP (beta) from me and upload it somewhere? I have no (e,g,) SkyDrive (etc) account and refuse to create one. edit - and it appears that All Roads Lead To MSFN (when searching). edit2 - I -did- find this -but- use at your own risk. www.htasoft.com/u98sesp/downloadmesp.phpIt appears to be the last available WinME Unofficial Update (includes all kinds of extras etc). Described as "Updated Feb 15, 2014, UWMESP3.EXE Beta 5".

This has been hashed and rehashed repeatedly. The v4 Update site has been long-gone. It doesn't exist - period! MS basically wiped it out. Absolutely -no- Win9x updates are avalaible by it anymore. You have one of two choices - 1 - http://www.msfn.org/board/topic/95815-important-stickified-pinned-959898-seme-topics/ 2 - Search search search the WWW... BTW, duplicate post... http://www.msfn.org/board/topic/172573-windows-me-updates/

From all appearances (I use twitter also) they seem to imply they're a terrorist cell. I thought it funny that they thought if (hopefully when) they were tracked down that DBAN would totally wipe their HDD's -in time- (NOT!), apparently totally unaware of how long it needs to run to do it's deed. edit - well, jaclaz, I'll tend to "somewhat" agree with you. I actually use it to get news from nowadays since I see MSM omitting or distorting facts (which I of course check on first). MSM is no longer dependable. I'll say no more since we/I would be getting into MSFN Rules.

Could you be more precise with that Gateway ATX STF? More info. "Not connecting" tells us nothing. And I believe that it may be an on-board Intel.

Addendum - You might also Google this NT4 "USB support"Only third party USB Drivers. MS didn't ever provide for it. NT4 (like Windows 2000) was strictly business oriented. There's RAM limitations, HDD Partition size limitations, and-on-and-on. Also google this NT4 limitationsand this windows nt4 sp6 slipstreamMSFN jumps up immediately on the second one. HTH

Yes. Better check the specs/hardware limitations of NT4. You've answered your own question.

Related (appears to be for Vista->Win8.x) - http://superuser.com/questions/569449/how-to-remove-file-type-associations-in-windows-7 "assoc" and "ftype". I went into the Registry to disassociate ".BIN" from VLC - two places in the "Classes" - ".bin" and "VLC.BIN" before it would "go away". The first is the Extension which points to the second one which is where the old-fashioned display (in older Windows) of "File Types" (ftype) is. The "new dummy-proof" Windows is a horror for Geeks Who Play. HTH (as a little info...) And thx for the App link - it appears to indicate just what I said. Wish I'd seen this sooner.

No, you don't. The original request was for Dutch. As I have repeatedly said, you will play "heck" getting the Updates. Here is one source (includes the last version of AutoPatcher). http://www.tmeeco.eu/9X4EVER/GOODIES/Inside Autopatcher are all of the Official and Unofficial. Whether it works on your PC is a different matter (hardware-related stuff). Did you bother to look at this? There's also an Unofficial Service Pack. The same warning applies here. Bear in mind that the difference between it and Autopatcher is that it's a Service Pack-type package, meaning you can't pick-and-choose as the original Installers are not there. http://www.msfn.org/board/topic/95815-important-stickified-pinned-959898-seme-topics/ Please be aware that this is an English Forum and most information directly relates to just English. HTH

(sigh...) Tested the NSW2002 Goback v3.0.4.53 in VirtualPC on clean install Win98SE. Asked for Reboot, so OK - hangs at blinking cursor/black screen. Boot to LiveXP (WinBuilder) and MBR is overlayed with the GoBack one, Partition Type changed to "44", and a spanky new file on the C-drive (my LiveXP ignores Partition Types) named "gobackio.bin" (google that). Next, I try using the Removal ISO, it hangs during execution (go figure...). Here's a link that indicates *maybe* it's best to use two partitions. http://www.pcreview.co.uk/forums/major-goback-problem-t2828981.html Here's the oldest link to the Original WildFile website - http://web.archive.org/web/19991127225842/http://www.goback.com/? I *suppose* I could try the LiveXP, delete the BIN file, rename the GoBack folder (for funsies), change the Partition Type back to FAT32 "0C", boot the GoBack ISO, run "FDISK /MBR" and see what happens. Side note - be aware that you would need a Floppy Boot specifically with FDISK and PTEDIT (downloadable from Symantec FTP), reboot to it, then do the delete/rename if doing this outside of a LiveOS CD. The PTEDIT program is basically a "must have" as the FDISK should be on the HDD already. 1 - Basic Bootable Win9x Floppy with FDISK - get PTEDIT onto it 2 - Boot to it and use PTEDIT to change Partition Type, then run "FDISK /MBR" 3 - Reboot to it and rename/delete "gobackio.bin" and "C:\Program Files\Roxio" (maybe the WiledFile foldername I indicated above?) 4 - Remove Floppy, reboot, and pray to whatever gods you pray to. PTEDIT found here inside "PTEDIT.ZIP" ftp://ftp.symantec.com/public/english_us_canada/tools/pq/utilities/One might have HOPED the OP had made an Emergency Boot Disk (floppy) at one time or another, noting that the "sick" PC is the only one with a Floppy Drive. (le-sigh....)

FYI - 1 - Ctrl+Alt+G is (more than likely) in the MBR Code much like (e.g.) Dell's "System Restore" key sequence. 2 - The HDD may/may-not be zonked (filled up) by... GoBack. 3 - As soon as you "attach another Physical HDD" and/or create an additional Partition, GoBack "takes over". It "kind of" works like "System Restore" in WinME/XP-and-up but *vastly* differently. It runs CONSTANTLY, hence the statement Pee-O-S**t (KILLS the HDD's). NOT good for Gamers at all or even heavy Web Browsing, now is it? 4 - Also, you might note the "snippet" from CONFIG.SYS (booting to DOS Command Prompt). "FDISK /MBR" will completely restore the MBR. Again, I'll gladly install this junk on a Test PC and give further instructions as necessary. 5 - The REG file is "useless" on the "sick machine" since the "not so older machine" has no floppy. However, please note that the Burned CD provides access to the CD files. It would be possible to "recreate" the CD (NOT GOING TO DESCRIBE THAT to a n00b here) and include said REG file that *could* be double-clicked in Safe Mode. Indeed, that SINGLE LINE indicating the "RunServices" entry could be MANUALLY removed using Regedit in Safe Mode (F8) to turn-it-off, providing it can be Disabled AT LEAST ONCE and remove it WHILE DISABLED. Please note that the WWW is rife with GoBack problems, including but not limited to -LOCKS UP-. How about we wait and see the result from the CD/ISO attempt? Side note - It appears to boot to PC-DOS but utilizes Windows 98 (First Edition) files (e.g. SYS, FDISK, FORMAT, etc) and a smattering of Win98SE as well. (Yes, I dumped it to look.) Addendum - Antivirus is going to be useless until GoBack is obliterated, amirite?

No, absolutely not. I guess you missed the part where the Master Boot Record is altered? BIOS->MBR->PBR->OS So, you can't download and burn the ISO with this computer? This has nothing to do with Floppy. Read this - http://en.wikipedia.org/wiki/ISO_image BIOS->CD-ROM-BOOT->GobackBeGone Need I get screenshots of a Gateway (actually *normally* Intel) BIOS Setup Screen to show you how? Try pressing F2 *repeatedly* when you turn it on. There will (should be) be a "Boot" selection there - change it *after* you Burn The ISO Image using your other (unnamed) Computer and boot to it. 1 - Download ISO to "other less older" Computer 2 - Burn ISO to CD-R (NOT DVD!) 3 - Turn on "sick" Computer and press F2 (AFAICR), change Boot Order 4 - Stick Burned CD-R in CD-Reader 5 - Press whatever key in BIOS that says "Save Changes" (usually F10) 6- "Sick" Computer will boot to CD-R - do whatever it says to do. 7 - Report back. (Another unnamed computer). Please state the Make/Model of said "sick" (some kind of Gateway 2000?) and "less older". Sir, I'm 63 years old. Please don't use your age as an excuse for not thinking clearly. Thank you. Now, if you *refuse* to do that... well, the ball remains in your court. Here (again) is the link to the FTP Folder containing the ISO Image - ftp://ftp.symantec.com/public/english_us_canada/linked_files/GoBack/ There's also a REG file that completely obliterates all traces of GoBack from the Registry, including the Service that has been haunting you. Here is the CONFIG.SYS selections in the CD ISO Image [menu]menuitem=GBPROGU, To unhook GoBack (for typical machines)menuitem=GBPROGR, To repair the Master Boot Record (for typical machines)menuitem=PCDOS, To Load IDE (typical) CD-ROM Drivers and exit to the command promptmenuitem=SCSI, To Load SCSI CD-ROM Drivers and exit to the command promptHere is the AUTOEXEC.BAT actions for above :GBPROGUecho *****************************************************************echo This Utility will allow you to remove Norton GoBack from yourecho system's partition table. If you do not want to do this, pleaseecho remove the CD-ROM from the drive now and restart your computer.echo.pauseecho.echo Unhooking GoBack from MBR...echo.%CDROM%:\GB_PROG.exe /uecho.echo Norton GoBack has been removed from the partition table.echo Please restart your computer.goto ENDNeed I say more? Erm... guess I do, since Drugwash responded. Here is a snippet of the code inside the REG file (that can be run in Safe Mode) [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServices]"GoBack Polling Service"=-[HKEY_LOCAL_MACHINE\Software\Symantec\InstalledApps]"Roxio GoBack"=-I'll let him explain that one since he's already mentioned it. (Wildfile->Adaptec->Roxio->Norton/Symantec - same GoBack software) I'm out of this... Addendum - I'll happily install this POS software on a test machine to prove this to you. Did I not state that I had done this to someone's PC some years ago? I even described the "HDD thrashing"... And and Edit. This is found inside the Program (also at the FTP site) that gets executed from the Bootable CD (ISO). C:\PROGRA~1\WILDFI~1\GOBACK\GB_PROG.EXEThis clearly indicates that the "maker" of said software includes (you guessed it) - WILDFIRE! (found via Hex Editor)

Seems that's part of "extsis.exe" - "Aquarius Symbian 9 SIS files editor". https://www.virustotal.com/en/file/e63a04d1a6c601734202b69fd39831aaadd2cc22063f2903da6105661af78df2/analysis/#behavioural-info Part of SISware? http://sisware.software.informer.com/ Nokia? http://www.allaboutsymbian.com/ http://www.komeil.com/blog/sign-unsign-symbian-siscontents Here - http://symbiandev.cdtools.net/batchunpack.html http://symbiandev.cdtools.net/

Actually there are several factors of which two are - 1 - How was it originally packaged? 2 - Can it be repackaged the same way or can it be repackaged in a similar fashion? All Packages don't intall in the same fashion. Bear in mind that UE extracts a myriad of packages/compression methods. Easier to right-click original package and discover the Installer Method. Of course, you can use a different method but you still need to know the original. HTH

GoBack - same software, different owner - http://en.wikipedia.org/wiki/GoBack Looks like Gateway's agreement began in 1999. So, may I inform you that I removed the GoBack from someone's Windows98SE Gateway 2000 PC with that software? (Please note aquisition dates when passed from hand-to-hand) Gateway's Sales Pitch - Refers to the Adaptec "version" (98, 98SE, ME) - http://panam.gateway.com/s/issues/666801110.shtml Also refers to WindowsME - http://panam.gateway.com/s/issues/667607110.shtml So let me guess - you didn't try it, did you? Let me repeat myself - same software, different owner now, has been and always will be a pile of junk software fraught with problems. It constantly monitors all HDD activity and constantly backs up -any and all- changes, thus thrashing the crap out of the HDD's. http://www.wikihow.com/Remove-Norton-GoBack-from-Your-PC-and-Access-the-Hard-Drive http://www.bleepingcomputer.com/forums/t/74951/how-to-get-around-norton-goback/ This - http://www.cgsecurity.org/wiki/GoBack A rose by any other name is still a rose. I'll not say it again (since you want to argue/ignore) - Try it or don't try it. Your choice...

May or may not have something to do with it. Five Prerequisites? http://www.msfn.org/board/topic/159082-internet-explorer-11-updated-12082014/ Google "ie11" site:msfn.orgindicates some probs w/IE11.

1 - Overheating - I don't have "newer" Dual-CPU (only the old P-III Slot) but on (at least) this MoBo, the Heat Sensor is some kind of "stick-up contact tab" kind of thingie. You might want to check that the contact between CPU and Sensor Contact are both clean and fully contacted (*carefully*). Just a possibility. 2 - DEP - Not sure how that works (exactly) but it *does* have something to do with a BIOS setting in relation to the CPU's ability to support it.. Look for this (CPU on this PC does not support it) - Data Execution Prevention (DEP, NX, EDB) - yours undoubtedly has this support. Also, you might note that dencorso suggested using this in BOOT.INI "/noexecute=AlwaysOff" <-disabled it (NX) entirely in the OS. Some people find it to be nuisance, though. Basically, it's done by Software *and* in conjunction with Hardware (if supported) <-but you knew that. HTH disclaimer - have not and never will claim that I have all the answers, but *sometimes* I'm right.

It is with deep sadness that I report that Robin Williams has died this morning from an apparent suicide by asphyxiation (pending final Coronor's report). I have read the official Marin County Coronor's preliminary report stating that he was officially declared deceased at 12:05PM Pacific Time. It has been reported that he was battling severe depression. At this point all I can say is DAYUM, I liked his stuff and will definitley see his last performance as Teddy Roosevelt in "Night At The Museum III". R.I.P., Mork. And Nanu, Nanu.

(Still thinking the gLAN problem is some sort of setting somewhere..) ...and Are you, by chance, booting with the "/PAE" option in BOOT.INI? Could you say what the symptoms are of the 16-bit proggies not working? I wouldn't think the "bitness" of the Hardware would have anything to do with it? (please note what the PAE parameter says in the link jaclaz gave)

That's because you're in the wrong place to ask/try. Obsolete methods. Note the date of the last post is 2009? The following is where you should go (actually works). http://www.msfn.org/board/forum/157-install-windows-from-usb/ HTH

So sorry, those aren't all-inclusive via Wayback as the individual Updates beyond those were only accessible via Windows Update, now completely defunct and inaccessible. The given Wayback "link" only gives "corporate" (if at all). I have the whole pile before it went "down" in English only. You're only alternative is to search, search, search and hope you get lucky. HTH

Just read the link - sounds reasonable...

Laugh as you will. They just haven't been "buried" yet and the stench is horrible! I hesitate to cremate them as the City may not like the smell of burning plastic and circuit board. I shall soon, instead, resort to a Logan's Run style disposal (recycle the remains for others to consume). I now have a "better" ( to use the word loosely ) Dell - an I531 which happily has Win7ProOEM residing on it. P.S. "Accidental" is putting it mildly. G-kids screaming will do it every time... (#1 - "KRAP! I forget to MOVE THE JUMPER BACK!") (#2 - "KRAP! I didn't INCREMENTALLY update the BIOS!")

I'll start off right now saying YOU DID IT WRONG!!!! STOP WATCHING THAT TUTORIAL - FOLLOW MY INSTRUCTIONS TO THE LETTER! I specifically said the stuff WITHIN the folder, NOT THE FOLDER ITSELF! I said EXTRACT THE CONTENTS! How on Gods Green Earth did you extract? I'll end with a screenshot and a comment - BIOS do NOT always say "USB DEVICE". My Boot Screen (the one like your ESC) Specifically lists "Sandisk" (which is my USB Device) plus the DVD Drive (only ONE of them, it has TWO) and NO HDD AT ALL. Now, in the Boot Menu (via F2, this is an Intel-based BIOS) it DOES, however list an Option "USB Boot" which is "enabled" and under "Hard Disk Drives" it lists "Sandisk" and the REAL "HDD" (named "PM-WDC" yada-yada). So, I am GUESSINg that MAYBE you can NOT boot to it. UNLESS, did you READ that whole "Screenshot" thing? Mine: Screen #11 (Main Boot Screen, ignoring extraneous) - 1 - PXE Boot To LAN (disabled) 2 - USB Boot (enabled) <- Mine has that option BUT I have NO "REMOVABLE DEV." (you keep using that exact word) 3 - Boot Device Priority <- DO NOT PRESS THIS YET!! WRONG ONE I SPOKE OF! 4 - Hard Disk Drives <-THIS ONE!!!! Will list what it RECOGNIZES as HDD -IF MORE THAN ONE-! (I said that) 5 - CD-ROM <-This one lists BOTH of the DVD Drives, one is a Burner, the other is a Reader) - IF I had a Floppy hooked up it WOULD list it, but I have that "disabled". YOURS does not HAVE ONE AT ALL (side note - did you even get your User Manual from the repeated link given from Sony Support?) * Bear in mind, my BIOS is somewhat different. To continue to the RIGHT SubMenu - Select #4 and tell me (when you get another Keyboard), press Enter and tell me what you see. You SHOULD see the USB Device but IT MAY NOT LITERALLY SAY "USB Device"! * I will also point out that in the "ESC" Screen it DOES NOT LIST THE OTHER DEVICES! It's LITERALLY giving ONLY the CD-ROM and USB since THAT IS WHAT I PERSONALL HAVE SET IN THE "F2" SETTINGS. IOW, you *MAY* have the USB listed in THE CORRECT SCREEN! Sir, your terminology leaves a lot to be desired. The ISO is a DVD ISO and you will be burning to a DVD not a CD. Preferably a Single Layer DVD+R and NO OTHER and it MUST BE OF GOOD QUALITY and -preferably- burned at 4x if you are going to try that route AGAIN! I understand you -may- be PC Illiterate, but come ON, dude! You can't be THAT illeriterate, you've already stated you changed the HDD and restored to it! Did you let everything go on Autopilot? http://www.msfn.org/board/topic/172356-xp-home-sp3-in-reboot-loop-no-f8no-bsod-oem-sp1-need-slipstream-bd/#entry1083041 NOW, as for USB - Have you TRIED that USB Stick in ALL OF THE PORTS? Why do I ask? -SOMETIMES- a BIOS will NOT recognize a Bootable USB Device in CERTAIN PORTS! INdedd, -SOME- BIOS won't recognize a USB Keyboard -except- in CERTAIN PORTS and will -ignore- it if in -any other-. HERE is what the Marketing Specs say Are you going to tell me that these won't be recognized in the BIOS and Bootable? REALLY? It -also- states it has an Intel 915PM Chipset. That's "relatively" new. IOW, that's quite a "crippled" BIOS. Since it has absolutely NO FLOPPY, one wonders how one -might- have updated the BIOS -if- one was available (it has NO INTERNAL FLOPPY!). Look at MY snapshot of MY Bootable USB!See this difference? Even WORSE, you have the "Tut43_FiraSO" listed TWICE! WHAT ARE YOU DOING, DUDE!!! Your FIRST "Tut43_FiraISO" -CONTENTS are correct -BUT when you -BUILT- it you did NOT take the -CONTENTS- (not the WHOLE FOLDER, but the CONTENTS) when giving the Folder Name! I -specificallu- said! There is ABSOLUTELY NO FOLDER NAMED "Tut43_FiraISO" within the ZIP File "Tut43_FireaISO.ZIP". If you used an Unzip Program -DO NOT EXTRACT- to "Tut43_FiraISO" use "Extract To..." and BROWSE to (e.g.) "C:\MakeUSB" folder! IOW, you did NOT follow my instructions TO THE LETTER! The CONTENTS of that ZIP file is EXACTLY what MY screenshot SAYS! If you WOULD have done it that way your QEMU test would have shown what MY QEMU test showed, understand? BTW, WTH does "tut#32" have to do with my SPECIFIC INSTRUCTIONS? --DO NOT WATCH ANOTHER DAMM VIDEO-- Use -my- instructions because I SPECIFICALLY SAID IGNORE EVERYTHING ELSE, did I not? You just said I call BS, you -NEVER- said you could actually -ACCESS- any options and -USED- them. You JUST NOW said you did that and, -worse-, you -CLAIM- to have said this ELSEWHERE! http://www.msfn.org/board/topic/172356-xp-home-sp3-in-reboot-loop-no-f8no-bsod-oem-sp1-need-slipstream-bd/?view=findpost&p=1083504 http://www.msfn.org/board/topic/172356-xp-home-sp3-in-reboot-loop-no-f8no-bsod-oem-sp1-need-slipstream-bd/?view=findpost&p=1083428 We have a search facility here and you never said anything about Safe Mode except THESE two places! NEVER here!!! http://www.msfn.org/board/topic/172356-xp-home-sp3-in-reboot-loop-no-f8no-bsod-oem-sp1-need-slipstream-bd/?view=findpost&p=1083629 http://www.msfn.org/board/topic/172356-xp-home-sp3-in-reboot-loop-no-f8no-bsod-oem-sp1-need-slipstream-bd/?view=findpost&p=1083504 DUDE! You -are- yanking chains here, and I don't appreciate the fact that you've drug this on with misinformation, lack of information, and proceeding with every instruction (even -modified- instead of -exact-) -but- what was given here. Screen shots? How did you take Screen Shots of the "Black Screen"? With a camera? Edit you last post (before this one) and -REMOVE- those because they show -NOTHING MORE- than "you created a USB wrong" and POST AGAIN FOLLOWING THIS with the supposed "screenshots" you made for "elsewhere" ("microsoft board"). What's REALLY weird is everytime I had a "dirty bit" set is that it NEVER went to an F8-type Screen, it ALWAYS AUTOMATICALLY DID CHKDSK! (You're BS'ing us here.) AGAIN! - WHEN you get another keyboard - SPECIFICALLY select "Safe Mode Command Prompt" and see what happens -AFTER USING "Diskpart"/"Chkdsk" INSTRUCTIONS- (that is -IF- you don't have that result that you posted "elsewhere"). - UPLOAD those Pics after deleting the Useless Pics. - REDO THAT USB like I SAID and IGNORE EVERYTHING ELSE IN REFERENCE TO BUILDING ONE! (MY way or HIGHWAY!) - Stick the USB in a DIFFERENT PORT and try it! (two on Rear, one on Left) BE SURE THEY ARE ENABLED IN BIOS (wherever that may be, since I DO NOT KNOW what it looks like and SPECIFICALL ASKED you to write it ALL down and report it!) - IN THE BIOS, do the SELECTION I said and TELL what it says! * A small point but SIGNIFICANT (and MAY have a bearing on BIOS recognition)... Within the RMPrepUSB Menu there's TWO ALTERNATIVE selections for Partition Formatting: 1 - Force Use of LBA Calls 2 - Use 64hd/32sec if possible Bet you didn't even hover over them to see the descriptions, did you? (Your Country Flag says USA - what shift do you work to be posting at odd hours?) Beyond all of the above, I no longer want to play this game. Play by OUR rules or go play in someone else' yard... -Apologies to Mods/SuperMods/etc... getting tiresome. Do what you will.

(I'm going to hate myself for this...) 1000g/sNIC<->100g/sRouter A setting problem?