jaclaz

FGA. Yes http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/problem-report-standard-litany.html But do not ask here for support - even indirect - to WAREZ releases, check Board Rules. http://www.msfn.org/board/index.php?app=forums&module=extras&section=boardrules jaclaz

I believe this depends on the exact situation. http://www.microsoft.com/oem/en/licensing/sblicensing/pages/downgrade_rights.aspx#fbid=HvSiguYh4Ef a copy of the Digital River .iso and the generic Windows 7 keys should do At least from a logical point of view (which not necessarily reflects anything MS related ) if one needs a media AND key, it is not a downgrade, it is a reinstall (and as such it makes no sense to pay additionally the Windows 8/8.1 license as if you already have a valid media and key, you already payed for a "full" 7 license and you can install on the new piece of hardware fine. jaclaz

It is interesting how Malcinio joined the board and made his first post to recommend a piece of software. Altruism brought to a next level. jaclaz

The confusion is that most of the Winbuilder .scripts (but not all) are aimed to build a PE (Preinstallation Environment) of some kind which is not an "install" (not "from", not "to") of *any* kind. The only Winbuilder project that I can remember that creates a "portable" XP (which is NOT a PE) is the one by Misty called "MiniXP": http://minixp.reboot.pro/ which, unlike the several misnamed Winbuilder projects that contain XP in the name (such as - an example - LiveXP), is actually a (very minimal) XP and NOT a PE. A PE (1.x/2.x/3.x/4.x/5.x) is NOT an "install" and a PE (1.x) is NOT a "portable XP". <- this last character is a "full stop" or a "period" On the other hand there are a couple projects by wimb that are NOT based on Winbuilder but do create a "portable" XP (though I am not so sure that they are compatible with a XP 64 bit source): http://reboot.pro/topic/9830-universal-hdd-image-files-for-xp-and-windows-7/ http://reboot.pro/topic/18657-vhd-xp-compact-make-mini-xp/ As the actual Author of the program just tried to communicate - failing to reach you - WinsetupFromUSB could be renamed to WinsetupFromUSB_To_Any_R/W_Mass_Storage_Device_Including_USB_connected_Ones, the point here is that when source (FromUSB) and target (ToUSB) are the same device it is possible that the setup routine gets tricked by "other connected Mass Storage devices" AND that XP 64 bit - though tested - has not been extensively tested like the more common XP 32 bit. jaclaz

I will bookmark this under "senseless" unless submix8c will be so kind as to provide a meaningful explanation. For the record Winbuilder is a scripting engine (and nothing else), so the validity of the equation, more than debatable, is null, you know a lot like: "Building"="concrete mixer" or "Cabinet"="hammer" jaclaz

Let's see if some basic math helps: Seemingly (on other people systems without the extensions you have): Aeroglass+Chrome = No memory usage spikes On your system: Chrome + a number of extensions + a number of user scripts = No memory usage spikes Aeroglass + Chrome + a number of Chrome extensions + a number of user scripts = Memory usage spikes It would be a nice experiment to try (on your system): Aeroglass + Chrome (with NO extensions, NOR user scripts) and see if the result produces those Ram spikes or not. jaclaz

Well, again, a Czech Republic Registrant using a Dutch host and selling in US$ only: http://whois.domaintools.com/softwaretopgrade.com may be EITHER a sign of globalization OR of something fishy . Getting the actual .iso from Digital River is one thing: http://www.infoworld.com/t/microsoft-windows/windows-7-sp1-downloads-dry-microsoft-distributor-digital-river-239224 http://www.infoworld.com/t/microsoft-windows/windows-7-sp-1-downloads-once-again-available-digital-river-239516 (and it could be a good way to test for 30 days the Pro vs. Ultimate), but then you will need to buy a key. Digitalriver (please read as Microsoft) doesn't AFAIK sell anymore the Windows 7 keys, so your options are IMHO to buy an original DVD ("physical disc" AND NOT an "electronic download") from a reputable source or get a Windwos 8/8.1 Pro and use your downgrade rights. Precedent experience with sites selling electronic downloads (which are not digitalriver or store.microsoft.com) have traditionally been a scam, of the one or the other kind: http://www.technonsense.com/2011/02/cheap-windows-7-winkey-sale-scam/ jaclaz

Q.E.D. Don't worry too much , your English doesn't seem to me that much bad (said by an Italian) , and I suspect that also Ilko_t (who is from Bulgaria) won't protest much about it . For the scope of installing a XP on it, possibly a "Fixed" disk device would give some advantages, but most probably these can worked around adding Diskmod to the actual installed OS: http://reboot.pro/topic/9461-page-file-in-usb-hard-disk/ (in theory it should work on XP 64 bit, but of course it needs to be tested) But anyway, let's first see how the new attempt with latest WinSetupFromUSB goes, and then we will see if the above is *needed* (or *desirable*) and, if it doesn't work, we may talk of "flipping the bit" on the "Removable" device to set it as "FIxed" (if we can identify the stick's controller and find the relevant Manufacturer's Tool). jaclaz

Naah. There is a much simpler explanation , it's actualy a shortening of my name and surname: http://jaclaz.altervista.org/Projects/USB/USBstick.html ...though I thought jacla was a Navajo/Native American thingie: http://nativeamericanjewelrytips.wordpress.com/2013/06/13/jacla-jackla-jocla-no-matter-how-you-spell-it-what-is-it/ jaclaz

Yep, and - basically - it makes NO SENSE whatever for a non-enterprise customer to have Enterprise and not much sense for anyone to prefer Ultimate over Professional. The differences are little (and of no or very little practical use), see: http://winsupersite.com/windows-7/windows-7-product-editions-comparison In practice the only possibly useful things[1] missing in Professional are Bitlocker (that is basically a very good way to appear 1337 AND lose all your data before or later) and booting natively to VHD. (there is also MUI support, but it is unlikely that it has any use in a non-multinational enterprise) jaclaz [1] by definition possible useful things are whatever one can understand their use and may actually want to use, according to common sense (a surprisingly rare to find ability)

Ok. Let's wlite be. Here is a suitable icon draft. wlite.bmp. Can we have the tool, now? jaclaz

Yes. The idea is that a copy of the "source" files (pre-SP) are in C:\XPSP3. The SP file is in C:\SP3\, youfirst extract it's contents that will go in C:\SP3\i386\. Then change current directory to C:\SP3\i386\ and run the update.exe with the /integrate switch pointing to the source files, i.e. C:\XPSP3\. The update program will replace some of the files with the corresponding SP3 updated version (and change some other setting files. After the procedure ends successfully, the files in C:\XPSP3 will be "current". As said the procedure may not work for two reasons mainly: the "source" is not "valid" (i.e. the CD does not contain a "plain", "normal" XP SP1 - thank th egood Sony guys for making a mess of an otherwise simple thing) the "environment" is not suitable (i.e. the Windows 7 - thank the good MS guys for this - has some incompatibilities with update.exe).In your particular case the two reason may even happen at the same time. We *somehow* managed to "fix" similar situations in the past, see here: http://www.msfn.org/board/topic/120423-how-do-i-make-a-bootable-xp-cd-out-of-the-i386-folder/ (but in that case the files on the hard disk were used as "base") and here (from a recovery CD): http://www.msfn.org/board/topic/91907-cannot-access-cd-containing-windows-xp-installation-files/ A thread where a similar procedure (in painstakingly detail) is represented is here: http://www.911cd.net/forums//index.php?showtopic=24161&hl= It is of course "a lot of work" and there is no real guarantee of success... If you can afford to buy )or however procure yourself a "standard" CD it would surely be easier. In any case, you will need (to be on the safe side) to use a "real" XP or get this "Virtual Machine" for 7 and run the tools in it: http://www.microsoft.com/en-us/download/details.aspx?id=8002 jaclaz

This is "queer". The NF-CK804-6A61FD4EC-00, see here: http://www.tomshardware.co.uk/forum/194868-30-expert-skill-series-dual seems connected to the date of 12/07/2005. Even if the actual naming/versioning of BIOSes/corresponding files is often what I define "pure folly" , it would be strange that two releases, corresponding to files NF4ED406 (04/06/2006) and NF4EDC07 (12/07/2005) show the same version on screen. The actual page on NFI site is seemingly down, but the google cache is working: http://webcache.googleusercontent.com/search?q=cache:NRGdMyVs0xIJ:www.dfi.com/DFI-Lanparty/support/MBBiosDownload.jsp%3Fshowselectvalue%3D10LP_UT%26selectBiosItemId%3D479+&cd=2&hl=it&ct=clnk&gl=it&client=opera You could try dumping the current BIOS and compare it to the above two files from the DFI website. jaclaz

Well, you have to consider also the sound it makes when read aloud by an English speaker. nliteX may sound too similar to "in latex" doubleulite could be better as it might sound more like "double your light" jaclaz

The error with nlite is not readable easily, but it seems like pointing out an issue with the actual "base" source. It is also possible that there are some issues running nlite (or the service pack) under WIndows 7. You clearly followed the instructions here for the first attempt of integrating SP2: http://winsupersite.com/product-review/slipstreaming-windows-xp-service-pack-2-sp2 (which AFAIK/AFAICR are OK). Maybe you had some issues with paths , or maybe, for any reason, something went wrong when downloading or expanding extracting the XP SP2 executable or there are some issues with permissions (but you should have some different kind of errors if the latter) or there were some copying issues when copying files from CD to hard disk . But you can slipstream "directly" a SP1 source to SP3. Try following to the letter this set of instructions (they are very similar to the ones above related to SP2): http://kb.parallels.com/en/5446 Do open a command prompt with Administrator privileges (you never know) to execute the commands. Report what happens. (what you reported doing seems fine , but sometimes a small glitch in the matrix may happen) Theory of operation: by re-doing the copy from CD to hard disk we can reasonably exclude that there was some error (or it should show)by using the SP3 instead of the SP2 we may reasonably exclude the possibility of a failed/botched SP2 download (unless of course also the SP3 is a botched one)jaclaz

Maybe yes, maybe not, but it is not like "You only live activate twice once" . A non OEM license can be transferred fine (as well as an OEM if it includes the hardware), and will activate (again and again) fine, as long as it is not - for any reason - blacklisted by the good MS guys (something that may happen if the license/key becomes "public" and they get tens, or hundreds or thousands requests for activation in a short period of time). Just as an example, if, a month or two after first activation you are affected by (say) a virus and decide to re-format the disk and re-install from scratch (or your disk drive dies and you need a new one) you will need to activate again your copy, and if you don't overdo it (like attempting re-formatting and reinstalling and asking for activation thrice a day for one week ), you won' t have issues with automatic activation, and in case of issues you can still phone MS and ask for a "manual" activation, which they will normally grant you after a minimal verification process. No idea, sorry, I try to stay as away as I can from that madness, see: http://www.msfn.org/board/topic/172139-trying-to-decide-on-operating-system-and-office-package/ and my personal advice is to also stay away from it, the previous versions of MS Office are IMHO much "better" and there are several "good enough" alternatives, some of which also free. jaclaz

With all due respect , the info you provided is not much useful for troubleshooting, you listed several different tools related to USB booting. WHICH tool did you use to "prepare" (partition/format/etc.) the USB stick? HOW EXACTLY did you prepare the stick? WHICH EXACT (make/model) is the "16GB USB3-Stick" you used?Is it a "Fixed" or "Removable" device?[1] WHAT EXACT error/issue are you having? (please describe what you see happening, as opposed to the "result", like "the bootloader on the origin-stick can't be found - or let's sayit get confused with the other bootloader on the aim-stick. Seems like there are written some datas during the 1st bootstep on the origin-stick") Standard litany, please: http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/problem-report-standard-litany.html You have to understand how even the mere process of writing down an accurate description of your actions and their results may help in pinpointing the cause of the issue. jaclaz [1] This may be relevant as while - say - 99.99% of USB 2 sticks are set in the factory as "Removable" a large number of USB 3 sticks may have been set in factory as "Fixed" devices (generally the fastest ones), and this may affect the booting process.

And maybe one could get away with it also saying that he is "looking in the existing market to evaluate the possibility of entering that business" jaclaz

There is a dedicated thread for that tool: http://www.msfn.org/board/topic/142382-rt-seven-lite-rc-build-170-and-beta-build-260/ From what I can get from there it is now in an "abandoned" state. You may want to make sure that your source is an "original" (hologram, etc.) MS install disc and that the copy of RT seven lite you have is "unmodified". You may want to get a "reliable" copy from here: http://www.softpedia.com/progDownload/RT-Seven-Lite-Download-174061.html It is entirely possible (but improbable, since the tool has been widely used in the past) that you have a "queer" combination of "original" source and "unmodified" RT seven lite that produces that screen. jaclaz

Yep , JFYI : http://www.msfn.org/board/topic/170361-experimenting-with-refs-on-win-81-it-does-work/#entry1061240 jaclaz

Sure , it sounds good as an ad: : jaclaz

You can get a Windows 8/8.1 Pro license from MS and use your downgrade rights, or find some other source, which may include "used" software. See this: http://www.pcworld.com/article/2105765/3-ways-to-get-a-new-windows-7-pc-in-the-windows-8-era.html Cannot say in the UK, but in the US (among others) NewEgg is a known source: http://www.newegg.com/Microsoft-Operating-Systems/BrandSubCat/ID-1149-368 I presume that there are UK based comparable hardware/software sellers. jaclaz

I am sure a large number of Egypt based software selling companies are partners of MS and sell their (MS's) product internationally through UK websites. http://www.whois.com/whois/microsoftcheapsoftware.com http://www.scamadviser.com/check-website/microsoftcheapsoftware.com It is not clear (to me) if the site is selling "counterfeited software" or, as they seem to say here, they take advantage of different product prices in different countries (which may be perfectly legal ) to offer lower prices: http://www.justanswer.co.uk/law/7yc4y-paypal-google-suspended-accounts-no-reason-saying.html Some more related results: http://irenagilbert.brandyourself.com/ there is another software company with the same phone number and address: http://www.softwaresdigital.com/ http://www.softwaresdigital.com/about-us-1-w.asp http://www.whois.com/whois/softwaresdigital.com And also this other one has the same address: http://www.a1companies.com/contact-us/ which offfers Company Registration and Company services. The 2 WoodBerry Grove must be a very large building (or at least it's first floor), as it seemingly hosts also: http://www.globalenforcementsolutions.co.uk/ https://www.whoareyoultd.com/ http://www.patientsfirst.org.uk/ jaclaz

The CMOS checksum error could be connected to a defective/worn out CMOS battery, check it (and it's contacts) first thing. Next thing I would try (though there are risks involved in the process) would be to upgrade/reflash the BIOS firmware. Which version of BIOS do you have? Usually if you press Pause when booting you can see the date and version of the BIOS. It is well possible that for any reason a "tweaked/modified" BIOS was flashed and this can be part of the problem: http://www.techpowerup.com/articles/other/114 jaclaz

You see , you are a professional, doing professional things and I am pretty sure that every single US$ you spend on hardware and software is well spent. But you belong - like it or not - to an elite of people (professionals in the software industry, that make a living out of using this "tool"), what is good (and appropriate) for you may well be not good (or appropriate or affordable/justifiable) for the "average Joe", that was the point. Of course SSD's are really nice and fastish thingies, but IMHO suggesting that everyone should have a RAID with 4x512 Mb SSDs to have a responsive system is a lot like saying that everyone should have - say - a McLaren P1 in order to be able to get "serious" car driving experience. So, in my perverted mind, a single 128 or 256 Gb SSD (for actual System) + a "conventional" hard disk 512 or 1 Tb in size (for Data) + 2x (external or internal) 1 Tb drive for backup, are already what I would consider "more than enough" for - say - 85% of people needs. But the point here (and on this we are actually saying the same thing) is that - at the moment - noone, not even a software developer, has an actual *need* for a device bigger than 2 Tb, and in any case there is no actual need for booting the OS from a larger than 2 Tb device. If you check a few "standard" desktop PC's, let's say the homepage of Dell and HP, you will see how the price range goes roughly from 500 to 1500 US$ and offer a single hard disk from 500 Gb to 2 Tb. You just confirmed how even in your "faster than average" needs and highly tuned, custom built, PC you don't *need* more than 2 Tb. So, the "right" answer about benefits of EFI/UEFI for the final user (which was the direction in which shae shifted the topic ) is still "None, yet". The industry is pushing like mad this new EFI/UEFI "standard" (which as said IMHO is a "non-standard" at the moment) since a few years that provides no real benefits/advantages to the final users (and won't produce them for the few next years). jaclaz