jaclaz

I am actually not asking for "considerations", I am only asking for two (actually three) names we can all agree upon and that are understandable by users, and that make sense BOTH when we are talking of a superfloppy image and when we are talking of a hard disk volume, and I am not "insisting" in anything, only explaining my wrong (in the sense of simplified ) way to describe things in the given context, as you may know the graphical and mechanical representations are completely meaningless on any modern (meaning what, last 15 years? ) hard disk, so that maybe was CHS. We have THREE fields that I temporarily (and mistakenly) named: Sectors_per_Head Number_of_Heads Sectors_Before How should they be named? Sectors_per_Track Number_of_Heads Hidden_Sectors Is that OK? This only affects the actual variable names, I reserve the right to call them (as I understand them the wrong way) in the "textual part": Sectors per Track (Sectors per Head) Number of Heads Hidden Sectors (Sectors Before) I also asked, PLEASE for additional corrections to the two added sheets in the Workbook, and to verify and FILL the missing data. Can I have them? Or everything is already "perfect" (I doubt it, but I may have been lucky) jaclaz

Broken google? http://sourceforge.net/projects/smartmontools/ http://smartmontools.sourceforge.net/smartmontools_scsi.html jaclaz

Sure, sorry , I missed the "final" "*Number_of_Cylinders" (that is not a "field" in the bootsector) in the case of hard disk and "*Number_of_Tracks" ( or number of "whatever") (that is also not a "field" in the bootsector) in the case of floppy. Let's take the example of a "super-floppy" of 9,437,184 bytes, 512 bytes/sector. That makes 18432 sectors. Let's say that we have an "extended" ED disk drive , thus m/2/36 It has 256 "whatever #1"<-this is NOT a field in the bootsector it has 2 "whatever #2" (Sides?, Heads? Tracks?) <-this is a field in the bootsector It has 36 "whatever#3" (Sectors_per_Track? Sector per Head?) <-this is a field in the bootsector 9,437,184 is given by: Bytes_per_Sector*whatever#3*whatever #2*whatever #1 512*36*2*256=9,437,184 A partition/volume on hard disk 18432 sectors, 512 bytes each, totaling 9,437,184 bytes in size on a hard disk with a nx64x32 CHS geometry will have (let's assume that it is a very small second partition and that we do respect cylinder/head boundaries), first partition being: CHS 0/1/1-19/63/32 LBA 32/40928 will have: CHS 20/0/1-28/63/32 LBA 40960/18432 9,437,184 is given by: Bytes_per_Sector*whatever#3*whatever #2*whatever #1 512*32*(63-0+1)*(28-20+1)=9,437,184 The differences between the two bootsectors should be: whatever#3 (temporarily named "Sectors_per_Head") 36 vs 32 whatever #2 (temporarily named "Number_of_Heads ") 2 vs 64 "Sectors_Before" (or "Hidden Sectors") 0 vs. 40960 "Media_Type" (this should be OK ) 240 vs 248 How can the two "whatever" be named so that they are "self-explaining" in both cases? jaclaz

Can you expand (pardon me the pun ) on this? Which source do you have (in .SWM files)? This is usually OEM.... and AFAIK there is no explicit provision for .SWM files in the WinsetupFromUSBWithGUI (which I presume is what you tested, and - still presume - in the newest 1.0 beta7 version), it is likely that is the actual .SWM mechanism that somehow checks the install media. Easiest would be to procure yourself a stick for which there is a "flipping removable bit" tool (or verify if there is one for your current stick) and flip the bit. jaclaz

Are you joking or what? http://www.embeddedmarket.com/products/USB-to-TTL-Converter-Module/ http://www.embeddedmarket.com/Products/RS232-to-TTL-Converter/ Do you want me to draw a map for you? jaclaz

OK, I'll try again. In a typical hard disk with a CHS geometry of nx255x63 in the MBR there are two fields that are normally called (see also my old page here): http://jaclaz.altervista.org/Projects/USB/USBstick.html bHead BHd Starting Head Starting Head Starting Head and eHead EHd Ending Head Ending Head Ending Head in populated entries, and with the "old" alignment standard, in the "BHd" field there is normally 1 (in first partition, because of the hidden first Track ) or 0, whilst in the "EHd" one there is 254 (as heads are numbered in CHS starting from 0). In the corresponding bootsector, the field "Number of Tracks" or "Number of Heads" is 255. And two called: bSect BSec Starting Sector Starting Sector Starting Sect and: eSect ESec Ending Sector Ending Sector Ending Sect in populated entries, and with the "old" alignment standard, in the "BSec" field there is normally 1, whilst in the "ESec" one there is 63 (as sectors are numbered in CHS starting from 1). In the corresponding bootsector, the field "Sectors per Track" or "Sector per Head" is 63. To me in this context of bullding volumes that can be either a volume on Hard disk or represent a "superfloppy", a Head or a Track are exactly the same thing, for which two different names are used, one for floppies and one for Hard Disks. The size of the volume in bytes is given by: Bytes_per_Sector*Sectors_per_Head*Number_of_Heads or: Bytes_per_Sector*Sectors_per_TracK*Number_of_Heads No problem whatsoever in naming the field "Sectors_per_ Track" , but then also the "Number_of_Heads" should become "Number_of_Tracks", thus losing any logical connection with the MBR. Sure , dencorso already posted the algorithm used and the little spreadsheet I was talking about was a reversing of that algorithm to check if the Volume serial had been tampered with, by detecting possible dates/times that may have generated the serial and verify if they were within a possible timeframe. This applies to DOS but NOT to NT systems, for which the algorithm is not AFAIK known. Here are some details: http://www.forensicfocus.com/index.php?name=Forums&file=viewtopic&t=2134 jaclaz

You didn't read them "hard enough". FORGET about your current project. Create a new batch file with ONLY these commands, as CLEARLY stated on the given page: http://www.robvanderwoude.com/battech_redirection.php @ECHO OFF ECHO This text goes to Standard Output ECHO This text goes to Standard Error 1>&2 ECHO This text goes to the Console>CON and test it as explained there. Then try with: @ECHO OFF FOR /F %%I IN ('DIR/A-D/B HFMER') DO ( ECHO Copying %%I ECHO No redirection: MOVE HFMER\%%I %SP6%\sp6 ECHO. ECHO Redirection of DEFAULT "Standard output" to NUL: MOVE HFMER\%%I %SP6%\sp6 >NUL ECHO. ECHO EXPLICIT redirection of "Standard output" to NUL: MOVE HFMER\%%I %SP6%\sp6 1>NUL ECHO. ECHO EXPLICIT redirection of "Standard Error" to NUL: MOVE HFMER\%%I %SP6%\sp6 2>NUL ECHO. ECHO EXPLICIT redirection of BOTH "Standard output" "Standard Error" to NUL: MOVE HFMER\%%I %SP6%\sp6 2>&1>NUL ) jaclaz

Learn about "Standard Output" and "Standard Error" and their redirection: http://www.robvanderwoude.com/redirection.php (already given to you) AND: http://www.robvanderwoude.com/battech_redirection.php jaclaz

Well WIN TO FLUSH is probably WINTOFLASH. But athough I don't see why you haven't asked for help on their Forum , the issue is most probably (please read as definitely) in the way you formatted the USB stick. Use RMPREPUSB (and nothing else) to partition and format the USB stick: http://sites.google.com/site/rmprepusb/ Preferrably (but of course not at all mandatory ) use our own app to create the Windows 7 base for install: http://www.msfn.org/board/forum/157-install-windows-from-usb/ (BTW it already includes RMPREPUSB) jaclaz

Probably stupid question, but what happens with a "plain" dd-like tool? What happens with MHDD? http://hddguru.com/software/2005.10.02-MHDD/ Or with ZAP? http://www.digitalissues.co.uk/html/os/misc/ibm-wipe-zap.html Also, I would try the whole set of thingies here: http://www.shlock.co.uk/Utils/index.htm the diskimg and omnidisk for DOS first Also maybe you can create your own parameters for NFORMAT http://toastytech.com/files/nformat.html jaclaz

A "J" in top left of the screen (or a flashing cursor) is usually a problem with the bootsector. (more specifically it is often connecte with unbalanced CHS/LBA and or with geometry of the filesystem) HOW (meaning BOTH): WHICH tool HOW EXACTLY did you use it was the USB thingy partitioned/formatted? More generally describe in better detail, WHAT (which device) are you attempting booting from USB, it's size, the filesystem used on it and under which OS did you prepare it. jaclaz

@dencorso Yes, the "FREE" options are used as "separators", to divide three "logically grouped sets": three common floppy formats (compatible with the El-torito standard) three max floppy formats (compatible with the rloew's findings on the El-Torito standard) All the rest (less common floppy formats) *any* of them can be used, they correspond to "blank" values... Since Multibooter is also around here , I would ask him to post a set of the formats/sizes (and OTHER data) of the hardware he is playing with, like the LS-120/240, the 32 M floppy and the ZIP and clik (PocketZip) discs.... Yes, that is what I find the most important things and that I hope Drugwash will implement in his nice tool, the problem is not really to create a bootsector BPB, but rather calculating "reasonable" (if not "right" values). I have changed the .bin to something less common, .t#p Thanks for testing, but I am interested in your (and everyone else's) ideas/comments/corrections on the "naming" and ".ini" idea. As well, the "Sector per Head" is "intentional", since we have (on hard disks) an addressing convention called CHS (and not CTS) and AFAIK/AFAICR "Track" is used almost exclusively in conjunction with "real" floppies, I thought it to be more descriptive, but this is part of the naming convention that I would like to get a "common agreement upon", just like "Sectors Before" vs. "Hidden Sectors". About serial, is not a problem to calculate a "random one", I even have *somewhere* a (clever ) spreadsheet I made to calculate (for forensic scopes) the probabilities of a serial to be an actually "kosher generated" one or a "random" (please read as "counterfeited" one. Since the algorithm is (partially) reversible something can be done in that sense, but this is an alltogether different topic. jaclaz FAT_make_08.zip

@all Can you please review the attached version of the spreadsheet? I added a tentative way of "classification" and naming and an example .ini, as I am thinking we can use a .ini file to create a "database" of known formats and/or let the user choose only a subset of the available and/or have a common "interchange" format between different utilities/scripts. Please do review the "known" values and the "ranges" besides the actual "naming proposal", and let me know of any mistake, missing piece or whatever you think about the idea. Please , no comment/proposal involving directly or indirectly any of: access (or any other database format) xml java .net jaclaz Attachment removed, see a few posts below.

Not that it matters, but are you sure that Gurgelmeyer made a SP5 for Windows ME jaclaz

12 (twelve) easy steps: You find a compatible PCB board. You verify it is compatible. You check again. You find out that you got a wrong one and need to find the right one. You find a compatible PCB board. You verify it is compatible. You disassemble the PCB from the disk. You de-solder the eprom from the "old" one. You de-solder the eprom from the "new" one. You solder the "old" eprom on the "new" PCB. You assemble the "new" PCB on the disk. You test the disk to find out that it doesn't work as well. A Q&A that may help you : Q.: WIll changing the PCB (provided that I am able to perform it's swapping correctly and without frying anything) help in *any* way to rec ove the disk or the data in it? Short Answer: A.: NO. Long Answer: A.:NO, it will simply represent an (expensive) exercise in futility, with no practical benefit of *any* kind and additionally carries with it the risk that once done even a professional won't be able to get anything out of it. If you have a bad flu, you do not cast your left ankle into plaster. If you have a broken left ankle you stop walking to avoid putting your weight on your left foot, and you normally don't take antibiotics. jaclaz

Clarification: Your laptop probably has a SATA disk and your source does NOT contain a suitable driver. If this is the case, you need to integrate the appropriate driver (or the whole Mass Storage Driverpack) to your source BEFORE creating the USB thingy. jaclaz

No iso is "extracted", No "more work". The .iso is mounted in a virtual drive. Actually, IF it was a conventional disk drive using a .iso should put LESS stress on head/arms . jaclaz

I like the screen shot of BootMaker. It is a little OT, but would it be possible to turn BootMaker into a track-0-writer for removable media, so that it could, for example, write/re-create track 0 on a bulk-erased/de-gaussed removable media disk, e.g. a bulk-erased LS-120 diskette? Such a tool could be very useful for re-initializing the rare special removable media of dual-format drives in general (e.g. also Floptical, Sony HiFD, Caleb UHD144). Unless I am mistaken, we then need to draw another line. Are we talking of a DOS track-0-writer (which is doable) or of a Windows NT one (that will get us into the drivers trouble)? @Drugwash: and: http://alter.org.ua/en/soft/win/floppy/ JFYI. jaclaz

And the answer depends on the actual OS you want to run from it, to how actually PLOP behaves with your hardware and existing BIOS, how this "interacts" with the add-on card, how the actual OS sees it and probably a few other variables.... Even Win95A vs. Win95B vs. Win95C open way to different situations. jaclaz

Historically, there have been a number of BIOSes that did have problems with Hard disk emulation. An example is (was? ) the BOCHS (read Qemu) one: http://reboot.pro/3890/ http://reboot.pro/3890/page__st__46 but similar issues are more common that you may think, of course mostly on very dated BIOSes. DELL's are notoriously a PITA in about everything concerning booting them but also Acer and other makers have their own "queer" things, examples (not directly related, though): http://reboot.pro/10503/ http://reboot.pro/12942/ Because its fun? Because it can be done? If you mean an actual *need* there isn't any AFAIK, nowadays you can boot a grldr no-emulation CD or a 1.44 floppy emulation one booting grub4dos and you can map almost *anything* to *anything* else. If you want an example of a project that may make use of this, it's here: http://reboot.pro/10373/ Given the anyway limited size of the possible image with 2/18 or 2/36 geometry, FAT16 is iMHO a good choice, FAT12 is, as seen, a bit stretched out and FAT32 is pointless (besides not being NT 3.5/4.0 and DOS <=6.22 compatible), whilst NTFS sounds "looking for troubles" (unneededly). Take all the time you need (and even more ) there is no pressure. Well, right now (I mean the preliminary version you posted) doesn't do much, so it's hard to say how what you added to it in the meantime can be bettered or enhanced. The posted version, besides Writing capabilities, is missing IMHO what I tried (and still try) to add to the worksheet: a set of pre-configured settings for most (if not all) floppy and "super-floppy" formats a set of suggested settings for the "FREE" formats Your nice app, unless you add these features (and/or other ones) won't have much more practical functionalities (exception made for a nicer interface ) than an existing app, such as Roadkil's BootBuilder: http://www.roadkil.net/program.php/P3/Boot%20Builder BTW, your nice program is not necesarily connected to the use of a floppy or super-floppy image on a CD, it could (and should) be IMHO a "general" tool to experiment with floppies and super-floppies. jaclaz P.S.: I am attaching last version of the spreadsheet and a small batch that may possible be useful (needs dsfo and dumphex) FAT_make_06.zip getFAT1xBS.zip

Let's make a deal. You write a CABINET.DLL replacement. You make sure it works as expected. You also fix SETUPLDR.BIN and NTLDR (if needed ) I will take care of CABARC.EXE and EXTRACT.EXE, one way or the other. The compression used is VERY SCARCELY documented AFAIK/AFAICR. Maybe you can find something of use around here (and given links): jaclaz

Yes this is perfectly consistent with "2nd" version of the ZIP, with the ARMD jumper set, see here: @rloew Yes, I know what you mean, but the fact a device is mounted a A: or B: may depend on several factors, like BIOS (or bootmanager) and/or actual OS drivers (if any), so it is not an "objective" way unless you actually tried the device on a given machine and you see which letter it gets under a given OS. @Multibooter Since the ED 3840K floppy (as image) is inside the El-Torito specs, I doubt you can consider it a "super-floppy", after all: it is is inside the specs it is supported by most CD burning or .iso making application the actual hardware "existed" and was produced in great quanitites, I remember a period when ALL original IBM's, desktop and laptop had an ED floppy drive. As a (completely void of any relevance , but interesting as a reference ) example the known bootmanager Syslinux/Isolinux considers these as "normal" floppies, and all the rest as "super" or "queer" : Anyway, as said, no problem whatsoever, we can draw "the line" (if needed) wherever you prefer. jaclaz

WHICH manual? Including PROPER GROUNDing? Re-check everything, following EXACTLY the advice given in the read-me-first: Does that happen BEFORE you try CTRL+Z, right? jaclaz

As always Yzöwl is right, if you have no space between the 1 and the > you will redirect standard output to file. You can always leave the spaces and post-process with gsar changing [sPACE][CR][LF] to [CR][LF] .... Or see if redirection BEFORE line works, see point #(3) here: http://www.robvanderwoude.com/redirection.php jaclaz

If we have to draw a line somewhere, I would draw it, as hinted, right after the 2M 4003.9 Kb size, since that is "the biggest floppy you can have on actually largely mass produced hardware using standard floppy media" (a bit lousy as definition , but not worse than many others ). While the LS-120 did have some diffusion, the LS-240 had so short a lifetime that the actual numbers are really low AFAIK (and only the LS-240 could make the 32 Mb floppy). But I am with rloew, to me *anything* which first sector is a MBR and holds a partition table is a "HD-like device" and *anything* which first sector is a bootsector is a "floppy-like device". jaclaz