jaclaz

You cannot recognize pure bull§hit ® when you see it? http://www.reuters.com/article/2013/07/26/us-hacker-death-idUSBRE96P0K120130726 Conspiracy Theory anyone? What will be next? He was not from New Zealand, and was not 35, he was an alien aged 1389 years. He was killed by ESP powers by an Aztec descendant of the enemy alien race that ruled some countries of pre-columbian America. .... Come on, let us all grieve for the loss of a brilliant mind and a so young man, but let's at least wait for some actual data before going astray with theories.... jaclaz

The concept of "detail" means what EXACT hardware you are on (possibly including Vid/PID/PCI ID's of the devices you are having an issue with drivers) AND the EXACT driver (including a link to it) that you attempted using unsuccessfully AND an EXACT description of WHAT happened when you made your attempt, like a driver not loaded error or a cannot start this device/service error AND the Code associated to the error (if any). A quick reference (standard litany): http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/problem-report-standard-litany.html Start with just the RTL8187B_WLAN_Adapter. jaclaz

Sure , but come-on, this is not really a "limit". A "normal" Win9x System partition, even a very large one, and considering all the software you might want to install to it can be at the very most what? 10 GB? (at the times I had both Win95 and Win98 in multi-booting (with DOS 6.22 and Windows NT 4.00 and Windows 2000, JFYI) I used a 1 Gb partition for both DOS 622 and Win95 plus a 2 Gb for Win98, if I recall correctly). That allows to grow it 12x before "hitting" the 128 Gb LBA28 barrier. The LBA 48 upgrades came out for 2K with Service Pack 3 and for XP with Service Pack 1 which means August/September 2002, it's not like since 1995 users of Win9x had issues or particular problems, it's just a matter of using some common sense when creating partitions (and put not *everything* on "C:\" ) jaclaz

I guess that situation (on Law side) is much more complex than that. The document is however public: http://www.gpo.gov/fdsys/pkg/CRPT-112hrpt381/pdf/CRPT-112hrpt381.pdf I guess that the first point that makes the certification needed for those is that a "model" can ONLY be flown for hobby: and, later: jaclaz

Just to confirm that yes, the Volume Tracker besides being one of the silliest thing EVER implemented in a OS , it has caused more diskettes to die prematurely (beside making them not anymore an "exact copy") then you would think. For anyone wishing to read more on the stupidities done over the years with the OEM name, this is a good article: http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/volume-boot-block-oem-name-field.html jaclaz

To me it is still the SAME issue already seen on the good ol' "merge and join" thread. In there I used for simplicity a pre (and post) processing with gsar for substituting characters that created issues in the batch processing. I don't see in which way this is different. In my perverted mind, if you can do without an external tool/app, that is very good , but in this specific case a small .exe like gsar is better (IMHO) than any complexity in batch code and once you have it anyway it is better to re-use it as much as you can (economy of scale , the cost - in bytes - of the tool is amortized faster). jaclaz

WHAT EXACTLY do you actually EXPECT that piece of batch to do? If you prefer what do you apply that batch to? And what you would want to have returned by the batch? jaclaz

Yeah, that's called "feature" or "progress" (BTW the headless peeps at IPB have not even managed to understand how this bug is there since three or maybe four releases, at least these same bugs affect reboot.pro since more than one year - when the board software was updated). ... and at least on reboot.pro the issue wit CODE tags is even worse .... Do some experiments with "numbered and bulleted lists", previewing a list often (but not always) inserts an empty item .... jaclaz

The OP specifically stated he would be performing the operation on Win7... Sure, but in the specific case, by "pure chance" Windows 7 is a suitable environment to copy those floppies, the fact that he stated what he would like to use is meaningless in itself (with all due respect), the mentioned thread gives some examples of formats used in the DOS era that CANNOT (please read as CANNOT) be copied under *any* NT based system, let alone 7. If you prefer, in the DOS era, floppies were copied for years and successfully, with DOS programs, they DO WORK (because they DID work at the time). On newer Operating Systems new ways to manage/interface the hardware may (or may not) make an old format be copyable or not. ... or more simply he is open to suggestions and not necessarily "immobilized" in a "windows 7 only" paradigm... Sure , and I know Gilles Vollant since what? 1995 or so, and I have utter respect for him and for his work. As well, I really do like Porsche 911's, still a Toyota Hilux (or a wheelbarrow) may be more suitable for a given use: http://www.911cd.net/forums//index.php?showtopic=24502&st=12 and: http://www.msfn.org/board/topic/158990-switch-from-windows-xp-64-bit-edition-to-anything-else/?p=1017763 Just for your interest learn here: http://www.winimage.com/wimushlp/wini1a1y.htm http://www.serverelements.com/forums/viewtopic.php?t=64 WHY exactly Winimage (and/or any tool running under a Windows NT based system, unless particular drivers are used) is ABSOLUTELY NOT suited for some particular format of floppy (namely for a high capacity version of the DMF format), and however how (on the contrary) Winimage may have issues with the plainer DMF 1.68 format (which was actually used by MS for their "distribution" floppies, but that was "after" Windows 3.1) under Win9x. Additionally, especially with "low cost/poor quality" floppy drives, forcing them beyond track #80 may mean (it has happened) breaking the actual disc drive. To sum up, each tool (and OS) have it's own merits, advantages and disadvantages, the only thing that matters is getting somewhere (possibly where you want to arrive ), the path which you use to get there is not important. jaclaz

Fresh news: http://diydrones.com/profiles/blogs/faa-certifies-first-two-drones-for-commercial-use?id=705844%3ABlogPost%3A1348820&page=1 And no, you wont' need any particular device to notice one of these . And another (nice? ) approach: http://actu.epfl.ch/news/latest-video-of-the-daler-project-shows-a-walkin-2/ fly-and-crawl jaclaz

Let's say that "accuracy" is not particularly seen as an ESSENTIAL requisite by the good guys @nsslabs. On the report overview: https://www.nsslabs.com/reports/2013-browser-security-comparative-analysis-privacy-0 Too bad that in the actual report there is NO trace of Opera, let alone of Mr. Orlando Barrera: It's usually not a good idea to judge a book by it's cover, but still .... But let's see the actual content: Basically imagine that Philips (say) starts implementing in all it's domestic appliances a new additional protection against short circuits that depends on compatibility with the mains line (and that NO provider of electricity on Earth implements). Panasonic (say) has not this additional protection circuit (as it is NOT required by current standards). WHEN (and IF) the standard WILL BE changed AND the electricity provider WILL provide compatible electricity/lines, THEN the Philips' thingies WILL HAVE additional protection when compared to Panasonic's. NOW and UNTIL THEN, NO additional protection of ANY KIND is provided. By that time, most probably, the products will be end of line/obsolete. And BTW, I lied in the above example, it is not that the circuit is not already present in the Panasonic appliance, only, in order to save some electricity NOW, it is turned off and can be turned on by simply setting a little switch. I have rarely seen a report as worthless as that one. Among the other things, I am quite perplexed by the new, innovative definition of "honest compliance" in all my years I thought that you could put no qualification to "compliance", something is either compliant or it is not, and no one cares if such compliance is reached honestly, dishonestly, with good will or bad will, etc.) as long it is reached . jaclaz

Well, what about a flying shark jet drone? http://easytigermodels.com/index.php?main_page=product_info&products_id=28 jaclaz

From pi§§ed-off ranting to Zen in three steps, it must be a world record! http://en.wikipedia.org/wiki/If_a_tree_falls_in_a_forest http://www.101zenstories.com/index.php?story=21 jaclaz

Nowadays the issue is all about "quality". The quality of floppy discs is "very poor". The quality of floppy drives is "very poor". The original floppy discs for DOS or Win 3.x had not any particular "copy protection scheme", but in any case, what I would use (if the scope is that of making a set of backup floppy disc or floppy images) is a pure DOS program, one that would have been used at the time. Winimage is not a particularly good idea, not because it is not a good program, but it would be like shooting at flies with a cannon , Winimage is a tool to manipulate floppy images, in the hands of an unexperienced user it has the power to (inadvertedly) corrupt/change the floppy. Under DOS, I would personally use Venus: http://retro.icequake.net/dob/ or d.bosman's nice Dcopy program: http://users.telenet.be/jbosman/applications.html The dcopy program exists in a Windows (NT and later) version and though it won't be able to duplicate some "peculiar" formats under these OS's, it is "good enough" for "standard" floppies like the MS ones. In any case there is a pretty much exhaustive thread dedicated to the "specific matter": http://www.msfn.org/board/topic/136856-how-to-archive-old-floppies-for-access-under-win98/ including some info on 720 Kb/1.44 Mb floppy discs. jaclaz

I would add that data recovery is an "art" (or at least artisan work ). NO way *any* program will automagically recover *everything* and in any case they are ONLY tools, it's the hand that drives the tools that may make a difference between a total loss and a (almost) total success in data recovery. In any case, the FIRST thing to do is to make a "dd-like" or "forensic sound" image of the disk "as is", BEFORE *any* and I really mean *any* further step/attempt/whatever, as any and all tools, particularly CHKDSK and the like, may recover *something* but at same time prevent *forever* the recovery of *something* else, this way there is a "second chance". jaclaz

But you see, all Female connectors have odd numbers (evil) and all male have even ones (good), so they actually failed at failing! jaclaz

BUT IF they actually were after you, you would already have been pwned. WHY exactly do you think most exploits are called "zero-day" ? AFAICR all attempts to produce and sell the magazine "exploits monthly" failed miserably By the time you publish (or patch) something you are already dead . For NO apparent reason, a lolcat: jaclaz

Well, to be picky that is C6 (male) adapter to a C7 (female), i.e. a way to use a mains cable terminating with a C5 on a device that has a C8 ("Appliance inlet"). And yes, the good guys at IEC missed the lessons about "making easy mnemonics" at school..... The socket on the device is always male (and then maybe it's not even a "socket") while the plug at the other end of the cable connected to mains is alway female (and then maybe it is not even a "plug") , represented like this starts to make motre sense then with words: mains socket -< <- plug ----cable ---- <- C5 -< <-C6 device mains socket -< <- plug ----cable ---- <- C7 -< <- C8 device jaclaz

There is no such thing as 24 bit LBA , only 22 (never or rarely implemented) and 28 bit LBA! (and later of course 48) Some answers/things to read are provided on the other thread started by ROTS: http://www.msfn.org/board/topic/163554-48-lba-and-sata-drives-in-windows-9x/ jaclaz

Maybe down under , where they look at it upside down : o_o_o_it's name is "C5", actually IEC "60320-C5": https://upload.wikimedia.org/wikipedia/commons/b/b3/IEC_60320_C5.svg but a number of laptop mains adapters/charger are in "double insulation" and may use the 2 connector one (without earth), called "C7" or "IEC60320-C7": https://upload.wikimedia.org/wikipedia/commons/3/32/IEC_60320_C7.svg More: https://en.wikipedia.org/wiki/IEC_60320 jaclaz P.S.: Among the nice features of the board it seems like .svg images are prohibited.

You must have a defect on your keyboard. After you press the "." full stop or "period", you should also press the [ENTER] key, which will provide a Carriage Returne (or CR+LF) that will make your posts much more readable. Hey, you actually asked to be corrected . LBA is about "addressing", not about "cache". Traditionally hard disks had an addressing scheme called CHS that hit a limit at around 8Gb in size (1024*255*63*512). Then the LBA addressing scheme was widely adopted, but originally the LBA address had a size of 22 bits, in practice never used, and later of 28 bits. http://en.wikipedia.org/wiki/Logical_block_addressing This limited the max addressable size to around 128 Gb. Then the addressing scheme was extended to use 48 bits instead. To have a bigger than 128 Gb disk in Win9x/Me quite a number of things are needed/must be taken care of. You will need to go through here: http://www.msfn.org/board/topic/129027-big-hdd-48-bit-lba-thread-index/ Yes, all given links are related, but on second post dencorso put together a nice, simple "How to" that covers most cases. For a SATA disk you might need additional "special" tools, like Rloew's SATA DDO/driver (or whatever). You should post the specific make/model of the motherboard in order to get more "targeted" support. jaclaz

You mean old and rich people, nice chicks in bikini and decent weather also from Idaho to Michigan? jaclaz

It's meme time! The "us" is to be intended as "US" . jaclaz

Quote of the day: jaclaz

It must be a particular kind of telemetry. I mean, IF they had provided the option to use EITHER the Start Button (AND Menu) OR the NCI, they might have been able to count how many users actually preferred the one over the other, but since they forced everyone to use the NCI, I wonder WHAT THE HECK they registered through telemetry. jaclaz