jaclaz

Topic pinned. jaclaz

BTW, and JFYI a pretty much interesting new approach to install XP from .iso on USB device has been developed (and is in an advanced testing phase): and: http://sites.google.com/site/rmprepusb/tutorials/install-xp-from-an-iso the "advantage" (if any) is that with this approach you can have a "vanilla" (or plainly slipstreamed to SP1, 2 or 3) XP .iso and have as many "F6 floppy" images as the different AHCI/SATA you need to install. From time to time it happens that someone posts about a company policy (or whatever) that seemingly does not allow a "modified .iso" and of course Commercial use of nlite is NOT allowed. The method of course need the setup to be attended. Many laptops do not have an option to set the internal SATA to "IDE emulation" mode, if those can, you can always post-install the SATA driver, an example is given here: jaclaz

With all due respect to everyone , "proof of a guess": I am sure that often this is part of or the whole issue , but "proof" has another meaning. :cheers: Wonko

Well, no. This is not "just to be safe", it is "unneededly" or "just for the fun of it", meaning that there is no - as you have been told by Ponch - known connection between the label (volume name or volume id) and bootability of the CD. There are quite a number of info on an original XP .iso or CD. If you run isoinfo -d on the actual original .iso (utility that is part of cdrecord tools, like mkisofs), you may get something similar to: CD-ROM is in ISO 9660 format System id: Volume id: WXPFPP_IT Volume set id: WXPFPP_IT Publisher id: MICROSOFT CORPORATION Data preparer id: MICROSOFT CORPORATION, ONE MICROSOFT WAY, REDMOND WA 98052, (425) 882-8080 Application id: CDIMAGE 2.46 (10/12/2000 TM) Copyright File id: Abstract File id: Bibliographic File id: Volume set size is: 1 Volume set seqence number is: 1 Logical block size is: 2048 Volume size is: 261167 NO Joliet present NO Rock Ridge present The Volume id or Volume set id, as well a Data preparer id and Applicaiton id are NOT connected in ANY way with booting. jaclaz

Not at all "stupid", simply you panicked (and didn't follow the advice given in the read-me-first #14 ): I guess I can count you as another happy bunny in the basket : jaclaz

Which is fundamentally this one: with a nice spin-off/addition detailing the use of a multiple-driver F6 floppy for adding the AHCI drivers The "making of" is here: http://reboot.pro/13912/ jaclaz

Of course NOT , all the work that was done to make it possible was in order to have people have a LESS convenient way to install their XP. Approximated average(1) CD read throughput: 6 Mb/s Approximated average(1) USB 1.1 device read throughput: 1 Mb/s <- not a wise idea to choose USB install if you have USB 1.1 only controllers on the motherboard Approximated average(1) USB 2.0 memory stick read throughput: 12 Mb/s Approximated average(1) USB 2.0 HD throughput: 24 Mb/s In the future (or if you are a rich guy and can afford it now): Approximated average(1) USB 3.0 device read throughput: 60 Mb/s? Draw your own conclusions. Note(1): "Approximated average speed" calculated using "common sense" and not at all representative of the actual results you may have on any particular combination of hardware, data meant only as a comparative, simplified example jaclaz

Describe EXACTLY WHAT you have done like commands issued, Operating System you were using (if I get it right that you formatted form an OS) or describe EXACTLY what you have done and the EXACT error messages/whatever you got. No matter how desperate you are, it's pretty much binary, either it is possible or it is not (sorry ) it depends on what you did EXACTLY. Review this: http://homepages.tesco.net/J.deBoynePollard/FGA/problem-report-standard-litany.html NO. jaclaz

I can get to the page allright: http://www.anthologymarketing.com/microsoft/deployment/virtualization_cert/virtcert_landingpage_r02.html http://www.anthologymarketing.com/microsoft/deployment/virtualization_cert/virtcert_landingpage_r02.html from Italy. The reason must be something else. Forget the above, I see, I too land to: http://www.prometric.com/error.htm http://www.prometric.com/error.htm when clicking "Register", instead of: http://www.prometric.com/Microsoft/virtualization http://www.prometric.com/Microsoft/virtualization There is a page I can get to here: http://www.prometric.com/Microsoft/default.htm http://www.prometric.com/Microsoft/default.htm But I seem like not finding anything connected to "virtualization". jaclaz

http://www.legroom.net/ It seemingly happened again. Everything is cool again, now: http://www.legroom.net/software/uniextract Installer: http://www.legroom.net/scripts/download.php?file=uniextract161 Binaries/Portable (No installer) http://www.legroom.net/scripts/download.php?file=uniextract161_noinst jaclaz

Look, that auto-built thingy you posted a photo of is a RS-232 to TTL adapter. WHAT you connect it to? As in EITHER: a RS-232 (COM port) interface physically soldered to your PC's motherboard a USB to RS-232 cable adapter/coverter You may understand that: OS->COM driver (ALREADY on your system)->COM (RS-232) port->your converter->TTL OS->USB generic drivers (ALREADY on your system)->specific USB to RS-232 converter cable driver->COM driver (ALREADY on your system)->Virtual COM (RS-232) port->your converter->TTL in the first case you need NO particular driver installed, in the second case, you need one. You READ how to do it? OK, my bad, I gave you a reference to #6 while it was #8 (corrected previous post), but finding it shouldn't have been that difficult , and you should know the read-me-first by heart, by now. jaclaz

A Server 2003 install source did have a \I386\ folder last time I checked one. You are not looking to an installed system (as opposed to the install media CD or a copy of it's contents) right? jaclaz

But to WHAT is it connected? If to a serial port on your mainboard, you need NOT any driver but the standard Windows ones. You can (and should) performa loopback test to the actual serial port, before. Check links in point #6 #8 of the read-me-first: jaclaz

It is peculiar. A "normal" XP install disk has an "XP" bootsector that loads SETUPLDR.BIN in \I386\. <- this is hardcoded and cannot be longer than four characters. Yours uses evidently a "Vista" or 7 bootsector that loads BOOTMGR in ROOT of the CD. There may be several other ways to make a bootable CD out of it, like using grub4dos or isolinux or BCDW as "bootmanagers" and leave BOOTMGR the role of OS loader. jaclaz

You created an "outline structure". Simply select the whole sheet (top left "square" beween "1" and "A") and "promote" or "ungroup" everything until you have no more a structure. Data->Group Outline http://www.wikihow.com/Group-and-Outline-Excel-Data http://office.microsoft.com/en-us/excel-help/remove-an-outline-HP005202031.aspx jaclaz

Yep, it should be it. JFYI, Uniextract extracts it allright. And it runs on XP 32 bit from the extracted folder. jaclaz

My exact same suspicion, but it is a "long standing" topic, since December 2009 and accessing it as: http://www.msfn.org/board/index.php?showtopic=140247 should always work (and it DID NOT ). Another suspect may be the presence of forward slashes in the title, currently working (stoopid friendly name) link is: http://www.msfn.org/board/topic/140247-trace-windows-7-bootshutdownhibernatestandbyresume-issues/ the actual title being: Trace Windows 7 boot/shutdown/hibernate/standby/resume issues which means that the board software doesn't particularly like forward slashes Or maybe the combination of BOTH dashes(please read as spaces) and forward slashes? jaclaz

What the ....! It did exist , here is a google cache of it: http://webcache.googleusercontent.com/search?q=cache:G3x0j3P_lGwJ:www.msfn.org/board/topic/140247-trace-windows-7-bootshutdownhibernatestandbyresume-issues/page__st__320+site:msfn.org+xbootmgr+msfn&cd=5 jaclaz

Hmmm. There are IMHO two basic misunderstandings: You use either makeisofs or cdimage.exe (if you are from MS) or oscdimg.exe and NOT Nero to create the .iso If you really want to use Nero to create the .iso, you will need to study it a bit, it does allow for all three El-Torito standards: Floppy emulation (the one that you probably are using), No-emulation (the one that you should use), and hard-disk emulation (VERY rarely used) Now, how to create an XP/2003 install .iso with mkisofs is on a good half of the internet, (the other half containing info about using cdimage.exe or oscdimg.exe). Info on how to create such a .iso with Nero is also available, but hard to find, and probably not exact to the version you are using. In any case from what you posted your source is - to say the least - "queer" as it looks like using the Vista or 7 based BOOTMGR and it's \boot\ folder (most probably containing a BCD store). So you will need anyway to study quite a bit to be able to replicate that bootable .iso approach. Choose a path, but choose wisely. http://www.imdb.com/title/tt0097576/quotes?qt0357926 jaclaz

There is NO way you can "fix" the actual drive. (NOT a DYI kind of job, unfortunately ) The most you can do, when it happens to actually load "properly" is to make a "forensic like" image of the disk, a suitable app is this one: http://www.datarescue.com/photorescue/v3/drdd.htm How many disk do you have? How is the "problematic" disk connected? You will need also: another hard disk with enough space to contain the WHOLE size of the "problematic disk" (i.e. if it is a 500 Gb disk, you need a 640 Gb one to host the 500 Gb sized image) possibly an USB or firewire adapter to connect the "problematic" disk should direct connection to motherboard prove to create problems. Once and if, in one pass or in several partial attempts, you will have managed to have the image, you can try using programs like TESTDISK and PHOTOREC: http://www.cgsecurity.org/wiki/TestDisk or, actually adviced in this case, DMDE: http://softdm.com/ to attempt to recover the partition(s) or, should this attempt fail, the actual files. If you don't succeed in creating the image (due to any reason) your ONLY hope is to find a professional disk/data recovery service, and they aren't cheap . jaclaz

Link #1 and #3 are OK. Link #2 is "a suffusion of yellow" : http://www.thateden.co.uk/dirk/ NO idea what it is meant for. Adapter in link #1 has been reported as working allright : Please note how the link #3, ALSO allright is the actual "shifter" originally used, which has a dedicated note in point #11 of the read-me-first: (which you obvioulsy failed to READ FIRST ) NOW, would be nice if you read it, particularly point #10 and #11. jaclaz

You should rather appreciate that you have a clicking drive (that is NOT a BSY or a LBA0 problem) and the thread you posted to is ONLY about BSY and LBA0 issues, like: Long answer: start a NEW thread (aptly titled) for your problem, the present thread is for OTHER problems ONLY. Short answer: you have a failing drive, buy a new one. Corollary to the short answer: there is NOTHING you can do about it (and fixing it by a professional will cost WAY more than buying a new one), just backup it's contents (if you can access them) then throw it away. jaclaz

While we are being pedantic, you might rephrase this pleonasme. Sure , you are very right please read it as either: or: I may venture in a : jaclaz

It's not stupid by itself, it is simply illogical asking it here, on page #177 of a thread illustrating a rather complex method to solve the problem. See here: READ BOTH the read-me-first AND the FGA's FIRST (they are there to hopefully avoid having the SAME questions asked again and again): That would be FGA #1 (and yes it is the first frequently given answer because it is a VERY frequently asked question). Unless of course you think we are a bunch of sadists that like to suggest complex methods when simply swapping a PCB would do. jaclaz

Aerostudio has a dedicated Forum here: http://reboot.pro/forum/72/ jaclaz