jaclaz

On other UNrelated news : http://www.metro.co.uk/tech/911912-ebay-changes-logo-in-a-bid-to-embrace-the-future What else one could say if not : jaclaz

Why? I mean poor innocent baby whippersnapper (just to place him/her behind the green glass door together with Kelsenellenelvian ) Just kids having fun http://www.imdb.com/title/tt0090555/quotes?qt=qt0298600 jaclaz

The VBEMP driver uses VESA resolutions. (but it won't only work at the resolutions the video card won't "expose") http://www.navozhdeniye.narod.ru/vbe9x.htm None of the above resolutions is 16:9. Quick reminder: W/H=1.25->5:4 W/H=1.333->4:3 W/H=1.600->16:10 W/H=1.778->16:9 Common resolutions: SXGA 5:4 1280 1024 1280 x 1024 VGA 4:3 640 480 640 x 480 SVGA 4:3 800 600 800 x 600 XGA 4:3 1024 768 1024 x 768 XGA+ 4:3 1152 864 1152 x 864 UVGA 4:3 1280 960 1280 x 960 SXGA+ 4:3 1400 1050 1400 x 1050 UXGA 4:3 1600 1200 1600 x 1200 WXGA 16:10 1280 800 1280 x 800 WXGA+ 16:10 1440 900 1440 x 900 WSXGA+ 16:10 1680 1050 1680 x 1050 WUXGA 16:10 1920 1200 1920 x 1200 WQXGA 16:10 2560 1600 2560 x 1600 WXGA 16:9 1280 720 1280 x 720 HD+ 16:9 1600 900 1600 x 900 FHD 16:9 1920 1080 1920 x 1080 QWXGA 16:9 2048 1152 2048 x 1152 WQHD 16:9 2560 1440 2560 x 1440 The closest possible is the 1280 x 800 (which is 16:10) but cannot say if you can use it. jaclaz

For NO apparent reson : jaclaz

I am looking for what I think is a simple tool, but I am literally overwhelmed from the results of searching/googling for it. It seems like everyone, before or later has written a tool to preview fonts. The tool I am looking for should have the following characteristics: be able to run on XP allow comparison preview of NON-installed fonts (like - example - fonts in a given directory or set of font files manually added to a list or from a pre-made list) allow a custom text to be used for the preview NOT needing/using .Net possibly (but not vital) needing NO install Freeware (yes, I am cheap) To try and explain better what I am after, what I did in the past with my dinosaurish approach (and still do for lack of a better method/tool) is/was: install all fonts open a spreadsheet type the string i want in a cell copy the cell down n times type in the near colums the font name and the actual filename of the font file apply to each cell of the first column the correspondign font formatting insert a column on the left insert in cells in this leftmost column ordering numbers (from a visual comparison) re-order the whole set along the order number loop to #8 until I find a set of thre or four "similar enough" fonts to make further experiments finally choose the "right" font among the few selected with the above procedure If anyone knows of some tools capable of doing something *like* the above in a simpler way, I would be very thankful for any suggestion, as well if there is a completely different approach leading to the same final result, I am all ears. jaclaz

grub4dos (which is NOT GRUB and NOT GRUB2) which is the tool used has "native" support for gzip compressed files. There is no need to uncompress the winvblock.ima.gz, BUT if you (WHY?) want to decompress it, you need to change the menu.lst, as right now "points" to winvblock.ima.gz. map --mem /winvblock.ima.gz (fd0) map --mem /winvblock.ima.gz (fd1) More technically a line like: equates (PSEUDO CODE): gzip /winvblock.ima.gz | map --mem (fd0) i.e. the expanded output of the gzip (winvblock.ima) is piped to the map command. jaclaz

No, as I told you I never try things I suggest. Yep, but that is only a reference related to your failing to find a reference, not at all a suggestion for a viable way to boot Windows 7 from a .vhd file, as it covers ONLY the actual real-mode part of the booting (which is also covered by grub4dos), the whole point being the support in the protected mode that must be provided by either the "native" VHD mounting provision of some releases of Windows 7 (which does not work on FAT32 by design) or by using a suitable driver, the mentioned firadisk or Winvblock (or there may be other ones). You might want to go again through this: http://reboot.pro/15407/ Those drivers "simply" map a file to a (virtual) disk device, it doesn't make any difference on which filesystem the file resides, as long as it is accessible. Most probably you are having an issue with the actual driver(s) do check : Firadisk: http://reboot.pro/10234/ http://reboot.pro/16646/ http://tech.outcult.com/tutorials/winram/01/ Winvblock: http://reboot.pro/13738/ http://reboot.pro/15997/ http://reboot.pro/16141/ Since the limit for a file on a FAT32 device is 4 Gb and there are anyway RAM limits (firadisk), the Windows 7 needs obviously to be "considerably" slimmed down. I presume that since most people uses "native" Windows 7 booting from .vhd capabilities (from files residing on NTFS) the development of the mentioned methods wasn't particularly followed. Or, if you have the money, you can see if the Commercial Vboot works on FAT32 (it should) : http://www.vmlite.com/index.php?option=com_content&view=article&id=51&Itemid=148 jaclaz

Which still applies only to 16-bit programs.... http://ss64.com/nt/start.html http://www.windowsnetworking.com/kbase/WindowsTips/WindowsNT/AdminTips/Miscellaneous/Running16-bitprogramsinseparatememoryspace.html http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/start.mspx?mfr=true jaclaz

Just in case: (Link temporarily removed along the lines of the "better safe than sorry" approach) jaclaz

Well, maybe there is need to type this slowly so I will do so : If you have a BSY or LBA0 then you are in the right place, as this thread is RESERVED ONLY to a possible solution to BSY or LBA0 problem. A drive suffering from BSY or LBA0 spins up normally. If a drive does not spin up, it is NOT in BSY or LBA0, and if you want help with it you should START A NEW THREAD about your issue (which is NOT a BSY or LBA0 problem and - as such - does not belong here). It well possible that your disk is suffering from ANOTHER problem that prevents it from spinning up and that causes ADDITIONALLY a BSY or LBA0 problem, but since the only known solution, talked about in this thread is about a disk that IS spinning normally AND can ONLY work on a disk that is spinning, it makes NO sense trying to find similarities, as until (and if) your disk won't spin the proposed solution won't simply work. Now you are perfectly free insisting on posting on this thread, but what you will likely get is - besides upsetting the people that would otherwise most probably try and help you - simply making this already confused and long thread more confused and longer. Automotive comparison : Q. I hit a curb with my car. The alloy wheel is in pieces, and the tire is flat. How can I repair the tire so that I can drive the car home? A. You need to fix or replace the wheel before repairing the tire. R. But the noise the car makes is very similar to that of a flat tire. A. Yes, but you still need to fix the wheel as a tire won't inflate or remain inflated on an alloy wheel that is broken in pieces. jaclaz

Of course not. I only give senseless suggestions based on things I never tried myself. Though not the most reliable source in the world: http://reboot.pro/15997/ jaclaz

Yep. You may also want to try a "dedicated" sync tool: http://blinksync.sourceforge.net/ jaclaz

Without entering in whether the actual "concept" is correct (last time I checked you hade to load pxeboot.n12 ), the error 1 simply means that you have not a space between the --raw switch and the target file path and the grub4dos parser reads "--raw(pd)/bootmgr" as a "single item" (since it is a single item withut the space). Again, which EXACT version of grub4dos is it? What device (NAS/whatever) is it? Can it not trun a BINL server? As in: http://reboot.pro/1656/#entry119166 http://www.ultimatedeployment.org/win7pxelinux5.html jaclaz

Basically, yes. The issue may be that it is possible (a number of factors are involved) that the NTFS filesystem driver will "choke" on partial data (or when you try accessing files that are not there) and force or require a NTFSCHK. It is possible that you will need anyway to run TESTDISK on the "newly made" disk to fix the second copy of the bootsector, but I seem to remember that it won't be needed. Once you (hopefully) got back the "main" files (the ones within the first 137 Gb imaged), and ONLY then, we will try to see what can be done on the original HD. A guess (educated , but still a guess) could be that *somehow* the original disk "self-capped" to 137 Gb. It is something that can happen "generically", I haven't been able to find substantial reports about this issue affecting particularly this specific disk model. You can try using this: http://blog.atola.com/restoring-factory-hard-drive-capacity/ I think that the disk must be connected "directly" (NOT through the USB converter) for this kind of tools to work. The above is a "simplified" user friendly specific tool, a "pro" would most probably use HDAT2: http://www.hdat2.com/ or a similar "lower level" tool, but the good thing is that the Atola tool will either work or fail completely, but shouldn't make things worse if it fails. jaclaz

The usual F8 is probably a 0x0000007. I gave you some links. Tens, hundreds or maybe thousands of people used and use this approach, and you also posted starting from here: http://reboot.pro/9830/page__st__800#entry160343 that the particualr build you used worked for you, but you have issues with Task Scheduler. So, yes, you must be doing something wrong. Winoutreach is right regarding "native" boot, but using other tools it is perfectly possible. jaclaz

Sure, that should do nicely. (of course all data - if any - currently on the 1 Tb disk will be lost) If you need help to dd the 137 Gb image to the disk, ask, but if you use dsfi (part of the dsfok toolkit): http://members.ozemail.com.au/~nulifetv/freezip/freeware/ it should be easy unless the Windows 7 - for any reason - creates issues. Be VERY careful about WHICH PhysicalDrive n to use AND be aware that the dsfi (being a complement to dsfo) uses a "reversed" logic in command line: i.e. Good, it should be a "normal" BIOS (seeing the disk as having 255x63 HS geometry) the issue would have been if the BIOS )like many HP's and Lenovo) see the disk internally connected as 240x63 (the USB connected are always seen as 255x63). jaclaz

Hmmm. Which errors? Using grub4dos/grldr how (EXACTLY)? Using grub4dos/grldr which (EXACT) version? Why #3 is not an option? Why not trying the 5th (or maybe 5th and 6th) way? jaclaz

Yes/No. http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/questions-with-yes-or-no-answers.html A good idea would have been to SEARCH first: MAKE SURE you are in either BSY or LBA0 and if not, start a new thread. Does the disk spin? (normally when powered up) If it does, the should mean that the board and hard disk contacts is not good or ot good enough, completely detach board clean contacts and try again: jaclaz

Being a little picky, but it would be more correct to say something like; "BOOTMGR and BOOTMGR.EXE are actually the same file, but the first has some added code (16-bit) to make it a suitable local boot target" Yep , my bad I got it the "other way round" . jaclaz

Hmmm. .bin says "little". Which program made the file? It is "queer" that the error is about "bad sectors". Which OS are you running (apart W98) or can you run? Where is (physically) the .bin file saved? It is not at all clear (to me at least) if the error is in the .bin file, in the media on which it is or in the way the two mentioned tools attempt to extract the .avi from the .bin. I would try to mount the .bin in a Virtual CD and then copy from it with a tool like Unstoppable Copier (or similar). Then I would throw at them files every tool around +1, another one: http://www.risingresearch.com/en/dvr/ Also Virtualdub has more options that you (or myself) will ever be able to understand and use, I seem to remember that I managed more than once to create "good chunks" from otherwise corrupted videos, but cannot remember the details and most probably it depends by a number of factors like codec, etc. or maybe try VirtualdubMod: http://www.afterdawn.com/guides/archive/repair_broken_or_corrupt_avi_files.cfm jaclaz

BOOTMGR and BOOTMGR.EXE are actually the "same" file BUT the second has some added code to make it a suitable "pxe" target. EDIT: BUT the first has some added code (16 bit) to make it a "local boot" target. EXACTLY like it was in the good ol'days with SETUPLDR and SETUPLDR.EXE, see: http://reboot.pro/5900/ http://reboot.pro/4952/#entry40701 It seems to me like you pinned down exactly the problem, i.e. the way BOOTGR.EXE looks for the BCD, and right now it seems to me like there are only the metioned ways out: use an original WDS server using the workaround you found http://www.0xf8.org/2012/04/the-30-second-delay-in-booting-windows-pes-pxeboot-com-via-pxelinux/ using an alternate WDS server (suggested but UNtested) using an alternate loader from pxelinux (suggested but UNtested) Another possibility (also to be tested) is here: http://reboot.pro/1656/ http://www.ultimatedeployment.org/win7pxelinux1.html jaclaz

The grown image, the NTFS filesystem driver is likely to throw errors on a "less-than-declared-size" one. The "grown" image should mount, the only issue being (hopefully) the backup of the bootsector, which shouldn't be checked by the NTFS filesystem driver when mounting . It is very possible that - for any reason - the partial image that you have is not an image of the first 134 or so Gb of the original hard disk (and consequently the "grown" image is "invalid") or that somehow the $MFT is "misplaced" in the "grown" image or that - again for *any* reason the making of the sparse file or the dd-ing to it of the partial image produced an invalid image. How EXACTLY did you create the "grown" image? Please list EXACTLY, in DETAIL, EACH and EVERY step you performed to make that image. jaclaz

Many of the devices you listed are OK. Particularly those based on the Max 3232 and on the PL2303 chips. This one definitely is NOT. http://www.ebay.com/itm/280942999018?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649 The CA-42 maybe or maybe not. This one is a USB to serial (nothing to do with TTL): http://www.ebay.com/itm/B-USB-2-0-SERIAL-RS232-DB9-9-PIN-ADAPTER-CABLE-PDA-/160523344872?pt=US_Parallel_Serial_PS_2_Cables_Adapters&hash=item255fefdbe8 Yes, CTRL+Z means : Please review the suggested guide by CarterinCanada: http://www.mapleleafmountain.com/seagatebrick.html ALL of it but particularly the part titled "The Real Deal - Fixing the Drive" AND the READ-ME-FIRST (which contains more details about the TTL level that maxes at 3.3 V and the TTL level that maxes out at 5 V (both have nothing to do with the actual 3.3V or 5V DC or VCC at which the thingy might be powered and/or from which power can be drawn): jaclaz

Do the .avi's play in VirtualDub? http://www.virtualdub.org/ jaclaz

Good. Wait a minute, are you still using the "resulting" image as ddrescue created it, or did you "grow" it to it's full size (creating a new file with mksparse and dd-ing to it the image)? jaclaz