jaclaz

Sure, and that is ANOTHER topic. You are (were) mixing things without referencing to the OTHER thread. It is only logic that ilko_t - even without clearly making reference to it - talks here of the way WinSetupFromUSB uses, since anyway it was explicitly cited in the OP. jaclaz

2006 evidence (just for the record): http://www.wilderssecurity.com/showthread.php?t=136401 @NoelC Maybe a goat : http://www.msfn.org/board/topic/170954-windows-82/?p=1067620 jaclaz

Charlotte, did you actually READ my reply? For the record (and of course) there is no need (at least in 7-zip) to rename the file changing it's extension, you open 7-zip and from it you open a CAB .in_ file normally. jaclaz

But it usually helps. Flasche, try explaining what the problem is, i.e. what is the actual Goal that you want to achieve. The risk of slipping on a chocolate covered banana is high http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/put-down-the-chocolate-covered-banana.html Start with a basic standard litany: http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/problem-report-standard-litany.html jaclaz

Who/what is "it"? The one telling you to extract SYSOC.IN_, I mean. SYSOC.IN_ expands to SYSOC.INF (which is a plain text file in the .INF format, not a .TXT file) In any case SYSOC.INF is related to SYStem Optional Components (like WordPad, Fax services, COM+, etc.). The file you are interested in is likely NTPRINT.IN_/NTPRINT.INF, which contains: and - consequently - SPJX9600.GPD and JX9660PS.PPD. But these are NOT only actual files , they are sections in the .inf: and the files are not in the \I386\ directory of the CD, but inside the \I386\Drivers.cab. The files listed in the two data sections are also needed: But what is the "actual GOAL"? I mean what do you need those drivers for? jaclaz

@submix8c Which menu.lst? There is not one in post #6 in that thread, which however can be referenced as: http://www.msfn.org/board/topic/170809-multiple-windows-7-versions-on-same-iso-unattended-product-key/?p=1065445 Maybe (please read as "undoubtedly") you are putting together (mixing them) different methods. Ilko_t was making reference to WinSetupFromUSB (and WITHOUT specifying it, to it's latest version(s)), whilst in the other thread you are talking of various methods/ways by Steve6375- I would presume that the Author of WinSetupfromUSB has a (vague) idea how the tool he himself wrote works. I would say that FAQ#11 is related: http://www.winsetupfromusb.com/faq/ jaclaz

Maybe useful, maybe not, something now lost in the midst of time, Letter Assigner: http://www.msfn.org/board/topic/118623-how-to-create-easily-a-second-win98xp-in-the-same-computer/?p=826574 jaclaz

Sorry to say so, but 120,000 bucks are "peanuts". The issue here is IMHO much different, see: http://www.msfn.org/board/topic/155290-windows-8-deeper-impressions/page-199#entry1066170 jaclaz

I will re-state how I run an install of NT 4.00 since more than 10 (ten) years 24/7 and the reboots are made only for maintenance purposes, probably less than 4 per year. The only issue I had, and that somehow was solved (though I cannot really say how exactly) some years ago by tweaking some registry entry was a "strange" accumulation of mouse movements (the machine actually runs almost exclusively a "DOS" program, in which interaction is through the keyboard only) which made after several months the mouse unresponsive. Of course NT has less services than XP running (and most probably I actually disabled what I do not need), but still the "reboot once a day is needed" is way more than needed IMHO. Apart that machine, my "everyday use" PC is also not switched off/rebooted often, i.e at stretches comparable with the 60 days or so, but I did never notice such a degradation in performance. jaclaz

Yep , what I was wondering is if this is the "normal" status for an install made from a DVD bought in a shop (or - if it is not - whether the DVD is/was a "fake" of some kind and OP was tricked into buying it ). jaclaz

Remaining Windows rearm count 1000 (one thousand)? Is this "normal"? Volume_MAK channel? jaclaz

Well, you have anyway a 50% probability : http://en.wikipedia.org/wiki/Flipism More seriously, matters are much more complex than that. Among all the PC's existing, the DELL's (and particularly their BIOSes) have been traditionally a PITA, it is perfectly possible that it is that particular machine's BIOS that behaves like that (i.e. that same disk connected on another PC shows 0 size instead of unknown) But it is also well possible that your disk suffers from an altogether different kind of issue. Before going on, I would try on another machine and/or have a look at the drive from either Victoria or hdat2, or if you have a Linux distro available, check it with hdparm it is possibly not the case,/it is unconnected but, example: http://forum.hddguru.com/viewtopic.php?t=11040&start=175 hdparm can see a LBA0 drive as having 0 sectors (LBAsects=0) but it will in the end say it is "unknown". See also this (and a few posts starting from here): http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/?p=994801 jaclaz

epic, maybe you are taking tomasz86's reply the "wrong way", before accusing someone of trolling, you may want to take a couple deep breaths or making a good walk outside and cool down a bit . Historically Opera was Shareware/Ad supported, *always* had a "mobile" version (besides a "vertical" OEM one) and became free when they started presumably selling the "mobile" versions. The "switch" happened in the second half of September 2005: 17/09/2005 https://web.archive.org/web/20050917195451/http://www.opera.com/buy/ 23/09/2005: https://web.archive.org/web/20051001081407/http://www.opera.com/buy/ https://web.archive.org/web/20051001085048/http://www.opera.com/free/ Of course the targeted devices for the Mobile versions were what was available at the time, Symbian, Windows Mobile, etc. But, if there was something similar to a tablet, it was the ARCHOS WiFi-enabled Pocket Media Assistant PMA400 which was in the "Home media" section: https://web.archive.org/web/20051001043503/http://opera.com/products/homemedia/ https://web.archive.org/web/20050824131806/http://www.opera.com/pressreleases/en/2005/01/11/ So, whatever caused the (BTW wrong) decision to ditch the Presto engine in favour of the (stupid) Chromium, it doesn't not seemingly come from people that are willing to enter the tablet market for the first time, as they are among the ones that were there before anyone else. jaclaz

zjxls, WHAT did you buy in a retail store? Like: A windows 8 install DVD <- if this is the case post what is actually written n the physical DVD A computer with Windows 8 pre-installed on it <- if this is the case post the EXACT make/model of the computer Something else <- post as much details as you can about this "something else"The "test mode", means that you are running in "test mode" . This could be connected with a BCD setting and the use (or used just once and not reset) of unsigned drivers: http://answers.microsoft.com/en-us/windows/forum/windows_8-windows_install/windows-8-pro-shows-test-mode-build-9200-above-the/60468fe9-07db-42ab-bde4-b11f6ba0f029 jaclaz

And the kickstarter campaign appears as a bad failure. https://www.kickstarter.com/projects/thorium/thorium-core-cloud-desktop jaclaz

If I may, not only that, to that you have to add that it is HP, I mean it is not like an unknown laptop maker from Taiwan, it is one of the main MS OEM (just like DELL, which has traditionally carried the flag of PITA for doing things unlike any standard, creating more incompatibiites that I can recall), in theory such a "close friend" should have made tests for all MS hardware. Seriously, it is possible that it is an "inner MS" conflict of sorts, like the good guys including the PID/VID of the specific hardware under the "Generic adapter" without actually testing that the generic driver is compatible with the actual hardware. I would try having a look a the .inf files of both the "Generic" and "MS specific", it is possible that the mechanism used by the stupid Windows is that of "trusting" more the MS "internal to the OS" driver if the same device ID is on it than a (still MS) "external" driver, or maybe the actual date (or version) of the "specific" is older than the "generic". If the ID in the "generic driver" .inf is related to a single instance, removing it from the inf should work and have no consequences. The issue may be if the "generic driver" is associated with a wider set of devices, but still if you don't plan to use other bluetooth adapters, removing the "whole" set may do as well. jaclaz

Guys, go and sign the petition (if you haven't already): http://www.msfn.org/board/topic/105936-last-versions-of-software-for-windows-98se/?p=1067020 https://www.change.org/petitions/opera-software-open-sources-of-presto-engine jaclaz

Well, no . One should ignore him every other day . jaclaz

That switch, just for the record, is documented here (for Windows 95): http://www.tiplord.com/ http://www.tiplord.com/customizing/MSDOSSYS.HTM (which has a few nice tips/docs/whatevr about 9x) And (about hex editing to do other things): http://www.msfn.org/board/topic/118073-disable-f8-win98-boot-disk-startup-menu/ http://reboot.pro/topic/4754-disable-the-f8-startup-menu-on-win98-boot-disk/ jaclaz

ddrescue is likely already there, or if not, read here: https://help.ubuntu.com/community/DataRecovery Sometimes the good Linux guys have a peculiar way to make things more complex by misnaning or confusing things by giving to different things the same name, etc. or - some other times - by giving so many options to do something that it makes reaching the goal more difficult. The above page has a link to another page where 5 or 6 different methods to install ddrescue (which is astutely called gddrescue as package, whilst the ddrescue package actually delivers dd_rescue ) but the easiest would be to use apt-get as in: http://www.forensicswiki.org/wiki/Ddrescue http://www.forensicswiki.org/wiki/Ddrescue#Debian_and_Ubuntu sudo apt-get install gddrescuejaclaz

Ubuntu is one (among many) available Linux distributions. Unlike what happens in the MS world, Linux is Open Source and (largely free as in free beer, besides being free as in freedom). Basically everyone can "assemble" a Linux distribution (or "distro") which may be "universal" or "very specific" (either in the sense of running only on a given hardware or of being "focused" on a specific subset of computing tasks). In practice there are only a couple handfuls of "main" distro's, and Ubuntu is one of them. There are more "flavours" or "spin-offs" or "remixes" of Ubuntu as stars in the sky (plus the infinite number of other distro's), it is very confusing for a new user. Ubuntu is a "fully featured distro" (please read, though I will be soon flamed for this , as "a nice but senselessly huge amount of of bloatware, a large part of which being bells and whistle") for your uses smaller/simpler distro's will probably be more suited. You want a "Live CD" distro, i.e. something that is not installed anywhere but that runs directly from a CD or USB stick. Possible candidates: http://www.sysresccd.org/SystemRescueCd_Homepage (still largish) http://puppylinux.org/ (as small as it can be) http://trinityhome.org/ (what I would probably use if I were you) This article should be of use: http://techmuck.blogspot.it/2012/03/data-recovery-with-gnu-ddrescue.html as well as this thread: http://www.murga-linux.com/puppy/viewtopic.php?t=71026 I think you will need anyway some assistance from a friend a bit more familiar than you with the Linux environment, as a few "naming" conventions" and commands are different from DOS or more generally Windows command prompt. There is nothing overly complex in the use of such tools, but there is a concrete risks for the newbie (no offence whatever intended ) to "confuse" disks/drives/devices, with consequent potentially catastrophic resuts. In any case ideally you should first try the procedure with another (working) possibly smallish hard disk (or a USB stick), just to get the hang of it. The mentioned: http://www.pendrivelinux.com/linux-live-usb-creator/#more-3034 should do if you wish to use a USB stick (instead of "burned" CD), check if the distro you choose is supported by the tool, most are. About temperatures, the rule of the thumb is that if it's "warm" i.e. you can hold your hand touching it's cover more than a few seconds and feel it "warm" (i.e. it is around 40° Celsius or less) it is fine, if you feel it "like hot" (i.e. it is around 50° Celsius) is still within the norm, if it feels "very hot", it is "very hot" and probably needs some added ventilation/cooling. The general idea is to copy as much data as possible to a new disk (or disk image). If you make an image of a perfectly working disk (or a "clone" of the disk on another one) the result will be identical to the source. When a "failing" or "partially failed" disk is the source the result will be "similar", i.e. it will be identical for corresponding "good sectors" and will have "holes" for the bad ones (actually sectors containing 00's). The image (or clone) being on a fully working hard disk allows to performa actions that would be impossible to do on the failing/partially failed disk, such as filesystem reconstruction and/or file recovery. In theory, one should make a second image (from the first one) and attempt recovery on this last one, as this allows to attempt different techniques (including some that while recovering something make something else unrecoverable) as a "way back" is available any time. But it depends on the amount of data that the ddrescue actually manages to copy and from a number of other factors (if only a small part of the disk is imaged without errors or if anyway "key parts" of the filesystem are still missing there is no sense in attempting filesystem recovery and all you can do is attempt file based recovery which is read only, so this second image is not needed). jaclaz

Oh, my. READ (now for the 6th or 7th time, I lost the count) point #5 of the READ-ME-FIRST: http://www.msfn.org/board/topic/143880-seagate-barracuda-720011-read-me-first/ and/or see if these slightly differently worded posts (to the same effects) are clearer: http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page-119#entry930329 http://www.msfn.org/board/topic/158397-invalid-partition-table-on-my-500gb-hdd/?p=1012499 Compare with flippism: http://en.wikipedia.org/wiki/Flipism and with "is it safe"? http://www.imdb.com/title/tt0074860/quotes?item=qt0247572 jaclaz

Logical error detected. IF it was a "new frontier", you could not ask how it can be done, as noone would have already done it. As a matter of fact WINNT.EXE (which is the installer from DOS) is one of the least used file for installation of Windows XP, while it was common enough in the (good ol') NT 4.00 days, I would dare to say that noone ever used it since year 2001 (initial release of XP) if not in very particular occasions, like: http://www.911cd.net/forums/index.php?showtopic=16713 and even then, more than 7 (seven) years ago, those who used it can be counted on fingers without taking one's shoes off, as soon "better" methods were developed: http://www.msfn.org/board/forum/157-install-windows-from-usb/ Definitely you are barking up the wrong tree hexediting the wrong file. Cannot say if it helps you, but I would guess that the *overall* colouring choice of the text mode setup is not entirely different from the way BSOD's are coloured: http://blogs.technet.com/b/markrussinovich/archive/2010/12/14/3374820.aspx jaclaz

How? I thought that Fonts to be available in CMD console need to have a given set of attributes : http://www.msfn.org/board/topic/141893-fonts-in-console-window/ jaclaz

The xolution to that broblem may require you to READ AGAIN (for the fourth or fifth time, unless I am mistaken) the given resources. jaclaz