jaclaz

Answer is YES again. Ten steps tutorial here: http://www.911cd.net/forums//index.php?showtopic=16713 (of course you need to keep the 16bit install files) Another possible solution is the one only hinted here: http://www.911cd.net/forums//index.php?showtopic=17425 jaclaz

Yes, see this LOOOONG thread here: http://www.911cd.net/forums//index.php?sho...c=14181&hl= Find any of Dietmar's posts, in the signature are links to the various tutorials. Check also in the same thread posts by martin and by sisal, and on the board, look for threads started by bshoangl1. For howto's to make the USB stick bootable search for posts by me (jaclaz). jaclaz

@nicke85 Sorry, but you seem to miss the point in making mindows, if you re-add: Win 98 Explorer Win 98 Shell32.dll you will need to re-add also ALL related files and the IE integration. If you also re-add sound support and Direct-X, you will most probably end up with a freshly installed Windows 98. jaclaz

I don't think that you can do that, because you cannot sum "intermediate" sheets. But why dont you make it simple: On Feb =Jan!I11 On Mar =Jan!I11+Feb!I11 etc. jaclaz

Yep, the idea was just to check it wasn't Explorer related. Next thing to check would be if you are (under current login) the OWNER of source files AND what level of permission is granted to your login on BOTH source and destination. A thing you can try (WARNING, using second one is risky business), is to use programs like these: http://grubletrang.com/Software.aspx?app=FreeFile http://grubletrang.com/Software.aspx?app=PowerPrompt To check if the files are busy, and to try using COPY, XCOPY or YCOPY from a command prompt with SYSTEM credentials. jaclaz

Happy to be of help. Please do post results of your tests. jaclaz

@oscardog The one you have is a very old link, of the time when the project was really at an early stage. Valid links are listed here: http://www.boot-land.net/forums/index.php?showtopic=14# There is not much documentation on it, most info can be found in readme.txt inside package, the syntax is the same unless differently stated, of GRUB: http://www.gnu.org/software/grub/ Additional info can be "extracted" from my posts on 911CD forum. jaclaz

Ghost otr Acronis Trueimage. And if you cannot afford Commercial programs, PING (Partimage Is Not Ghost): http://ping.windowsdream.com/ jaclaz

Compuapps swissknife: http://www.compuapps.com/download/Swissknife/swissknife.htm PING: http://ping.windowsdream.com/ jaclaz

FYI, on the 911CD forum a few automation scripts: http://www.911cd.net/forums//index.php?sho...c=17187&hl= and this method of combining A SDI with a raw drive image have been developed: http://www.911cd.net/forums//index.php?sho...c=17628&hl= jaclaz

Without doubt Grub4dos, as it has BOTH the abilities of booting from RAM with internal commands AND by using memdisk, + a bunch of VERY interesting "direct booting" features, possibility of integration with NTLDR, and to be used (GRLDR) as a no-emulation bootsector for CD's. Have a look at these threads on 911CD: http://www.911cd.net/forums//index.php?showtopic=16980 http://www.911cd.net/forums//index.php?showtopic=18231 Search foor "Grub4dos" on the board for more. jaclaz

There is a way to change system drive letter, though not so straightforward: http://www.petri.co.il/change_system_drive..._windows_xp.htm http://www.dougknox.com/tips/xp_drive_letters.htm jaclaz

Yep, sure. Easiest: http://www.911cd.net/forums//index.php?sho...c=16543&hl= jaclaz

The correct procedure is the one that is not working, at the moment, i.e. fdisk and Format the card, sys files onto it. It is possible that some of the limits that on some PCs/motherboards apply to USB flash drives do apply on PCMCIA CF card booting. These include: FAT16 and not FAT32 FAT16 06 (BIGDOS) and not 0E (V-FAT) Volume size, maybe the 1,2 Gb is too big and finds some kind of "barrier". What I would try first: 1) Fdisk the card using Freedos FDISK with one active primary partition about 500 Mb FAT16 http://www.23cc.com/free-fdisk/ 2) Format the card using the /s switch (that copies the system files) If it does not work, post again, there is another way by making a virtual drive (image file) and binary copying it to the CF card, and another one by using a bootloader to boot to a disk image in RAM. jaclaz

Sorry, wrong, the MBR "picks" a partition BOOTSECTOR, the partition BOOTSECTOR "picks" NTLDR. Since you can boot from floppy, the MBR is probably OK, the boot.ini on the floppy has an entry like multi(0)disk(0)rdisk(0)partition(1)\Windows that work, this means that the partition data is read allright by BIOS. The problem could be the bootsector. Nothing for the moment, you should use it to save the BOOTSECTOR, than copy the backup bootsector over its original position. Details are in the link in my previous post. However, before the above, do download this freeware utility: BEEBLEBROX http://students.cs.byu.edu/~codyb/ and use it to check both MBR and boot record, helping yourself with the info found here: http://thestarman.pcministry.com/ If you don't feel like using a hex editor directly on the system, you can use testdisk to copy backup bootsector: http://www.cgsecurity.org/wiki/TestDisk http://www.cgsecurity.org/wiki/Data_Recovery_Examples jaclaz

Interesting, but not really needed there are standard ways to do it: @jftugaFor future use, you are getting the R's because the underlined part is wrong: The variable is %%R, not %R: jaclaz

NO, sorry but you have it wrong. The OLD format from DOS did that. Under NT/2K/XP/2003, whenever the format command is used, the bootsector for booting NTLDR is written everytime. It is quite difficult however to help you without exact information, since we are not allowed to ask HOW it happened, maybe you can post WHAT it is now, by answering the folowing. 1) The partition you call C:\ is a PRIMARY one? 2) The partition you call C:\ was modified by some third party tools (like Partition Magic, Acronis or the like?) 3) Was it the result of using the CONVERT tool to convert it from FAT16/32 to NTFS 4) Are you confident with using a hex/disk editor? 5) Have you an alternate method to access the system (mount the drive in another PC, Live Linux CD with NTFS support, BartPE)? A NTFS partition has a "backup" bootsector at the END of it: http://thestarman.pcministry.com/asm/mbr/NTFSBR.htm#BSback If the partition is a primary one, you just copy it to the first sector, make the partition Active, copy to it NTLDR/BOOT.INI/DETECT.COM and if needed NTBOOTDD.SYS and you are done. jaclaz

just an idea, mind you, but it seems like you have a bad screen resolution/setting/frequency range for the "other" user. You can try logging directly with the "other" user credentials and temporarily set the display as VGA 640x480 16 colours .... jaclaz

Yes, if you have a look at http://www.everythingusb.com/forums/ you'll find hundred of reports of "smart" people buying LARGE sticks from "occasional" sources, like some e-bay auctions, for a SMALL price and later find that the stick is a fake one. But I thought that the smallest was 16 Mb, not 8Mb, so maybe this is not the case. jaclaz

by the way, it seems almost completely not needed. I mean: Since the idea is to replace ntldr with grldr (not grub, that won't work), most probably following this idea: http://www.911cd.net/forums//index.php?showtopic=18045 the ntldr to be replaced must be the one the machine usually boots from, which is 99,9999% in First Active Partition of First Harddisk (read C:\). And this also explains why the original script has drive letters the "wrong" way.... ... and the way it works, "overwriting" previous positive finds in other partitions While I was thinking about it, I happened to produce these few lines: for /f "tokens=3 delims= " %%A in ('Dir /A C:\ntldr ^| FINDSTR /I "ntldr"') DO ( echo ntldr size is %%A REM whatever else ) That effectively does the work without even needing an IF EXIST, as if the Dir command fails to find the file, feeds to FINDSTR an empty line, and the FOR loop is not executed. Just change the C:\ntldr and ntldr with another string or with a variable to put it in a loop or called subroutine..... jaclaz

Well, basically, you should try re-running the CBM 2080 program. Reading an English manual (not really for it, but for a device that uses it): http://www.crystalking.com.tw/FLASH.htm http://www.crystalking.com.tw/Flash/PDF/eManual.pdf Might help in understanding the settings to use, most probably you did something "wrong", like using the "Fix Volume size"or partition percentage.... Why did you use it in the first place? No warranties implied, but if you re-format it with the correct settings it should work, unless of course, you tried the production tool because it did not. On the other hand if the device worked, you should not "play" with this kind of utilities... jaclaz P.S.: just for the sake of trying keeping info together as possible I am crosslinking this thread to this 911CD one: http://www.911cd.net/forums//index.php?showtopic=15776 where some other make/models are mentioned

Try using ycopy: http://www.ruahine.com/ http://www.ruahine.com/ycopy-file-copy-utility.html jaclaz

Yes, sure, the only difference will be that the output of the command will be shown on screen, i.e. a listing of all found files matching *.ext. the >nul redirects the standard output of the command to a "NULL DEVICE" instead of default "CONSOLE". jaclaz

isn't this easier? Dir /B /S %1*%2 | FIND "%2">nul ECHO Errorlevel is %ERRORLEVEL% @echo off ::Check if a file exists in a given directory ::(and subs) by extension - FFBE.CMD ::by Jacopo Lazzari ::thanks to Rob van Der Woude for the examples, tutorials and ::info on his page http://www.robvanderwoude.com/ ::and to Simon Sheppard http://www.ss64.com/ ::----------------------------------------------------------- ::Usage: FFBE.CMD <path> <.ext> :: path must end with \ ::----------------------------------------------------------- ::Example FFBE.CMD Dir /B /S %1*%2 | FIND "%2">nul If %ERRORLEVEL%==0 Echo At least one file with .ext %2 was found (no need to write to a temp file) jaclaz

...or the SET /A command .... http://www.robvanderwoude.com/ntset.html jaclaz