jaclaz

You have a queer idea of testing. Usually you create the .iso, you try it in a VM, if it works you burn the .iso. Trying it in a VM is not a 100% "safe" test, it is possible that the .iso does not work in a VM and is happily booting on real hardware or viceversa, but unless VERY strange builds or VERY strange BIOS, if it works in Qemu or VMware it works on real hardware too. Qemu is a bit more "picky" for booting so in this case is a better testing ground. About grub4dos is not that bad, it's mkisofs the problem . An example menu.lst: http://www.msfn.org/board/index.php?showto...69211&st=26 (which if you have your own ways can be reduced to): timeout 1 title dos.ima map --mem /dos.ima (fd0) map --hook root (fd0) chainloader +1 or: timeout 1 title dos.ima map --mem /dos.ima (fd0) map --hook root (fd0) chainloader /io.sys To create the .iso you can use the command lines in my batch: http://www.911cd.net/forums//index.php?sho...18045&st=25 jaclaz

I see. Easiest would be to turn it off and edit the wallpaper or use coolmon, BGinfo, or samurize, etc., see here: http://www.msfn.org/board/index.php?showtopic=99231 jaclaz

I see. We talking of this? http://forums.techarena.in/guides-tutorials/1168298.htm or of this: http://www.avforums.com/forums/portable-mu...indows-7-a.html i.e. of this: http://support.microsoft.com/kb/976972/en-us Did you try the updated files? jaclaz

Well, the floppy image should be allright, if it works on CD, so the problem must be the way the DVD is created. If you use magiciso you don't need Winimage, however: http://www.magiciso.com/tutorials/miso-createfloppyimage.htm Are you using a "plain" El-Torito floppy emulation or the magiciso multiboot feature? http://www.magiciso.com/tutorials/miso-cre...multi-os-cd.htm http://www.magiciso.com/tutorials/miso-createmultibootcd.htm http://www.magiciso.com/howto/howto.htm#Make bootable ISO image Are you sure you are using ISO (and not UIF)? I wouldn't be that sure, I see no theoretical reason against the fact that a BIOS may be able to boot from a no-emulation DVD and NOT from an El-Torito Floppy emulation one. Easiest to check would be to use a no-emulation bootsector, as an example grub4dos grldr, and then chainload the floppy image. Mkisofs is anyway recommended (though it has an awful syntax) as we know how it works. jaclaz

It does help , but it doesn't make sense (to me at least) . You create a .iso with nlite, right? The files inside the .iso are the modified ones or they are not? Verify the MD5/CRC of the files you modified and compare them to those in the .iso. AFAIK "original" files cannot be recreated from thin air, and the VM should "know nothing" about them. i.e. I presume that the "original" are written to the .iso instead of the "modified" ones. jaclaz

Nice , though it's the "new place" for: http://www.frontiernet.net/~fys/ Home of the mtools for dos: http://www.frontiernet.net/~fys/mtools.htm now: http://www.fysnet.net/mtools.htm the site is online since the '90's, JFYI, look at first link in it's "useful links" page : http://www.fysnet.net/links.htm jaclaz

I do not understand what you mean: Are you trying to create a new BOOT CD form a \I386\ folder? Or are you trying to replace them on a live system? Do you have WFP (or SFC if you prefer) turned off? Can you try better detailing what you are trying to do and waht happens? jaclaz

I am afraid I cannot understand WHICH is "this problem" and WHICH are "these USB Sync/Copy Problems". jaclaz

How did you write/which tool you used/with which command lines to create the bootable DVD? jaclaz

Nothing much new under the sun, AFAIK it works on 9x/Me, 2K and XP too: http://www.pctools.com/guides/registry/detail/539/ jaclaz

What do you mean by automaticly? You mean something like burn to the brim? http://bttb.sourceforge.net/index.html Or an archiver/splitter? Like 7-zip? Or maybe a backup/restore application capable of saving and restoring data from CD/DVD? Like this one? http://hcidesign.com/dvdspan/ Or a cloning/restore app? http://www.macrium.com/ReflectFree.asp Can you detail what you are trying to do? jaclaz

Yes. No, if the loopback tests work and you get the messages the thingy is working. (unless for some reason the interfacce TTL levels is not adequate, i.e. the Rx "understands" the data sent by the PCB, but the "Tx" is not understood by the PCB. ) You should be able to check the peak levels of the interface with a multimeter: http://www.interfacebus.com/voltage_threshold.html (i.e. is it possible that you are sending 5V TTL/CMOS levels instead of 3.3 V TTL ones ) AFAICR you should be able to establlish a connection also with the PCB completely detached from the HD. Which contacts did you try insulating (there are two ways, one insulating the Head contacts and one insulating the Motor ones). Try the other way: http://www.msfn.org/board/index.php?showtopic=133387 Take your time reading the thread, there are several reports about CA-42 (or seemingly CA-42 cables) you may be able to find a report of success with one exactly like yours (and possibly some more connection details). jaclaz

Yes, you have to add the SATA drivers to the PE build. Depending if you are creating a "universal" PE or a specific one for that machine, you may want to choose between adding only a specific driver, or using the driverpacks, or use UNIATA: http://www.msfn.org/board/index.php?showtopic=141451&hl= There is nothing to change in menu.lst. It's inside your DOS .img that you need to add a NTFS driver. You have two options for R/W and another two for Read only: NTFS4DOS from Avira and NTFS4DOS IFS from Paragon: http://www.boot-land.net/forums/index.php?showtopic=8479 http://www.boot-land.net/forums/index.php?...c=10292&hl= http://www.boot-land.net/forums/index.php?showtopic=6865 jaclaz

Poor little fellow , I care for your unfortunate situation, in which you do not get the answers you want, what a pity. [italian] L'erba voglio cresce soltanto nel giardino del Re [/italian] (the above translates roughly to "The grass "want" only grows in the King's garden") Yes, you can write them allright, if you LEARN how to. jaclaz

http://www.911cd.net/forums//index.php?sho...c=23603&hl= jaclaz

If I am not mistaken TinyHexer runs on Win9x/Me, only it does not have direct disk access under non-NT OS. It has both a "normal" hex comparison feature and a script to find file differencies: http://www.boot-land.net/forums/index.php?showtopic=8734 jaclaz

Also, at least until the MS guys don't find it and delete it as they did for the original page: http://technet.microsoft.com/en-us/sysinte...s/bb963892.aspx however still listed on the "index" page here: http://technet.microsoft.com/en-us/sysinte...s/bb469934.aspx (which redirects to the Sysinternals homepage) can still be found here: http://www.microsoft.com/taiwan/technet/sy...on/bootini.mspx This is supposedly the new page: http://msdn.microsoft.com/en-us/library/ms791480.aspx I guess the good MS guys should really put together their act, and either leave things where they are or, if moving them, link to the new place where they moved them. jaclaz

Well no, when it's tuned properly , it is still a very good tool. The problem is the same: SCHOOL and EDUCATION. The Crystall Ball Tuners Guild is nowadays made ONLY by: young people who didn't listen to the elders and learned nothing about this very delicate job when they attended CRAPIT (Crystalball Repair Adjusting Polishing Institute of Technology) old people that is too old to remember properly the needed tricks of the trade As reknown the situation of Tarots and I-Ching is much worse anyway. jaclaz

Dear Mr. Ponch, thanks for your detailed post on MSFN.ORG board further explaining your issue. Now, at the light of the previous correspondence, you may want to press F4 while booting and follow the instructions that will appear on your screen. If you are missing any of the applications that originally came with your PC, you may want to download them from our site www.samsung.be. You must understand that here at Samsung Assistance we were taught these two directives (and these two only): Start a reparation procedure Before beginning a reparation procedure, you should reset your PC by holding the F4 key when turning it on. Then follow the instructions while the machine starts. Download software You can download the software that originally came with your PC, like Easy Display Manager and Magic Keyboard drivers from our site www.samsung.be. It's several months that we used advanced combinatory mathematic techniques to generate 13,657 different replies to Customer's questions using the words contained in the two directives above. The above is just to show that we are not - as you might seem to think - retarded, we are actually very intelligent and friendly, but we simply do not have the faintest idea of what you have done to your PC or, should it matter, not even know how a PC works. We took a course where they taught EVERYTHING that is needed to assist Customers. We learned a lot in that course (the above two directives) and since we passed the final exam replying BOTH questions in it with what can be compared to an A+ grade, we feel confident to have all the knowledge Samsung thinks needed to assist their Customers, including you. So, please download the drivers and applications you might be missing from our site www.samsung.be, then restart your computer holding the F4 key pressed and follow instructions on screen. You may well contact our call center at the number already given you in previous communications, if you do so, you will find a friendly assistant that will ask you to give your client number, then he will ask you to please download the drivers and applications you might be missing from our site www.samsung.be, then restart your computer holding the F4 key pressed and follow instructions on screen. Regards, Afedrtonm Rotamsnidan Technical Board Response Center Samsung Electronics Benelux jaclaz P.S.: you may also want to try restarting your computer holding the F4 key pressed and follow instructions on screen....

You go in BIOS and (if you have this setting availble) turn "AHCI" off or set "IDE compatibility mode" on (or some similar settings). Most probably you have SATA disk drive(s) and you need to access them in "IDE compatibility mode" OR to add to the build the appropriate SATA drivers. DOS, while being able to see the HD, won't however be able to access volumes in it formatted with the NTFS filesystem, unless you add to it a NTFS filesystem driver. jaclaz

Sure. There may be a couple of little tweaks needed, but if motherboard is the same model you shouldn't have any problem. You'll probably need to activate the new install, though. jaclaz

Yes, but you won't like it. This thread is not populated by hard disk recovery experts, by chance (and hard work, and guessing and a lot more things ) a specific solution to two specific problems of a specific hard disk model "surfaced", "escaping" the Sancta Sanctorum where this kind of info is kept by the professionals (usually guarded by a couple of leopards ). "Extending" this solutions to ANY problem on ANY hard disk model is simply not going to happen, unless some more specific to your drive model info comes out. The principles should be the same, but as well as the connection speed, also the internal "language" of the disk is different, Sadly, you are in the wrong place. See similar examples: http://www.msfn.org/board/index.php?showtopic=138828 http://www.msfn.org/board/index.php?showtopic=137080 http://www.msfn.org/board/index.php?showto...807&st=1636 jaclaz

...or U.S. schools have further lowered their standards, lately.... jaclaz

I am obviously missing something here , but for the little good it may be , this batch does provide drag 'n drop makecabbing: dragncab.cmd @ECHO OFF SETLOCAL ENABLEEXTENSIONS SET File=%1 SET FilePath="%~dp1" SET FilePath=%FilePath:~0,-2%" SET FileExt=%~x1 SET LastChar=%FileExt:~-1,1% IF %LastChar%.==_. (Extrac32.exe /Y /L %FilePath% %File%) ELSE (makecab %File% /L %FilePath%) jaclaz

Only seemingly OT jaclaz