jaclaz

Cannot say about Excel 2007, but something similar is common in every release of spreadsheet apps. It depends on the separator you use, in US and Britain are in use the comma as separator for thousands and the period or full stop to separate decimal numbers. In Europe generally it is the other way round. Be aware that there TWO separate settings for this, usually spreadsheet apps use the default "International" settings, but some have also an "internal" setting. Instead of putting "=850*77,1" in a cell, try the following: Input in cells A1 and A2 "850" (without quotes) Input in cell B1 "77.1" Input in cell B2 "77,1" Input in cell C1 "=A1*B1" Input in cell C2 "=A2*B2" Now copy the six cells a couple of rows below, and set cell formats "Number" to "General", you should see why it happens. To check results, when in doubt, always enter integers, like: =850*771/10 This has nothing to do with Excel (or any other spreadsheet for that matter) with any versions: you are simply giving to it data in a way that the app parses as being NOT the number you think you typed. jaclaz

I beg your pardon? I was referring to your question: jaclaz

You can try also using grub4dos. The "standard" way of using it to boot CD's is by using grldr as no-emulation bootsector, which, if the problem you are experiencing is connected to a "no-emulation" incompatibility of some kind, won't solve the problem, but you can use a FAT12 floppy with grub4dos as El-torito emulation image, and from it chainload whatever you want on the "rest" of CD. jaclaz

Also, maybe a "stupid" suggestion, but if you use one of those (wireless) "internet enabled" keyboards, during boot the "F lock" key may be off, and thus the F1 to F12 keys don't work. http://jtsang.mvps.org/flock.html jaclaz

For the record, there are quite a few FREEWARE apps capable of that. Notably (and apologies to the Authors of other ones): DSFO, part of the DSFOK toolkit (command line): http://members.ozemail.com.au/~nulifetv/freezip/freeware/ HDHACKER (GUI): http://dimio.altervista.org/eng/ jaclaz

And the link here: http://www.boot-land.net/forums/Useful-inf...-inf-t1966.html http://www.boot-land.net/forums/index.php?showtopic=1966 jaclaz

@happyusers Try putting all files in a .zip archive. jaclaz

Hey guys, not to be picky, but did you realise that the original poster had this problem in 2005, did you? I guess that he either found his way or a fair number of college students had no chance to use the PC's. jaclaz

"NTLDR is missing" is an error message hardcoded in the bootsector of any partition formatted under 2K/XP/2003. (if the "standard" english botsector is used) So the error is generated long before BOOT.INI comes into play. Forget for the moment anything about this thread and just: 1) Format the stick with the HP utility or petoUSB or any other method you use 2) Copy to the stick NTLDR, NTDETECT.COM and a BOOT.INI with at least two entries 3) Try booting from it If it does, try again the method, using the latest tutorial and the batch file. If it does not, post again, I'll try to help you in first booting part. jaclaz

Yes, it is common (though technically wrong) to call the Command Prompt or Console in windows NT/2K/XP/2003 "MS-DOS prompt". Actually it normally uses also, besides NOT being DOS, a different command interpreter, CMD.EXE instead of COMMAND.COM. Otherwise the good guys that made DOSBOX: http://dosbox.sourceforge.net/ would have done a completely unneeded work when they made the Windows "NT" version. jaclaz

No need (anymore) for Recovery Console install: http://www.boot-land.net/forums/MakeBScmd-...EASE-t2362.html to create a bootsector chainloadable from NTLDR/BOOT.INI jaclaz

Out of topic, but not much, you can use HDtune: http://www.hdtune.com/ to check Supported and Active ATA levels. jaclaz

Maybe stupid question , but does the file resides in %UserProfile%\Desktop\ ? Personally I would use "%~dpnx0" Other possibility, it is a timing problem of some kind. If this is the case, you may want to try a loop similar to the one detailed here: http://www.catch22.net/tuts/selfdel.asp BTW, you seem to be missing a GOTO :EOF to return from the calls in FOR loops. jaclaz EDIT: Sorry Yzöwl, cross-posting.

Really? Can you elaborate on this: Last time I checked the only way to run Qemu in DOS was using HX: http://www.japheth.de/HX.html Maybe you meant it is a Win32 Console app. Did you try installing/running Qemu manager under Win9x/Me? I tried one of the first versions some time ago and wasn't able to make it work. Besides, it seems like Qemu 0.9 has broken support of 9x/Me systems: http://qemu-forum.ipi.fi/viewtopic.php?t=3031 The elder 0.8.2 can still be found on archive.org: http://web.archive.org/web/*hh_/www.h6.dio...8.2-windows.zip jaclaz

Just for the record, here is what Microsoft has to say over the issue: http://support.microsoft.com/kb/302686/en-us The only difference between a quick and a full format is the scanning (and mapping) of bad sectors, on a perfectl yhealthy volume this won't make any difference in the recoverability of data after a format. This: should be read as: http://www.pcguide.com/ref/hdd/file/fat_FATs.htm http://www.pcguide.com/ref/hdd/file/ntfs/archMFT-c.html In other words, existing files are NEVER deleted by a format, whilst information on where the files are IS deleted. Data is generally better recovered if the files are contiguous, so running a Defrag program periodically does help to have better recovery resilts, should a disaster happen. Something everyone should read (Free E-book, also available for download): http://www.easeus.com/data-recovery-ebook/index.htm On the other hand, if you are going to sell or give away your old hard disk, it is a good idea to WIPE it's contents. Generally writing 00's to the entire drive is more than enough. Don't be misled by all the fluff about the Guttman Theory: http://www.boot-land.net/forums/index.php?...c=2683&st=6 jaclaz

not only 'appear' but they ARE faster. There is no DRMs built-in into the code of W2K (as opposed to XP). Thats the sole reason why. Interesting , do you have any link with some details and data? (I used "appears" as I have no exact comparison/test data to show the amount of lag you have under XP.) jaclaz

....but you can make a USB stick an install media, links are here: http://www.boot-land.net/forums/index.php?...=2807&st=20 jaclaz

The idea is to ask for help BEFORE using an app. However, if you just quick formatted the drive, you can try with TESTDISK: http://www.cgsecurity.org/wiki/TestDisk or you can try with its "counterpart" photorec: http://www.cgsecurity.org/wiki/PhotoRec to recover the files. You will need another drive with enough space for the recovered files. If you have a few bucks to spare and the drive was NTFS, these two COMMERCIAL apps are very good: http://www.diydatarecovery.nl/iUndelete.htm http://www.quetek.com/prod02.htm The "poor man's" option is this one: http://memberwebs.com/stef/software/scrounge/ jaclaz

Yes, as I see it there are TWO booting scenarios: 1) BIOS is "right" and SATA drive becomes bootdrive, i.e. \\.\PHYSICALDRIVE0, IDE becomes \\.\PHYSICALDRIVE1 2) BIOS is "wrong" and IDE becomes bootdrive, i.e. \\.\PHYSICALDRIVE0, SATA becomes \\.\PHYSICALDRIVE1 Now you have on the SATA drive FIRST ACTIVE PRIMARY PARTITION ROOT: NTLDR NTDETECT.COM (NTBOOTDD.SYS) BOOT.INI with contents similar to: If you add to the IDE drive FIRST ACTIVE PRIMARY PARTITION ROOT a copy of: NTLDR NTDETECT.COM (NTBOOTDD.SYS) BOOT.INI with contents similar to: When scenario 2) happens, machine will boot as well as before. Drive lettering should NOT be affected as it is dependant on drive signatures, so any "normal" program will work as before. If you have programs, batches or whatever that use the other available syntaxes for "low-level" access to the drives, like \\.\PHYSICALDRIVEx or the \device\Harddiskx\Partitiony or the \Device\HarddiskVolumez, those WILL change, and you need to provide some workarounds. Read these to get an idea of what I am talking about: http://www.msfn.org/board/Discovery_Unusua...ery_t33030.html http://www.msfn.org/board/BOOTINI_hard_drive_t25365.html http://www.boot-land.net/forums/index.php?...=2425&st=19 jaclaz

If I recall correctly it is a known "feature", in all Excel releases. Two workarounds possible: 1) If it is just a "cosmetic" problem, in options there is somewhere an option "Show Zero Values" 2) If you need an empty as a result of the VLOOKUP, use this: =IF(VLOOKUP(TRIM($M$5),'Left out'!$C$5:$M$24,7,FALSE)=0,"",VLOOKUP(TRIM($M$5),'Left out'!$C$5:$M$24,7,FALSE)) jaclaz

But, though not actually the solution to your hardware problem: What prevents you from putting a NTLDR+BOOT.INI+NTDETECT.COM+(NTBOOTDD.SYS) on the IDE drive, with an entry in BOOT.INI to load the OS on the SATA drive? Also, if the data is valuable and expecially it is a security company we are talking about, a UPS is a MUST, as I see it. jaclaz

If I may, these procedures should be taken only (if and) when "the milk is already been spilled" . For a new installation, I would prefer using a migrate.inf file, some reference: http://www.911cd.net/forums//index.php?showtopic=19663 jaclaz

Well, happy it helped solvig your problem. Of course most of the thanks should go to Kaare Smith and Dion Nicolaas jaclaz

For the record, these are also connected to the topic: http://www.boot-land.net/forums/index.php?...ic=3007&hl= http://www.msfn.org/board/index.php?showtopic=90495 I have used the Registrar Lite app to do the multiple Search/Replace. jaclaz

@ryeookin2 Read this thread: http://www.boot-land.net/forums/index.php?...c=2937&st=0 AND given links. If it's OK for you to use RAMdisk booting, read this: http://www.boot-land.net/forums/index.php?...ic=2989&hl= and search here on MSFN, on 911CD or on boot-land for keyword "ramdisk.sys" jaclaz