jaclaz

I am not at all "current" with Windows 7, it is well possible that it doesn't work as I remember, and as you describe. I would try, after having created the first partition of a given size, to hide it, disconnect and re-connect the stick, then try creating the second one. I am sure that only one partition can be accessed/mounted at a time in any Windows NT, unless the filter driver is installed, but if you each time you hide the "other" you should be able to choose which partition to access. However, I would separate the problem in two: 1) use the filter driver 2) try flipping the bit 1)I don't know if cfadisk.sys or dummydisk.sys are installable on Windows 7. If they are, it is possible that you have some "wrong" settings in cfadisk.inf (or corresponding files). You can try using this way: http://www.911cd.net/forums//index.php?showtopic=22795 which is a "generic" not "specific stick" way to have the filter working. Most probably you need to disable driver signing, but cannot say. If the filter driver approach doesn't work, you can always use manual partitioning of the stick, by using an image of it and/or a VM, but let first see if the cfadisk can work. 2)Maybe there is some misunderstanding. If you click here: http://www.mydigit.cn/mytool/ChipGenius.rar you should get a chipgenius.rar file, open it in 7-zip (or winrar) and extract from it the files: ChipGenius.exe Chips.wdb double click on chipgenius.exe, it is a GUI tool. Close it. Insert your USB stick. Re-run it. Select in the list in the upper window the USB stick that should be detected. Read in the lower window what Chipgenius knows about it. Post this latter info. I can try helping you find the appropriate "Manufacturer tool (if any available). jaclaz

IBM thinkpad's (read Lenovo) normally use a "strange" 240 heads geometry (instead of the "normal" 255 one). The flashing cursor is normally related to a mismatch/unbalancing between CHS and LBA addresses. What you can try to do is to patch the bootsector to avoid checks for CHS, a way through grub4dos is detailed here: http://www.911cd.net/forums//index.php?showtopic=23844&st=9 derived from an original idea by Clemens Fruhwirth: http://www.911cd.net/forums//index.php?showtopic=21702&st=129 http://blog.clemens.endorphin.org/2007/12/removing-chs-based-access-from-windows_3170.html which dencorso nicely compiled as a .exe: http://www.boot-land.net/forums/index.php?showtopic=8528&st=21 First thing you need to do is to check the geometry seen by grub4dos, press C and then issue: geometry (hd0) and geometry (hd1) and report feedback. Also check the data in the current partition table. These Lenovo's are making some troubles, cannot really say if we are missing something in the way they boot/behave. Compare with these: http://www.911cd.net/forums//index.php?showtopic=23408&hl= (solved) http://www.boot-land.net/forums/index.php?&showtopic=5306&st=215 (solved) http://www.boot-land.net/forums/index.php?showtopic=11320 (UNsolved) jaclaz

It is more probable that the BIOS doesn't expose the (possibly SATA) disk properly. What happens in "plain" grub4dos? Try pressing C to access command line, then issue a geometry (hd0) and a geometry (hd1) jaclaz

@bookworm The Windows NT FAT32 driver, was a commercial product by Wininternals (the read/write version), with quite a bit of limitations, including that of NOT being "bootable": http://web.archive.org/web/20020124185910/www.sysinternals.com/ntw2k/freeware/fat32.shtml but it was available a Read Only driver, with further limitations: http://articles.techrepublic.com.com/5100-10878_11-1047372.html Direct link to the freeware read only version: http://web.archive.org/web/20020124185910/http://www.sysinternals.com/ntw2k/freeware/ntfswin98.shtml The given post by fdv is pointing (point 7b) to a second driver from Ashedel (and the links is working allright): http://ashedel.chat.ru/ http://ashedel.chat.ru/fat32/ http://ashedel.chat.ru/fat32/fastfat32.rar which is said to provide bootability, but your mileage may and will vary. jaclaz

But as always some dismbiguation is needed. Do you want to INSTALL/RUN 2003 ON USB? (which is what the link fdv gave), more here: http://www.msfn.org/board/index.php?showtopic=122443 http://www.boot-land.net/forums/index.php?showtopic=9830&hl= In any case the new service to set properly the USB keys is recommended: http://www.911cd.net/forums//index.php?showtopic=22473&hl= or Do you want to run 2003's SETUP FROM USB? For which there are several methods in a dedicated Forum: http://www.msfn.org/board/index.php?showforum=157 jaclaz

Basically, you are trying to adapt an oldish solution to a newish, DIFFERENT OS, and guess what? Result is DIFFERENT. AFAICR Windows 7 had not one problem in the world in partitioning a drive marked as removable through diskpart, last time I checked. Now that you have verified empirically that applying changes to a given set of instructions may not always work, if you explain WHAT you are willing to do/create (as opposed to HOW to do/create it) I may give you some more suitable links/advice. Personally, since I hate all this mess with "Removable" vs. "Fixed", I tend to "flip the bit" in the hardware, whenever possible, and be done with it, as you may have found out in the thread you are referencing. jaclaz P.S.: Just to keep things as together as possible it seems like SPFDISK has a new home (and a much newer version - March 2009): http://spferng.myweb.hinet.net/ thanks to halohalo: http://www.msfn.org/board/index.php?showtopic=105936&st=487 Info is quite readable with google translate: http://translate.google.com/translate?u=http%3A%2F%2Fspferng.myweb.hinet.net%2F&sl=zh-CN&tl=en&hl=&ie=UTF-8

Good , that was essentially the reason why I posted it, to show you how giving partial informations is unuseful. It was intentionally "broken" to see if instead of trying to understand how it can work and write your own, you would have - as expected - simply tried to run it from a copy and paste. Try this one : @ECHO OFF SETLOCAL ENABLEDELAYEDEXPANSION SET FLAG=0 FOR /F "tokens=* delims=" %%? IN ('TYPE my_original_batch.cmd') DO ( IF "%%?"=="::BEGIN_REMOVE" SET FLAG=1 IF "%%?"=="::END_REMOVE" SET FLAG=0 IF !FLAG!==0 ECHO %%?|FIND /V "::">>my_edited_batch.cmd SET FLAG ) DEL my_original_batch.cmd REN my_edited_batch.cmd my_original_batch.cmd Hint: Check in the previous one spaces after the SET FLAG jaclaz

If I may, a small addition, there are two "BOOTCFG" programs, one in Recovery Console and one in "normal" XP with slightly different behaviour/switches. Most of the references you find around, including those on MS site are for the RC version, here is reference for BOTH: http://ss64.com/nt/bootcfg.html It seems like it's use is documented for XP only from RC : http://support.microsoft.com/kb/291980/en-us whilst on Server2003 it is detailed for both programs: http://support.microsoft.com/kb/317521/en-us These are also interesting: ( the "normal" bootcfg is in XP PRO but not in Home) http://support.microsoft.com/default.aspx?scid=kb;en-us;289022 http://support.microsoft.com/kb/303980/en-us jaclaz

And again, you should explain the problem you are having (as opposed to the way you think it should be solved). There is no problem in removing lines, as long as they are "unique" in the batch, but since you probably have several lines like "ECHO." you cannot use "ECHO." as a simple argument for FIND or FINDSTR. Also parsing the batch can be simple or difficult depending on it's contents. An example is this one: Running something like this: SET FLAG=0 FOR /F "tokens=* delims=" %%? IN ('TYPE my_original_batch.cmd') DO ( IF "%%?"=="::BEGIN_REMOVE" SET FLAG=1 IF "%%?"=="::END_REMOVE" SET FLAG=0 IF !FLAG!==0 ECHO %%?>>my_edited_batch.cmd ) DEL my_original_batch.cmd REN my_edited_batch.cmd my_original_batch.cmd Will remove anything between the two "tags", but it simply won't work if you have redirection or piping symbols in your original batch. jaclaz

Nice find! Here is an explicit link to the "other thread", where all the info is, just in case friendly names will be botched again at next board update: http://www.msfn.org/board/index.php?showtopic=143980 jaclaz

Maybe a suitable temporary solution: http://www.intelliadmin.com/index.php/2006/07/disable-floppy-drives/ jaclaz

As a side note, and only as a "philosophical" point, with no practical use whatever , the only "bad" thing that can happen if you try mkdir giving an existing directory is that an error message will be output to STDERR, I have no idea (but it may be worth a test ) if by unconditionally making the dir anyway would it be faster than looping to the "directory" IF NOT EXIST, when a great number of file needs to be copied. I.E. something like: FOR %%? IN ( "%ProgramFiles%\Winamp\Plugins\gen_MSN.dll" "%ProgramFiles%\AIMP2\Plugins\gen_msn7.dll" ) DO CALL :Copyfiles %%? GOTO :EOF :Copyfiles MD "%~dp1" >NUL 2>&1 IF NOT EXIST "%~dpnx1" COPY "%~nx1" "%~dpnx1" GOTO :EOF jaclaz

Yes , as said, if your drive motor does not spin up when it is connected to power (even with NO data cable connected) and beeps, it is ANOTHER problem from that discussed on this thread, so please start ANOTHER new thread, where maybe it will be possible to help you without further cloggering this thread. In a nutshell, when a drive of this kind is powered it should: start spinning try to read calibration data NOT beep even if it's "bricked" with BSY and LBA0 problems... This is not the behaviour you described, hence this is not the right place to talk about this problem. Read here: http://forums.seagate.com/t5/ATA-and-Serial-ATA-drives/Seagate-7200-11-Drive-Beeping/m-p/39439 then start a new thread about your issue. If this started happening since when you have removed the PCB ONLY, (and it didn't beep and it did spinup before) it means that somehow contacts are not as they should be. In other words, carefully and thoroughfully clean contacts, completely re-assemble the drive an PCB, and make sure that the drive operates "normally" (meaning NOT beeping AND spinning up) then check if it has a BSY or LBA0 problem. Until you are in such a condition, this is simply not the appropriate thread to try and help you. jaclaz

Please read, slowly, point #1 here: Pseudo-code: IF NOT LBA0 THEN IF NOT BSY THEN GOTO :Start_New_thread Your drive has probably the motor or motor controller stuck, nothing connected with the problems this fix can solve. @Phenom9 No, we cannot be 100% sure of anything, this is somehow a "hack", it is very possible that a little something has changed, but same applies to you, start a new thread if you need help in recovering those spanned volumes. jaclaz

Find the installation directory where files were copied by the original install. If the file HSBR-MP.EXE or the README weren't deleted, it is likely that they are part of the problem. Windows search for "HSBR" should be enough. Once you find these files, try searching the registry for their name. Also, there quite a lot of "registry fixing" programs that can remove an app from the list of installed apps, Regseeker comes to mind: http://www.hoverdesk.net/freeware.htm jaclaz

Yep, I mean which size is it detected with? If 0 you have a LBA0 problem: Clicking sound may be connected with a problem with the hard disk (lost calibration data) which is NOT resolvable without some specific software/hardware and knowledge. jaclaz

Good. Read this SITE (and yes, I don't mean a page on the site, but the WHOLE SITE): http://www.ntfs.com/ You may as well start from here: http://www.ntfs.com/ntfs-permissions-ntfs-history.htm and clicking Next a few times, but it won't help you much (and besides, it has NOTHING to do with the actual error you got). Strangely enough , in a few, very, very rare cases, MS error messages actually mean what it is written in them: Try googling for the above sentecnces, there are several reasons why this can happen, NONE of which afaik actually connected to the $Secure file. jaclaz

What scares me is, once you can see the "$" folders, what you would do with/to them. Strangely enough they are hidden for some good reasons. Can you detail your intended actions, once you can see them? jaclaz

Hmmm, maybe I was wrong, and actually TESTDISK can "see" the drive even if it is in LBA0 or BSY mode, but it would be "strange". And no, I guess that for the moment the deeper search is pointless. Please reply to my last questions: I still think about an intermittent problem, like a connection or the actual hard disk going bad. Is it noisy? Does it click repeatedly? jaclaz

Try LATEST: http://www.boot-land.net/forums/index.php?showtopic=8804&st=0&start=0 0.0.1.18 right now. @ilko Since you have some machines that do work with firadisk and some that won't, have you had a chance to test WinVblock? http://www.boot-land.net/forums/index.php?showtopic=8168 Maybe it works with 2K3 on the "pesky" ones? jaclaz

It may also be an intermittent (cable/connection) problem and/or a bad sector somewhere - fixable with CHKDSK or other utility. JFYI, about 0x000000ED: http://www.boot-land.net/forums/index.php?showtopic=11320&st=7 (AND given links) jaclaz

Well, first link is about the "Hitachi Microdrive Filter Driver" actual name of the driver is cfadisk.sys, the archive is named XPfildrvr1224_320.zip, or sometimes XPfildrvr1224.zip it can be found here: http://xpefiles.com/cs/files/ http://xpefiles.com/cs/files/folders/hardware/entry616.aspx http://xpefiles.com/cs/files/folders/616/download.aspx JFYY, there is another similar driver, widely used called dummydisk.sys, by Anton Bassov: http://www.codeproject.com/KB/system/soviet_direct_hooking.aspx and there is a "reversed driver" called rdummy.sys (making a fixed drive appear as removable) which is available inside USB_multiboot: http://www.msfn.org/board/index.php?showtopic=111406 Second is a direct link to a version of spfdisk, as you found out, on the home page of spfdisk: http://spfdisk.sourceforge.net/ which is now DEAD (since what? 2008?) but can be still accessed through The Wayback Machine: http://web.archive.org/web/*/http://spfdisk.sourceforge.net/ http://web.archive.org/web/20080317162014/http://spfdisk.sourceforge.net/ http://web.archive.org/web/20080317162014/http://spfdisk.sourceforge.net/Spf2K3tE.exe See this also: http://www.iceteks.com/articles.php/spfdiskreview/1 The C should mean Chinese version, the E means English, so I guess you got the wrong one. The actual SPFDISK.EXE should be 2006-09-05 01:49 119662 bytes in side. Generally speaking, if you spend some time in this, you will be surprised about how many people "rip" info and posts without mentioning the original Author. jaclaz

Just for the record. An original siemens cable for models C55 or M55 should look like this: http://mobilesupportservices.co.uk/shop/catalog1/product_info.php/products_id/8523/language/pr The "official" name is DCA-512 (USB version) The connector on the phone side: http://www.gsm-support.net/en/connector-for-siemens-c55-12-pin-p1127 Is rather "open" and the pinout is known: http://pinouts.ru/CellularPhones-P-W/siemens_c55_pinout.shtml (find in the above a list of models that use the same connector and hopefully which data cable is compatible) Just like it happens with Nokia cables there are a myriad of cables types/brands, examples: http://www.fonefunshop.co.uk/datacables/siemens.htm#data of which a few need an external battery. So actual mileage may vary. jaclaz

To clarify the meaning of my post you cited, that lists the available drivers: cfadisk.sys dummydisk.sys (and rdummy.sys) they are for 32 bit only, and should work under Win7 allright, only I never tested them on that OS, nor I have seen a report about them. The Lexar boot-it utility works ONLY with sticks by Lexar or that use the same controller the Lexar uses, see here: http://www.911cd.net/forums//index.php?showtopic=21850 There are other utilities (in practice EVERY controller has one, problem may be finding it, and very few are as simple to use as the boot-it program ). Here is where you should start: http://www.boot-land.net/forums/index.php?showtopic=4661 with the info thus gathered start looking here: http://flashboot.ru/index.php?name=iflash A couple examples of a Manufacturer's Tool search and use: http://www.msfn.org/board/index.php?showtopic=135120 http://www.msfn.org/board/index.php?showtopic=137990 BTW, if you ONLY have one copy of your (precious) DATA on a USB stick, it's time for you to back it up, NOW. jaclaz

Here there is a "full" catalog: http://www.boot-land.net/forums/index.php?showtopic=1507 IMDISK FIRADISK WINVBLOCK are the "in-house" thingies, but Gavotte's should work as well, just like many of the othere ones mentioned, it all depends on the use you intend for it. jaclaz