jaclaz

Sure , why shouldn't it? ... unless of course you are planning to create an Excel or Word file exceeding 4 Gb in size ... jaclaz

Is boot-land "singularly focused"? Being it the Official support Forum for: Winbuilder (and all projects based on this engine) <- PE builds of any kind based on XP/2003/Vista/2008/Windows 7 grub4dos <- universal boot-manager IMDISK <- ramdisk and filedisk driver RMPREPUSB <- USB partitioning/formatting utility Sardu <- multiboot CD build with Linux TFTP32 <- TFTP Server Winimize <- reduce Windows 98 size and boot it from almost anything bearwindows <- universal video driver for 9x and NT based systems Unetbootin <- advanced install from USB app Firadisk <- new ramdisk driver with advanced capabilities And the UNofficial one for: fbinst <- USB partitioning, formatting and more Syslinux/isolinux/memdisk <- you know what this is LODR packs <- a new approach to portable apps Aerostudio <- graphical bootmanager for CD/DVD's and more Besides being "another" home for these: Maybe it is not as "singularly focused" as some other boards , but who cares? I mean, the imortant thing is to share and exchange experiences, ideas and knowledge and help each other, it doesn't matter on which board/place on the net. And, BTW, this is cheating : jaclaz

Now, it is NOT about level of power going in, it's about TTL voltage level getting out. Read the post I linked you to. Read the link in it: http://www.interfacebus.com/voltage_threshold.html Check the specs of your interface, connect it wisely. I personally doubt that on a USB to TTL interface the good engineers who made it wrote "USB to RS232", but of course everything is possible. Where did you buy it? Are the specs of that interface available online? jaclaz

The working link is the following: http://home1.gte.net/res0uhdx/QuadraVex.exe (the board parser included the final period or dot as part of the url, thus making the link invalid) jaclaz

Well, it's strange, it seems like working for me with "Desktop.ini" jaclaz

Short answer: YES. The point is that you need to install the same program TWICE, one from XP and one from Windows 7, using the SAME "target" (the third partition). The files copied to the third partition will be overwritten by the second install by an identical copy of themselves, but each OS will have the right settings. Each "system" volume (and Registry) will have the appropriate "general entries" and the "mass" of the program will be installed on the "OS agnostic", "third", FAT32 partition (though of course if we are talking of dual booting XP and 7 there is no need for it to be FAT32, it can be NTFS as well). Most, if not all, programs will work this way. jaclaz

Well, I don't. Obviously one must clean his system from any virus BEFORE formatting anything, who knows if the format will be effective or if it will be a fake one modified by the Virus? But then, once the HD's BOTH internal and external ones are clean from virii, there is NOT one reason in the world to actually format anything. jaclaz

Hey peeps, have you actually read cdob's post? Windows 95 lacks UDF support. Being UDF a filesystem, it means that a filesystem driver is missing, which not necessarily is connected to CDFS.VXD (which is the CDFS filesystem driver) . Astonishingly , the MS guys have actually given a sensible name to UDF.VXD, which is in Win98_48.cab: http://support.microsoft.com/kb/188436/en-us Whether it is possible to add it to VMM32 in Windows 95, it's another thing, of course. jaclaz

Yes, grounding is a must, expecially if you are drawing power from two different power supplies, but I wonder if you are using one of those auto-adjusting TTL interfaces , see here: it is possible that if you supply 5V to the interface you get the "wrong" TTL levels in output. So, you should start a new thread about your current problem, drive is not anymore bricked and it doesn't "belong here" anymore. The thing you are missing is that a drive that has bricked is a FAULTY drive, the methods we use on this thread may unbrick it, BUT there is no magic wand, after the unbricking the drive is to be considered FAULTY, you should get all the data from it, if you can, and then eithr throw it in the dust bin or use it as tertiary backup media. It is possible that besides the bricking problem your drive suffers from other problems you should run the Seagate Diagnostic Tools on it and report (again in ANOTHER thread). jaclaz

See if it's one of the ones listed here: http://diabo.freehostia.com/windows/remove.htm jaclaz

Nothing so obvious. If BIOS recognizes it, it is not anymore bricked. The fact that you haven't seen the percentage of advance of the user format doesn't mean anything, the main part is: To restate the obvious, this thread is about two problems: 0 LBA BSY state Your drive is EITHER in one of the two states above (and then this thread may be of use) or it is NOT (and then you should start a new thread about your problem). This: tells us nothing in order to let us try and help you, we need DETAILS. Wait a minute. You don't want a USB to RS232, I repeated this info n times , but it seems like it simply does not pass through . The drive "speaks" TTL. You can have: (on a desktop or laptop that has a built-in RS-232 "serial" port): a RS-232 to TTL interface (on a desktop or laptop that only has USB ports): EITHER: a USB to TTL interface OR: a USB to RS-232 interface AND a RS-232 to TTL interface jaclaz

I don't care if you have a legal key, the downloaded copy is WAREZ anyway, but more than that it is a modified copy with services/files removed. We won't help you on this. jaclaz

Yep , basically anything that protrudes from the faces of the ideal "parallelepiped" of the hard disk is an "artifact". Noone in his right mind would solder anything to a "normal" HD PCB, voiding the warranty an what not, so, yes, it is definitely a "piggy back" PCB applied to the drive, BTW nice visual representation VideoRipper , which you can easily remove and get the "plain" HD. jaclaz

The black thingy in your second picture does look like a connector that cna be removed from the drive. Can you post a picture showing the whole drive upside down? jaclaz

Probably slightly off-topic, but JFYI: http://www.msfn.org/board/index.php?showtopic=142189 jaclaz

http://blogs.computerworld.com/15655/leaked_microsoft_intelligence_document_heres_what_microsoft_will_reveal_to_police_about_you?source=CTWNLE_nlt_security_2010-02-25 http://www.wikileaks.org/ jaclaz

Yep , but the Home Page of the program is the one already given by Jeremy: http://www.music-similarity.com/ jaclaz

Of course the easiest being that of buying for a few bucks an USB adapter capable of connecting to both ATA and SATA and both 2,5" and 3,5", something like this (just an example): http://www.amazon.com/USB-SATA-5-25-Cable-Adapter/dp/B000YJBL78 jaclaz

It was merged here: @Nic303 Go to your member page: http://www.msfn.org/board/user/244073-nic303/ and "find posts" or use Search and "search for all posts by user xxxx", this way you can quickly find if your post has been moved and/or merged into an existing topic. Obviously if your post is one that started the thread once it is movesd or merged the original thread vanishes. jaclaz

Fred, I am not sure to understand what you posted (or what MS writes ), the effect of pointing those Registry entries to "a suffusion of yellow" seems from this: http://support.microsoft.com/kb/222193/en-us like being that nothing is found in the DDLCACHE folder and THEN a search for installation is performed AND IF file not found THEN installation media is required: jaclaz

I am not sure if I get the full meaning of this, does it somehow mean that if I have a laptop and bring it on holidays in some other State/Region MS could limit the thingies I can get from their site depending on the place where I am connecting from (as opposed to the actual region where I bought a license for the OS or the actual Licnse itself)? @Tripredacus Canary Islands are to all effects Spain, and EU, at least from an administrative/legal point of view. Where can one find "N" or "Starter" zones listed (whatever they are)? jaclaz

Sure, but I don't see the connection with Me (in the sense of ME only). Sometimes (read, as you prefer as "often" or "always") MS KB/docs are written in a "cryptic" way, without providing the "real information" or doing so in such a way that each single word need to be weighted, or without a clear explanation, as an example: http://neosmart.net/blog/2007/bootsectexe-modifies-the-bootsector-not-the-mbr/ http://technet.microsoft.com/en-us/library/cc749177(WS.10).aspx but it doesn't seem to me like this is the case. As I see it, what MS says is: DO NOT USE FDISK (latest version for 98/Me) to create partitions larger than 512 Gb, as the utility was NOT designed to do this ANYTHING above 128 Gb results in "a suffusion of yellow" UNLESS the particular PC BIOS supports 48-LBA addressing Whilst #2 is without any doubt true, and also verified, #1 needs experimentations, as an example, it is possible that partitions bigger than that can be created but they result, once FORMAT is used on them, in incorrect data in the bootsector, like wrong number of FAT tables, wrong number of hidden sectors, wrong something that may go unnoticed until you actually try and check EVERY aspect of the created partition/filesystem. And again this problem may be something that it takes 5 seconds to fix with a hex/disk editor or something that needs a more complex patch. jaclaz

Well, alternatively, you can re-boot, since the OP drive was a USB one, disconnecting and re-connecting it is easier. It is not "compulsory", but different OS (remember that TESTDISK can be run on many OS) may have different behaviours when it comes to detect changes in the MBR and Partition Table. If you want an example of a "more advanced" TESTDISK session, check this thread: http://www.msfn.org/board/index.php?showtopic=133933 jaclaz

It is possible that you are failing in your goal. Sure. Can you post WHERE Microsoft said the listed 4 points? Here they are numbered: - Fdisk update is not designed for 48-bit LBA - Fdisk update is not supported on drives larger than 128 gb - Fdisk update is limited to 512 gb "by design" (contradicts previous two points) - Win-Me Setup boot disk can be used to partition drives larger than 512 gb (how?) The MS kb references should be these: http://support.microsoft.com/kb/139579/en-us http://support.microsoft.com/kb/239113/en-us http://support.microsoft.com/kb/239119/en-us http://support.microsoft.com/kb/245213/en-us http://support.microsoft.com/kb/263044/en-us http://support.microsoft.com/kb/263045/EN-US/ http://support.microsoft.com/kb/280737/en-us < #3? http://support.microsoft.com/kb/327202/en-us < #1 & #2? I am missing where #4 may come from. To clear some points (or maybe further confusing you ) read here: http://thestarman.pcministry.com/asm/mbr/FDISK.htm jaclaz

If I may you should add - if possible - something like a double check-box for selection, to avoid non expert users messing with their "non-USB" drives. jaclaz