jaclaz

Unless of course you specify that you are using the Word 20xx and it's integrated word correction.... http://www.blameitonthevoices.com/2008/08/...ction-fail.html Or the nice and very useful =rand(p,l) or =rand.old(p,l) function: http://www.techtalkz.com/technical-discuss...easter-egg.html http://support.microsoft.com/kb/212251/en-us I wonder if it could be hacked somehow to produce some real random text. There are rumours that there are cats that can even fool pawsense: http://bitboost.com/pawsense/ (which your e-mail might not ) Here is an actual picture of one: jaclaz

This happens on XP as well, as long as you have NOT ACPI. See this, JFYI: http://www.boot-land.net/forums/index.php?showtopic=3717 http://www.boot-land.net/forums/index.php?...=3717&st=26 jaclaz

Start from here: http://www.msfn.org/board/index.php?showtopic=133309 jaclaz

And, for the record, Opera: http://www.boot-land.net/forums/index.php?showtopic=7934 jaclaz

@fdv Though I am not an English mother tongue, and thus may be not "qualified" to do do, I have to disagree. You cannot take single sentences out of the context. The word substitution IMHO does not hold. Let's read again: I assume as a truism that the scope of a software is to be executed. Thus this is an implied right, to which however the License imposes explicitly no limits/restrictions and that is NOT covered as an "activity" protected by the license. In other words the executing of the software is a right given but not necessarily an activity protected. jaclaz

Batteries are NOT "all-the-same". Different kind of batteries may require different procedures to attempt recovering (if possible at all) some lost capacity. Here is a site where some good info is given: http://www.batteryuniversity.com/ If it's a Li_Ion battery, the freezing WON'T work (and it is possibly DANGEROUS). Read comments here: http://lifehacker.com/software/batteries/r...ezer-308225.php And directly from the given site: jaclaz

A semi-random question/thought. Is the good ol' CDmage: http://www.softpedia.com/get/CD-DVD-Tools/...s/CD-Mage.shtml compatible with DVD's? It offers as well a LBA mappng facility and it's Freeware. jaclaz

You need to apply a number format to the field in the Word document, not to the source in the Excel sheet. The code is awkward, I would need to check if you cannot find it yourself, but it does work, it is similar to the "personalized" number format codes used in Excel, but obviously it's not the same. Richt click on the field, select Modify, then see if you can change the format directly or if you need to press the "Advanced Field Code" (or similar) button and add the format after a backslash. jaclaz

Hmm, that seems to me more like a question than a statement. Let us reason the other way round, for one moment. Let us imagine that they were actually responsible, and that there is no way to recover them, not even through the services of a recovery specialist. How much should they be valued? US $1.00 per byte, per kbyte, per Mbyte or per Gbyte? Would the only existing photo of a relative of yours that is alas no more with us be valued the same as a crappy poem you wrote under the effect of one too much glass of (name your preferred alcoholic beverage)? Or the same as a song you downloaded from I-tunes? How will you prove (or even make a summary listing of) which kind of data you had on the HD before the irrecoverable failure? (an ideal way would be to produce a working backup/clone of the whole drive ) Think at how Airline companies are obliged to re-pay you for lost/destroyed baggages. Here is a reference: http://www.yourcreditnetwork.com/blog/HowD...hAnAirline.aspx So, HD manufacturers could well make an insurance for the event of losing data. It will have a max imdemnizable amount, say $ 1,500.00 or $ 3,000.00. This insurance will have a time duration, say 12 or 24 months. You (not the company making the thingy) will pay the insurance when you buy a HD, as it's price will raise accordingly. How much this price would increase? Hard to say, but probably in a range between $ 15 (max $1,500 - 12 months) and $ 50 (max $ 3,000 - 24 months). And of course you would need to buy a new HD every 12 to 24 months. jaclaz

It is possible that is related not to NTFS, but to the NTFS bootsector of Vista (as opposed to the 2k/XP/2003 NTFS bootsector) Try formatting NTFS, then run on the volume bootsect.exe /NT52, then try again running grubnst.exe, jaclaz

@zZolaa It seems to me like the right occasion to test the new kid on the block on a 64 Gb: RMPREPUSB: http://www.boot-land.net/forums/index.php?showtopic=7739 The alternative being installing a filter driver and using normal Disk Management. Or, under Vista, using diskpart. jaclaz

Reading the nLite's License in the part where it allows only personal use? jaclaz

You are not the only one, they were removed from the hosting server or timed out. However, you missed reading just five posts before yours, some images were re-uploaded, and there is a complete guide (with images): http://www.msfn.org/board/index.php?showto...807&st=1295 Please avoid quoting entire, lengty posts, it only makes the thread harder to read. jaclaz

The photos have been re-posted. Here are the links to them (in the order they were on the guide): http://www.msfn.org/board/index.php?act=at...st&id=25717 http://www.msfn.org/board/index.php?act=at...st&id=25716 http://www.msfn.org/board/index.php?act=at...st&id=25718 http://www.msfn.org/board/index.php?act=at...st&id=25722 However, there is a "comprehensive" tutorial with good images and details, link here: http://www.msfn.org/board/index.php?showtopic=133387 jaclaz

Sure, both were made from info on this thread. FYI: http://www.msfn.org/board/index.php?showto...807&st=1232 http://www.msfn.org/board/index.php?showto...807&st=1247 http://www.msfn.org/board/index.php?showtopic=133387 @robintay If loopback is OK, and you are positive about Hyperterminal (or Putty, or whatever) settings, 38400-N-8-1-N: http://www.msfn.org/board/index.php?act=at...st&id=25722 I am afraid there is a possibility that the PCB is "fried". Cannot really say what else you could try. Maybe, but maybe means maybe, doing the "short circuit" trick, but it's risky, and should be used as a last chance only. However AFAIK it only applies if you have a locked state board, not in a situation like the one you describe: http://forum.hddguru.com/tutorial-resolve-...-t11040-40.html (post by johnmar) and here: http://www.msfn.org/board/index.php?showtopic=129551 jaclaz

You where right, it was not complex at all. Look, don't want to seem grumpy, I am usually not , but you cannot jump from one method based on a USB stick to one based on a Cd and back. Several thousands or maybe tens of thousands of people have succeeded in using WinsetupfromUSB. It requires KEEPING the "Manual Install and Upgrade for removal". The few tens of people that had problems with WinsetupfromUSB have read it's thread: http://www.msfn.org/board/index.php?showtopic=120444 and if there were not able to solve the problem by themselves, posted in there, and ilko_t or myself found what the problem was and solved it. It is very probable that your same problem happened and was already solved. Try browsing the thread, you will see what the normal troubleshooting steps are and if you cannot still find what the problem is do post there with the usual things: description of the hardware list of exact steps taken detailed description of what happens LOG from WinsetupfromUSB jaclaz

Did you try a loop-back test, before attaching the HD? See here: http://www.msfn.org/board/index.php?showto...8807&st=384 http://www.msfn.org/board/index.php?showto...807&st=1194 jaclaz

Since you asked for it... ... you are wrong. It does make a difference when a drive is booted from USB or from "internal IDE". And, ...you are wrong , an external optical drive is NOT a readonly memory stick, a memory stick is normally a HD-like device, with a MBR and partition(s) - it starts booting from it's first sector (512 bytrs). An external optical drive is a CD-like device, has a CDFS and starts booting from sector 17 (and sectors are 2048 bytes). An external optical drive is a CD-like device and is equivalent to the CD part of a U3 memory stick (a stick that "shows" as two devices, a CD-like one and a HD-like one) Basically: IDE (read ATA/ATAPI) has been around for some 20 years. From the beginning both HD-like devices and CD-ROM devices were developed on this bus. Notwithstanding that, a number of BIOS was NOT coded to be able to boot from an internal IDE CD-Rom, and workarounds like BCDL, see this: http://www.911cd.net/forums//index.php?showtopic=18650 and some of the BIOS that could actually boot from a IDE CD-ROM only booted from floppy-emulation bootable CD's When SATA was introduced, it was meant as (or at least was used as) a "parallel" (pardon me the pun with it's serial nature) BUS, to be added to "normal" IDE/ATA/ATAPI for "high speed" hard disks. As thus, there are (should say were) motherboards that do have problems booting from a CD device on the SATA bus, simply because they somehow "expect" that anything connected to the SATA bus is a HD-like device. Situation with BIOS implementation of "booting from USB bus" is even worse. Every builder has made his own (crappy in my opinion) BIOS extension for booting from USB and we are in a complete mess, and we still haven't talked about USB "ZIP" booting. Just check FAQ#10: http://home.graffiti.net/jaclaz:graffiti.n...SB/USBfaqs.html And this thread: http://www.boot-land.net/forums/index.php?showtopic=7739 to have an idea of what problems one can find with pesky BIOSes Of all the USB devices that may (or may fail to) boot on a given "pesky" BIOS: Hard disk stick (HD-like formatted) stick (superfloppy formatted) stick (ZIP with MBR formatted) stick (U3 or however dual LUN with CD-like device) CD/DVD The last two are the LEAST experimented with. jaclaz

johnc, don't want to put you down, mind you , but if you think to use the Vista BOOTMGR as CD loader for a XP install, I think you are on a wild goose chase. There are several, tested and known to be working CD loaders/bootmanager, including: syslinux/isolinux grub4dos CD shell BCDW all of them freeware, some Open Source. They all work, have been tested and tweaked for years, are more flexible, give more options. Using the Vista one, besides creating possibly a problem with the OS License (you need both an XP and a Vista License) is sure COMPLEX, and I doubt would give ANY advantage over the standard bootsector. jaclaz

Hey peeps, it's not difficult, it's just probably outside your field of normal interest/experience. A Microsoft install CD has a 2048 bytes no-emulation bootsector (sometimes referred to as "Arnes boot record", sometimes as "Microsoft Corporation.img", that loads two files from the I386 directory: BOOTFIX.BIN (it's the thingy that say "Press any key to boot from CD") SETUPLDR.BIN <- this is the NT loader for setup grub4dos among other bootmanagers has the ability to load SETUPLDR.BIN just as it was loaded by the original MS bootsector. Since what is actually loaded the first time is grub4dos, the term chainload is used. (and it's also in the form "chainloader" a grub4dos command). Vista uses different files, etboot.com (the 2048 bytes no-emulation bootsector) and then the BOOTMGR/BCD. Normal XP install CD boots as follows: no-emulation bootsector->BOOTFIX.BIN->SETUPLDR.BIN->rest of files A grub4dos floppy emulation CD can boot either: grldr_on_floppy_image->menu.lst->whatever (including SETUPLDR.BIN) dos_on_floppy_image->grub.exe->menu.lst->whatever (including SETUPLDR.BIN) linux_on_floppy_image->grub.exe->menu.lst->whatever (including SETUPLDR.BIN) A grub4dos no-emulation Cd can boot: grldr_as_no-emulation-image->menu.lst->whatever (including SETUPLDR.BIN) jaclaz

Look in the forum you posted: http://www.msfn.org/board/index.php?showforum=5 there are 4 (four) sticked threads related to a known problem with Seagate drives. Just start reading them. jaclaz

As known, there are three kinds of emulation: http://www.boot-land.net/forums/?showtopic=4733&st=3 They are listed in the order of actual "most wide compatibility". The El-Torito floppy emulation one should boot on anything. The no-emulation one gave initially problems on some BIOS/CD's (I am speaking of years ago, when they were largely introduced by Windows 2000 CD's). It is possible that the same problem is happening today with the USB CD-Rom Bishop is using. The hard-disk emulation can be a problem, as an example it won't work properly on Qemu, see here: http://www.boot-land.net/forums/index.php?...=3890&st=46 So, something to try, besides using the tested, working, and "simple" as I see it USB stick approach, would be to make an El_torito floppy emulation CD with an image booting grub4dos and from it chainload the SETUPLDR.BIN on the CD. As well, using grldr directly as no-emulation boot cd may work, or at least it would help in finding out whether the problem is: in the emulation mode, or in the specific MS no-emulation bootsector, or in somethng else I don't think that the problem with SATA CD's/DVD's is connected to the above, however. jaclaz

It is curious to see all the efforts by wimb and ilko_t being dismissed by comments like "it is complex". Try reading these: http://ccollomb.free.fr/blog/?p=59 http://myeeeguides.wordpress.com/2008/11/1...sb-flash-drive/ It doesn't seem like "complex". The methods were developed using HD-like devices. Using CD-like devices is completely different. You may find something useful here: http://www.msfn.org/board/index.php?showtopic=121502 Since mg.eggink explicitly stated that for the CD-like device "Manual Install and Upgrade for removal" can be removed, the problem should be in something else. From what you write it could be a problem with the no-emulation bootsector of the CD, or with the options with which you burned it somehow not being compatible with the Aspire BIOS. jaclaz

Even without massive google searching, in this same forum: http://www.msfn.org/board/index.php?showforum=5 you will see how vast is the problem with 500, 750, 1000 and 1500 Gb Seagate harddisks of 7200.11 series. FYI: http://www.msfn.org/board/index.php?showto...092&st=1034 http://www.msfn.org/board/index.php?showto...092&st=1045 http://www.msfn.org/board/index.php?showto...092&st=1156 Personally, I believe that currently drives up to 250 or 320 Gb are a bit more dependable. http://www.msfn.org/board/index.php?showto...29114&st=11 jaclaz

The one reported to be working was the WinsetupfromUSB GUI one: http://www.msfn.org/board/index.php?showtopic=120444 but don't think it will make a difference. Most probably you deleted with nlite something that you shouldn't have. Let's wait for the nlite experts. In the meantime, if I were you I would remove from the post a file which incipit is: jaclaz