jaclaz

Well, the state of the art is obviously Commercial. AFAIK, it is basically a monopoly, led by nuance. Since it's going to be a pro tool, I guess that the added "transcription and synchronixzed playback" is needed, and thus: http://www.nuance.com/for-business/by-product/dragon/dragon-for-the-pc/ND_004125 the professional version is needed. BUT AFAIK, no Portuguese support: http://nuance.custhelp.com/app/answers/detail/a_id/3315 OT, but a nice take on early telephon voice recognition systems : http://snltranscripts.jt.org/05/05bdate.phtml On the Open Source front, this is a good "start point": http://voxforge.org/home but it seems to me like the good guys are well in a very initial stage. jaclaz

Well, but they have BOTH SIMMs and DIMMs (and SO-DIMMs too), though. jaclaz

And Nutella, and jelly, but no jam, eggs, but no bacon. The programmers in there don't ever make breakfast, but they always have dinner AND supper. jaclaz

Well, you can read the first also here: And the second is mainly nonsense, the new alignment originally derived from access optimization on databases and was adopted mainly for that reason and with compatibility with new sector sized HD's in mind (more theoretical than practical in everyday use), nothing to do with SSD's I am afraid: http://msdn.microsoft.com/en-us/library/dd758814.aspx http://reboot.pro/9897/page__st__40 http://www.anandtech.com/show/2888 jaclaz

Actually you are supposed to run RMPREPUSB. The new flash sticks needs to be PARTITIONED before being formatted. RMPREPUSB (and other similar utilities) do that, which is NEEDED. RMPREPUSB has additionally a couple little tricks that will increase you chances of bootng the stick on a bigger number of motherboards, even a few with "queer" Bioses. jaclaz

One of those questions that can be answered with yes/no/maybe/who knows. The geometry of a "real" device is NOT saved anywhere. It is the device itself that upon interrogation reveals it's own geometry. Then the BIOS, or the OS, or BOTH, may decide to EITHER: confirm the device "inherernt" geometry OR: change it to whatever it "likes" DOS trusts WHATEVER geometry the device "exposes". Some BIOSes (typical Lenovo laptops) "force" geometry to 240 heads. "Strict" BIOSes (typically BOCHS/QEMU one) force a geometry (on a RAW disk image - i.e. one without an exposed geometry) depending on size reported by device. NT 4.0 would use the "natively" (i.e. when the device, such as a virtual disk, does NOT expose a given geometry, a 64/32 one) 2K and later use "natively" a 255/63 one, but do use the one the BIOS sets in the early phases of booting. Theoretically 2K and later ONLY use LBA access, thus geometry should have NO meaning whatsoever for them BUT, due to legacy code in the MBR and the bootsector, if you use a "wrong geometry" they won't be able to BOOT from the drive. For some operations (loosely connected with the above) TESTDISK needs the "right" geometry, which you can then set inside the program. The above can be summed up into: JFYI: http://www.911cd.net/forums//index.php?showtopic=23408 http://www.911cd.net/forums//index.php?showtopic=21702&st=129 http://www.boot-land.net/forums/index.php?s=&showtopic=8528&view=findpost&p=73205 And, slightly (but not much ) OT: http://reboot.pro/6546/ http://reboot.pro/2246/page__st__15 You do not have to worry as in your case geometry should remain 255x63. The "right" way - as I see it - is to use the "legacy" Cylinder/Head boundaries. Of course the good MS guys are not of the same opinion and introduced in Vista a different approach. In some setups the combined effect of this choice and the stupidity with which the 2K/XP/2003 disk management was made can create serious problems: http://reboot.pro/9897/ Also, using "sorted partitions is ALWAYS a good idea IMNSHO: http://reboot.pro/13757/ jaclaz

But that is not a problem as they have the whatever swill or goo they swallow well cooled (actually chilled) , problem is there are no liquors (but luckily enough some booze and - don't tell it aloud - plenty of hooch). jaclaz

Sure you can. Point is if it's OK to have a 120 Gb "set of partitions" + another one or if you want to extend the "main" partition to "fill" the bigger HD. If I were you I would dd the image "as is" and in case extend it later (once it has proved to be working). jaclaz

Well, it depends obviously on how often you do the shadow copy, and if it was properly configured, and if you have enough space, and if you included the folder in the shadow copy... http://sourcedaddy.com/windows-7/restoring-file-shadow-copies-previous-versions.html http://www.pcmag.com/article2/0,2817,2342534,00.asp The default should not have changed since Server 2003: http://technet.microsoft.com/en-us/library/cc728305(WS.10).aspx I don't see it as such a great and effective increase of "safety", which is IMHO mainly in the user's head. Quite the opposite, at least in my circle of less computer savy friends, this (and similar added features) are seen as an authorization to thoughtlessly do any stupid deletion/change/whatever and to never backup data. jaclaz

Well, you cannot just rename them to .png. The 89 50 4E 47 0D 0A 1A 0A in the header is first 8 bytes, you have an "excess header" of 24 bytes: http://en.wikipedia.org/wiki/Portable_Network_Graphics#File_header You need at least to cut it out. jaclaz

The more (or less) probabilities to recover deleted data are pretty much OS independent (and have no real connection with "security" or "reliability") but quite heavily filesystem dependent. Assuming that you use NTFS on both there won't be ANY difference. If - by any chance - you used that "third party utlity" installing it on the actual OS that was running when the files were deleted, you did it wrong , those tools needs always to be used when booted from another OS (possibly also booted from another disk), and you can use the SAME "third party tool" under another XP install to recover files on BOTH a Windows 7 and a XP without any difference worth of note. jaclaz

What will the real programmers (of which there are plenty) drink then? http://uranus.chrysocome.net/ http://uranus.chrysocome.net/coke.htm I assume there are bottles, and no cans. jaclaz

Hey, it 's you that have those programs, personally I would use isoinfo, some info (pardon the pun ) here: http://reboot.pro/12406/ and mkisofs (or oscdimg) to create the .iso. To maybe better clear what I am guessing is that some of the early accessed files are "beyond reach", compare with this: http://www.911cd.net/forums//index.php?showtopic=20248 jaclaz

Wouldn't you also need a cam pointed to each screen? I mean if the number of machines is so big, are you really sure you won't be forcing a resolution, color depth or refresh rate that is not suitable with a video card or monitor among the machines? If I were you I would look into nirsoft's nircmd (setdisplay command+remote or multiremote): http://www.nirsoft.net/utils/nircmd.html jaclaz

You have a queer way of presenting problems, (presuming that people on the board all have a crystal ball to know among the few tens of possible ways and tools you used and choices in them, which exact part is the problem and point you to it by sheer magic..) You particularly do not detail how you actually create the .iso. The NTLDR has limited capbilities when accessing a CDFS filesystem, and as well in the intial phases of SETUP, some LBA addresses might be "unreachable". From your other post I presume you are using MagicIso, a Commercial tool that since 2005: You might want to check the actual LBA addresses of NTDETECT.COM (and of all files it cannot find). About runonce.cmd, even my crystal ball cannot list it properly, so you mught want to post for review. jaclaz

Yep , the idea is that you need NOT download 1.7Gb to read a lousy EULA 10 Kb in size. Expecially if you have a slow connection .... ....and a hard disk filled up to the brim..... Thanks for the basket, I am sure that it will prove useful. jaclaz

Good. jaclaz

What you report is the output of the LBA0 fix. If the drive is not detected, you have a BSY problem (and the "cure" you applied for LBA0 won't work). If the drive is detected BUT with "0 capacity", you have a LBA0 problem (and the "cure" you applied should work) It's just like you had a cold and instead of taking an aspirin and going to bed you bandaged your left little finger: NOT really effective in the case of a cold, but not that bad in case of a cut in left little finger. BSY problem->BSY cure LBA0 problem->LBA0 cure jaclaz

Easy Instructions: get the WAIK open the downloaded .iso with 7-zip find in root file WAIK_License.rtf open it in Wordpad read it Easier , download the attached, coming from the KB3AIK_EN.iso I have. Cannot say if it has changed in the currently downloadable version: http://www.microsoft.com/downloads/en/details.aspx?familyid=696DD665-9F76-4177-A811-39C26D3B3B34&displaylang=en If you want to check without downloading the whole .iso, see here: http://reboot.pro/13049/ jaclaz WAIK_License.zip

I don't really want to prove you wrong , when dealing with the good MS guys there is always something that is simply inexplicable. Have you ever read the actual ImageX/wim related dll's license (yes, the one everyone has broken, one time or the other) http://www.911cd.net/forums//index.php?showtopic=19355&st=132 and my carpenter's comparison? http://www.911cd.net/forums//index.php?showtopic=19355&st=134 I'll need to upgrade to a bigger basket.

Yep, but WHICH version is it? Just for the record, the "normal" way is to download the FULL Redist : http://www.microsoft.com/downloads/details.aspx?FamilyID=886acb56-c91a-4a8e-8bb8-9f20f1244a8e&DisplayLang=it this one is version 9.25.1476 and from it get the dxsetup.exe (italian): http://microsoft-it.confusenet.com/showthread.php?t=280435 This one: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=04AC064B-00D1-474E-B7B1-442D8712D553 is version 9.27.1734 It has to be cleared whether this 9.29.1962: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=3B170B25-ABAB-4BC3-AE91-50CEB6D8FA8D is true: And if consequently the fact that in this 9.28.1886: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0cef8180-e94a-4f56-b157-5ab8109cb4f5 Windows 2000 is not mentioned does NOT mean that it isn't supported. And/or which exactly is latest version supporting Win2K. jaclaz

Well, it's not that difficult (the base concept I mean). You are whining about not being able to image because you have an image (actually a set of images) that is/are hardware dependent.. Offline Sysprep promises: http://www.911cd.net/forums//index.php?showtopic=22064 Doesn't it look a lot like a solution to the problem? jaclaz

Guess why grub4dos was developed? Here: http://reboot.pro/forum/66/ Get a grasp of the whereto: http://reboot.pro/14/ And of the guide: http://reboot.pro/5187/ http://diddy.boot-land.net/grub4dos/Grub4dos.htm First thing. jaclaz

Well, kids today, my first one was a ZX-80 which you had to solder components yourself.... ...why, in my day ..... http://reboot.pro/1908/ .... and we LIKED it! jaclaz

See also this approach: http://forums.pcper.com/showthread.php?t=444831 jaclaz