jaclaz

Actually, it's not like a laptop CD/DVD drive works "wireless"! . Expecially since the CD has been replaced, it could well be the cable or a contact. BUT from what the OP describes I would rather suspect a "botched" Windows install, or, to be more exact two different players/codecs/whatever attempting to access the CD/DVD at the same time (and YES, I have seen this happening and NO, I haven't the faintest idea HOW it could happen - I suspect a "queer" combination of autorun+file association - but really cannot say, as the user in his simplicity wiped disk and reinstalled from scratch before there was the time to understand WHAT caused the issue) How much RAM has the PC? You can try using a RAMdisk only kind of Linux like DSL: http://www.damnsmalllinux.org/ that has such an option (though it supports audio cannot say if it supports video) or a more "full" RAM release such as Wolvix: http://wolvix.org/ that has a "copy2ram" "cheat code": http://wiki.wolvix.org/CheatCodes jaclaz

Someone called? As I see it we have a number of variables, most of which have UNKNOWN values. We don't know: if the USB support of the OS is working as it should if RPM can actually manage 1 Tb size disks if Swissknife supports 1 Tb disks if Diskman4 supports 1 Tb disks (and ANYWAY it is too difficult to use program for the end user) To which you add a (no offence whatever intended ) a non-expert user and the result of the equation CANNOT but become "a suffusion of yellow". At this point I would try (for free) the partition logic approach: http://partitionlogic.org.uk/ this way we remove any problem that might be caused by the Win9x + the USB support added to it. The alternative being parted magic. Instead of using the latter "directly" I would rather suggest the UBCD: http://www.ultimatebootcd.com/ which includes, besides parted magic, more tools, including the "SuperFdisk" (which I never used BTW) that could be yet another alternative tool. jaclaz

The same WHAT ? CLUF -> Contrat de Licence Utilisateur Final = EULA -> End User License Agreement http://fr.wikipedia.org/wiki/Licence_de_logiciel jaclaz

Sure, it is possible, but: it's not easy has nothing to do with WinSetupFromUSb (which this thread is about) You can: try the "automated" way (assuming we are still talking of XP): http://www.usboot.org/tiki-index.php post a new thread in the appropriate forum google a bit jaclaz

So does "stable". I think that everyone should try and learn, and if you do think you understand something more than another peep, instead of sporting your (assumed) superiority , you should try and help him. At 19 posts you are not in the condition (yet ) to be annoyed by posts of a newbie. Everyone has been a newbie (and still is in some fields) so let's not demoralize newcomers, OK? jaclaz

Well, try with "latest stable". The general idea is that a "beta" is an evolution of the "stable", reserved to people already familiar with the "stable". Or, if you prefer, "stable" is for "normal users", "beta" is for "beta testers" , a club which you can join allright , as soon as you get the hang of the program and become familiar with the procedures . jaclaz

Have you downloaded it? Have you READ the "readme.txt"? And the contents of the "\Docs\" directory? jaclaz

Please note how there is also an "iso master" which is Commercial (for Windows), and it has a home page allright http://www.littlesvr.ca/isomaster/ http://www.littlesvr.ca/isomaster/faq/ I hate to have to say this once again, but apart trivial modifications, editing .iso files (and expecially BOOTable .iso files) is NEVER a good idea. If anyone is interested in doing it the "right" way (i.e. recreating the .iso with mkisofs) here is some info and a batch that may be of help: http://www.boot-land.net/forums/index.php?showtopic=12406 Also please note how 7-zip can normally access the contents of a .iso and extract it's contents allright (without any need to mount it) and instead of a simple, only "Virtual CDROM driver" there is IMDISK: http://www.ltr-data.se/opencode.html http://www.boot-land.net/forums/index.php?showforum=59 that has many other uses besides virtual CD/DVD driver (ramdisk, virtual floppy driver, virtual partition driver) jaclaz

NO. That was a JFYI for dencorso. Diskman4 is well above the head of the average user. jaclaz ALREADY posted (on post #14) that an app to try was SwissKnife, which is GUI and more friendly: jaclaz

You first READ the read-me-first: Point #8 might interest you particularly. jaclaz

This is "normal". This should also be "normal". Unless I am mistaken, a standard 2K (or XP/2003) install from CD does: boots the CD (through BIOS) runs text mode part of the setup (which is done using still the BIOS "handles") which copies (or should copy) the relevant files to the HD. reboots the PC boots this time from the internal HD (the C:\$WIN_NT$.~BT folder) runs GUI mode part of the setup (which NEEDS the actual SATA drivers in the case of a SATA disk, least will produce the 0x0000007b) The only explanation at first sight is that somehow the USB drivers conflict with the SATA ones? Some questions: Which machine is it? (desktop/laptop) How much RAM? How big is the actual .iso? Have you not a setting in BIOS to set the SATA to "IDE compatibility mode" or something like that? jaclaz

Basic disambiguation. Backup or file based imaging is Filesystem Dependent. Cloning or sector based imaging is Filesystem Independent. first one is NOT "properly" an "imaging" solution. ANY actual "cloning" or "imaging" solution (sector based) will be able to image the actual sectors, NO MATTER the filesystem used. Obviously the "target" (i.e. where you store the image) needs to have a filesystem accessible by the actual imaging utility. Here is a list among which you can choose: http://www.msfn.org/board/index.php?showtopic=100299 jaclaz

The relevant part is this one (on the guide by CarterinCanada): http://www.mapleleafmountain.com/seagatebrick.html This non-issue is also detailed here: http://www.msfn.org/board/index.php?showtopic=128807&st=2999 jaclaz

Yep, usual mistake betweenLBA and numerals, my bad. Right are of course LBA 0 and LBA 6 or 1st and 7th. There is (AFAIK) NO relevant info about cluster size ANYWHERE but on those two sectors, , so, since as you know I am very cheap I would first try blanking just LBA 0, then LBA 0 and LBA 6, then LBA 0÷6 (and nothing more). http://mirror.href.com/thestarman/asm/mbr/MSWIN41.htm To really overdo it, you can wipe LBA 0÷8...., a neat "saving" of 23 sectors Edit: Before I forget, you may be interested in playing a bit with good ol'diskman: http://www.diskman.co.uk/ http://www.msfn.org/board/index.php?showtopic=100299&st=16 http://www.msfn.org/board/index.php?showtopic=141335 jaclaz

Yes, I do understand, but from experience, NOTHING is less read that the actual "read-me-first" or documentation for a program, and nothing is less searched for than the ALREADY available aswers on a board. Look at what I found in a 3 (three) minutes google search on MSFN: http://www.msfn.org/board/index.php?showtopic=142396 http://www.msfn.org/board/index.php?showtopic=142793 jaclaz

Please take your time reading Forum Guidelines (particularly #2a): http://www.msfn.org/board/index.php?app=forums&module=extras&section=boardrules Also, read the READ-ME-FIRST, particularly point #1: yours appears very like a non-target. You also, please read the READ-ME-FIRST, particularly point #1: yours appears very like a non-target. Please DO NOT POST on this thread ANYTHING that: is not 7200.11 related Even if 7200.11 related: is not LBA0 or BSY You can start a new thread here in the Forum: http://www.msfn.org/board/forum/169-hard-drive-and-removable-media-issues/ jaclaz

Well, you were wrong then! jaclaz

Naah, gasoline is too volatile , I was thinking more like napalm.... You know, like: http://www.imdb.com/title/tt0078788/quotes jaclaz

You don't actually *need* a Windows Server. You can use any windows with TFTP32 and a BINL server or Linux (and a BINL server) as "server". Start reading here: http://www.boot-land.net/forums/?showtopic=2322 AND given links in it, particularly: http://oss.netfarm.it/guides/ Also there is a very similar thread here: http://www.boot-land.net/forums/index.php?showtopic=12479 where you may find additional info jaclaz

Well, also, if anyone had followed my direct link to here: http://www.compuapps.com/index.php?option=com_content&view=article&id=112:swiss-knife-v322&catid=48:drive-managment&Itemid=193 he might have found that SwissKnife is tested for single partitions up to 500 Gb. So, for making three 460 Gb partitions it should be allright. Should anyone want to experiment, there is also this thingy, that I have tested with good results (but NOT with such a big partition ): http://partitionlogic.org.uk/ http://partitionlogic.org.uk/about/preview.html Why 32? (being that the bootsector is 1st sector and backup is 6th one?) jaclaz

It's one of your rights (to disagree) but in this case won't get you very far , you seem like missing the very basics of the way a XP is setup. In a nutshell when you install Windows, you boot from SETUPLDR.BIN that uses settings in TXTSETUP.SIF to "load" drivers and install them, by copying them to the \drivers\ folder AND create a .pnf AND write in the Registry the needed. So what nlite does is simply to modify the TXTSETUP.SIF to take into account the "new" drivers. The alternative being using the "F6 floppy" to add the drivers during install (which simply "adds" some settings to TXTSETUP.SIF and of course provides the actual driver files). When you boot an installed windows, you boot from NTLDR, that knows NOTHING about TXTSETUP.SIF so you CANNOT add drivers after install in the same way (well, you can, of course, add them once booted, but since without the SATA Mass Storage drivers you cannot boot, you are in a nice CATCH 22 situation). The "traditional" way to migrate an XP was to set the Mass Storage drivers to the "standard" "Dual PCI Ide" drivers because they are "universal" in the sense that they work both with actual IDE devices and with SATA devices as long as you choose "IDE compatibility" or a similar setting in the computer BIOS. (typically all desktops have this possibility as well as most laptops, but a number of the latter do miss this possibility). The whole idea of Offline Sysprep is to: access Offline a working install (booting ANOTHER OS instance) make it hardware independent (so that it can be transferred and boot on different hardware) The Mass Storage driver injection ONLY injects Mass Storage drivers , so if any other "critical" driver in the offline image is "incompatible" with the new "target" hardware, it won't boot . jaclaz

I would assume that: the two weeks starting on 08 December 2008 has elapsed in the meantime, thus I would guess that your kind offer is a bit too late. jaclaz

Just for the record, there is an updated version: http://www.ayera.com/teraterm/ And the Sourceforge continuation of "old" 2.3: http://en.sourceforge.jp/projects/ttssh2/releases/ now version 4.67 jaclaz

I wonder which kind of contributor are you? On your first post you start criticizing the way another member replies to a question on nlite, and on the second one you post a question on the use of nlite - without having taken the time to read the basic instructions.... nlite was written to be run under 2K/XP and tested under 2K/XP, and it works allright under 2K and XP. (you might want to notice how the last character in the above sentence is a dot, full stop or period) The only ways out AFAIK/IMHO are: run nlite in the OS it was developed and tested on re-write nlite from scratch adding to it compatibility with Windows Vista , Windows 7 and Server 2008 (and what not) sue nuhi for not having updated his program or having forecasted it would not work under an unreleased at the time OS sue Microsoft for having released an OS that broke compatibility with nlite of which #1 is the most viable, since you must have a full XP source (in order to nlite it) just get a Freely available Virtual Machine, like Virtual PC or Qemu or Virtualbox, install the XP on it, then run nlite inside the VM. jaclaz

Yep, I guess there must be a misunderstanding of some kind. The ORIGINAL wording was: And it seemed to me (and to a conspicuous amount of users) understandable and clear enough. Snakebyte2 said it wasn't clear enough and according to his requests/suggestions the text was modified as follows: As you can see, there is not that much of a difference, except the fact that the SAME info is repeated THREE times (and formatted/coloured more incisively) instead of TWO , and in my perverted mind just ONE should have been enough, just for the record this was the ORIGINAL-ORIGINAL text (never published): In any case, the 3 (three) golden rules of serial communication : GROUND EVERYTHING together check that GROUNDing together ALL equipment involved has been done while considering the reasons why and the consequence of the above two, check AGAIN that everything is effectively GROUNDed together jaclaz