jaclaz

Well, but - to be fair - in exchange for that Mouse Ballistics was applied , and all the gamers were (and still are) very happy about this : To sum up: Windows 2000 was a bettered NT 4.0, actually better. Windows XP was a very slightly bettered Windows 2000 with a toyish interface and with a number of senseles features added. Vista was a bettered XP, only worse. 7 was a bettered Vista , actually slightly better with an increasingly toyish interface 8 is a quantum leap , it is directly a toy jaclaz

Or because a number of businesses refused to upgrade their Office 2000 (that was working) to the XP one (2002) which was severely buggy, and to 2003 (which offered NOT *any * real advantage) and thanks to the needless use by most demented people of the senseless .docx and .xlsx "new" formats were eventually "forced" to "jump" from good ol' 2000 to 2007 or 2010? BTW only to find besides the REALLY slowing up work ribbon interface, also a few nice features REMOVED? Something I just found out the other day: If you read attentively the source (highlighted the interesting parts): http://blogs.office.com/b/microsoft-excel/archive/2009/11/02/excel-add-in-for-manipulating-points-on-charts-mpoc.aspx it can be used to infer that: Since the reaction time of the MS office team (which - with all due respect - has as focus a much simpler target than a "whole" Windows OS and the actual "issue" is so simple that can be solved by an add-in, a bit simpler that changing the whole GUI interface) is not snappy enough to react in over two years, then, even if the good MS guys would listen to actual user feedback, you can expect a "fixed" Windows 8 GUI by 2015 . jaclaz

OR do "the right thing" and use SHSUCDX, instead . http://adoxa.3eeweb.com/ http://adoxa.3eeweb.com/shsucdx/index.html Seriously, MSCDEX cannot possibly recognize and access a number of CD's, simply because some of the .iso extensions were made AFTER the MSCDEX was released. About USB, your best choice is to try this floppy here: http://johnson.tmfc.net/dos/usbdrv.html strangely down , via Wayback Machine : http://web.archive.org/web/20100127181929/http://johnson.tmfc.net/dos/usbdrv.html http://web.archive.org/web/20100127181929/http://johnson.tmfc.net/dos/usbdrv.html jaclaz

They also filed new ones. Example: http://www.tomshardware.com/news/microsoft-patent-lcd-screen-hygiene,13783.html maybe they are going to (swiftly) move from software to "Tablet screen sanitizers" We do have some similar examples in the past (please read as "in the future" ): http://collateraldamage.wordpress.com/2006/05/02/douglas-adams-right-again-lack-of-phone-sanitizers-will-doom-planet/ http://en.wikipedia.org/wiki/List_of_minor_The_Hitchhiker's_Guide_to_the_Galaxy_characters#Telephone_Sanitizer And even an interesting start-up: http://shop.cleanergear.com/ I cannot but find a few similarities between the instructions here: http://cleanergear.com/support And the famous toohpick ones: http://en.wikipedia.org/wiki/List_of_minor_The_Hitchhiker's_Guide_to_the_Galaxy_characters#Wonko_the_Sane Humanity is doomed ..... jaclaz

Very good. I would presume that when you use 1.5 Gb instead of 600 Mb of disk space, there must be *something* added to an OS. 1500/600=2.5 I am glad to know that - contrary to my previous beliefs - EVERY single Mb of the 900 Mb more are worth it, and that every added feature, including Autoplay is actually an improvement. And of course all the work by Nuhi and fdv is perfectly pointless . Of course I a do not approve of many things (not in the article by itself, but in viewing it as "Windows XP is better than 2K" advertising for it) but notwithstanding the "opinions", the article looks like very accurately written and exhaustive . jaclaz

You don't REALLY want me to tell you. http://www.911cd.net/forums//index.php?s=&showtopic=16534&view=findpost&p=125036 Easy, logical explanation : jaclaz

Yep, that is a view of LBA sector 202213012. This is going to be a loong thread (and it does not belong here, this is becoming "generic data recovery" and NOT 7200.11 specific), please start a new thread for it. Basically *any* software tries to interpret "RAW" data (which is stored in the HD sectors). If even a teeny-tiny byte is "wrong" some software may be unable to interpret the data (just as an example removing/altering the 55AA Magic Bytes makes from the MBR *any* Windows built-in tool to fail interpreting a whole disk). Recovery software tries to detect the sectors or bytes missing/altered/whatever and tries to correct them and/or hints you about where to manually correct them. Most recovery software is aimed to "basic disks" and not to "dynamic disks" (thus they can find "nothing inside"). You need a dedicated tool AND a more than basic knowledge of the layout. From the screenshot it seems like DMDE finds that partition allright, but you need to study and learn BOTH about how a Dynamic disk is made AND about the specific tool usage, we are well beyond the "click-here-and-I-will-automagically-recover-all-files-approach" a number of "end user" recovery tools tend to adopt. jaclaz

Since it has already been (senselssly) bumped, it should mean that somehow this thread is "easily visible" through a search engine or Board Search feature. So, it may be of interest to post some related news: httpdisk: http://reboot.pro/13049/ Getwaiktools: jaclaz

With *any* hex/disk editor. The one I normally use and suggest is Tiny Hexer: http://reboot.pro/8734/ Another very good tool (though not strictly a hex/disk editor) is dmde (which is IMHO an exceptionally good "advanced" recovery software): http://softdm.com/ It does have "sector level" access: http://softdm.com/manual/diskeditor.html jaclaz

For NO apparent reason , and possibly of NO use whatever , a simple spreadsheet with common display resolutions and screen sizes (and consequent physical density in dpi). jaclaz Screens_dpi.zip

No . Meaning that at the "level" it is very unlikely that the disk firmware knows anything about "partitions" (as defined in the partition table in the MBR). I suspect that the "User partition" message you saw on the screen is not related to a partition like you are used to (software partition). To the disk firmware there are two partitions, Firmware partition and User partition, or, if you prefer, "Reserved Area" and "User accessible area". The partitions you make via software are inside the "User accessible area" or "User partition". I wouldn't give any relevance to the message (in the sense that it seem to me like UNrelated to the actual issue). Dynamic partitions are "tricky" . There are several ways how the user may have made them : simple volumes spanned volumes striped volumes mirrored volumes RAID-5 volumes once set aside simple volumes (and probably the first partition you found is of such a type) and mirrored volumes, all the other types are VERY complex to recover and very few softwares can deal with them properly. A tool known to be able to deal with those is File Scavenger (Commercial): http://www.quetek.com/RAID.htm Are actual sectors blank (00 filled)? If yes, there is nothing you can do . If no, there are maybe some possibilities . jaclaz

A possible explanation could be an attempt to reach another "Ballmer peak": http://xkcd.com/323/ and fail at it (again) . I presume it will pass to history as the "Sinofsky plunge" jaclaz

And there is not even a picture! here: jaclaz

I would gladly tell you, but the board word filters wouldn't allow it.... jaclaz

Naah, it doesn't work this way, you cannot write that someone is an id***, but you can allright say that he/she has taken idiotical decisions.... jaclaz

With all due respect , a rather pointless experiment. The idea is (was) to "clone" a drive where a bootable Win 9x OS was residing to another drive and have this latter boot that OS "as before". Copying a bunch of files to a ramdisk is - even if sudccessful - only a subset of the needed chores. As said, a lot of time have passed, so I cannot remember the details, but at the time the XCOPY approach already posted was used because no third party tools were needed and because the simple COPY did not work, AFAICR. jaclaz

I can understand the "advertising" mesage possibly conveyed by "joakim", but I am completely failing to see the one in "tiny" jaclaz

To further push my idea we could use the board word filters for "metro". Just like one cannot write a** or id*** or s*** , everyone should have "metro" substituted by either (through a random-generator): quite inappropriate interface remarkably inept interface utterly unfit interface undoubtedly infelicitous etc., etc. jaclaz

Can you also post how exactly you acquired the License for it and how much you payed for it? You may be unaware of this , but Windows discs/.iso's, etc. that you "download from the internet" are mostly WAREZ , and the policies on MSFN are rater strict on this theme, so be careful: http://www.msfn.org/board/index.php?app=forums&module=extras&section=boardrules Anyway, first thing welcome . Now, what would be the sense in your scenario for an unattended installation? Unattended means that you boot the PC to the disc/USB stick/Lan/device, then you walk away and after some time you come baclk and find the PC already configured exactly as you like. It's use (the real one) is limtied to a different scenario, where you need to have ALL the following needs: install/reinstall VERY often (several times a week) install/reinstall on DIFFERENT hardware It takes LOTS of time to build an UNattended disk, expecially supporting different hardware. If you install "seldom" and on the same single specific hardware you can use a plain attended install - possibly with a specific set of integrated drivers/updates. In your case the approach you have used tll now is IMHO the best one, you install attended, configure the system exactly as you want it, then image it and can re-deploy it in case of troubles, BTW this is the approach used normally when the needs (example corporate use) is: install/reinstall VERY often (several times a week) OR once only BUT install/reinstall on several specimens of same hardware So, you may be looking NOT for an UNattended installation disc/whatever, but rather for an updated/integrated/tweaked one, and then you can continue using your imaging approach after first install . jaclaz

Sure , first thing you need to find - WITHOUT installng Hyperdrive and HyperOS - the "My other computers", then it is simply a matter of having something you DID NOT install and DO NOT have, actually clone your drive : jaclaz

Yep , point being EXACTLY HOW MUCH hard? jaclaz

I'tll try to correct the spreadsheet/implement the "EXACT" formulas, thanks. Eh? Sorry, I'm not sure what you are asking here. The cyan coloured curve doesn't match what? My bad , I gave as acquired that the issue I had in linearorcurve.xls about re-creating the "family of curves" graph was clear. In the article the graph has 4 curves, and I only seem to find 3 of them (the 4th "cyan" one being "off by something"). It is possible that the graph was plotted with EP ON (whilst I only tried with EP OFF) . Now that I have more clear the "levels" I will try again and see if I get a senceful result . As always, I need some time to understand the implications of your post, at first sight I am confused but the references you make to the way the number is stored, whch to me seems like marginal/irrelevant, in my view: If a number is stored in "xy.16" it is multiplied by 65536. If a number is stored in "wz.8" it is multiplied by 256. This happens IMHO "outside" of the formula and in the "conversion/storing". And, given all the horrors implied or derived or caused by the implementation, I feel allowed to add that in this context where almost everything is either rounded or queerly converted or just plain wrong, if and when I get 0.99998 I would call it a "good enough" approximation of 1 . Apple and oranges (YES, they can be compared ): http://improbable.com/airchives/paperair/volume1/v1i3/air-1-3-apples.html jaclaz

Sure . The idea was (still is) that you save the event logs (if needed) then you delete them, then you cycle the machine looking for any new event, this way it is easier. Clearing the event logs is part (at least here) of "normal maintenance" of the system. On a windows 7 machine there are more logs than you would ever want , so often a batch is used: http://forums.cnet.com/7723-19411_102-378338/delete-all-event-logs-at-once-in-windows-7/ http://www.sevenforums.com/tutorials/25480-event-viewer-one-click-clear.html jaclaz

If you think a bit about it, it is EXACTLY the same issue. Comic Sans is not as bad as people like to depict it in itself, and it was actually IMHO a "perfect fit" for the Rover balloons (or more generally for comics ballons, as our (at least mine ) ancestors would say: nomen est omen http://en.wikipedia.org/wiki/List_of_Latin_phrases_(full)#N AS LONG AS Comic Sans is kept within the right context, not only it doesn't bother anyone, but it is also appropriate. Metro , AS LONG AS it remains confined within the boundaries of a small sized touchscreen (whilst still looking awful) it may (with some fantasy and good will ) be deemed appropriate, it is when you use it on a non-tiny-screened, non-touchscreen-thingy that it becomes a PITA (as well as if you are actually using the PC to do something). I would then propose to choose either the inappropriate adjective or any of it's synonyms, possibly adding to it some additional strength: http://www.merriam-webster.com/thesaurus/inappropriate Synonyms: amiss, graceless, improper, inapposite, inapt, incongruous, incorrect, indecorous, inept, infelicitous, malapropos, perverse, unapt, unbecoming, unfit, unhappy, unseemly, unsuitable, untoward, wrong and never actually refer to "Metro" (BTW, Italians should collectively sue MS for predating from their dictionary, an otherwise perfectly innocuous word, metro, that means "meter" will soon be inextricably associated with "bad taste" and "failure" ) , but rather to the "quite inappropriate interface of Windows 8", or "remarkably inept", or "utterly unfit", etc..... Personally I would choose "undoubtedly infelicitous". jaclaz

Wild guess , mind you , but maybe somethig is written in one of the events log. See if anything is found (you may want to clear the event logs and do a few boot/sleep/off cycles. jaclaz