jaclaz

I take the liberty to suggest that if it happens on SAME machine, the cause may be different if it happens on different hardware only. An image of a system, once restored to same machine is (or should be) EXACTLY as if nothing was done to it. This would mean some problem with the app you use to create the image or in the way you make it. If it happens ONLY on different hardware, it is normal, and there may be some tricks/ways to prevent the need to repair. In other words, until you have a problem in restoring the image on the SAME machine, you are losing your time trying to restore it to different hardware, Once you have succeeded with restoring on same machine, it may be possible to attempt doing the same on different hardware. this: is not enough. You need to post an EXACT description of the procedure you took, BOTH for "saving the installation" AND for "restoring" it. jaclaz

Image restore on SAME machine or on different hardware? jaclaz

Read this thread: http://www.msfn.org/board/index.php?showtopic=124220 jaclaz

Than the acronym would be wrong : Windows Post Installer WWI? : Windows While Installer doesn't sound that good . http://unattended.msfn.org/unattended.xp/view/web/62/ http://unattended.msfn.org/unattended.xp/view/web/30/ jaclaz

http://en.wikipedia.org/wiki/Asterix#Humour SPQF Sono Pazzi Questi Fujitsiani These guys from Fujitsu must be crazy! 1.7 Gb is roughly the amount you can have three Linux distro's an three or four PE versions (a couple of which choking full of apps). jaclaz

Yep, the credits should all go to wimb, all I do/did is to put together some simple batch files (for several reasons): http://www.msfn.org/board/index.php?showto...133309&st=5 and try to keep the "real developers", like wimb and ilko_t, up to date and "connected" with the "loose ends" I happen to find here and there: http://www.msfn.org/board/index.php?showtopic=111401 jaclaz

And that makes a nice, round, total of 2 of us. jaclaz

I am pretty much sure that I never wrote anything that produces a .sif as output. I don't get fully the question. I guess a firadisk based PE 3.x image will work, but you will need HEAPS of RAM. Here is where to look for: http://www.boot-land.net/forums/index.php?showforum=94 Or maybe a "full" 7: http://www.boot-land.net/forums/index.php?showforum=77 http://www.boot-land.net/forums/index.php?showtopic=10234 "Standard" PE 3.x: http://www.911cd.net/forums//index.php?sho...61011&st=33 "Custom" PE 3.x: http://www.boot-land.net/forums/index.php?showforum=91 Mix and shake well, add whatever you see fit, and test.... jaclaz

Yep, what I meant is that it is not like that MS will create the updated files for the Nvidia chipset and break compatibility with all the other chipset, so there are three possibilities: you don't use those files you use those files and by chance they fix the problem also on non-nvidia chipsets you use those files and they don't fix anything I just wanted to make sure you are in the third case. 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