jaclaz

Yes and No. It should be possible to by-pass it: http://hardmaster.info/eng/articles/09-04-2009.html but it's well beyond the DIY level. Of course NOT, the CA-42 is (the good ones actually working) nothing different from a USB-to-TTL converter. It is possible, though, that the contacts are not good: http://forum.hddguru.com/1tb-seagate-hdd-d...d81-t12290.html It can happen that the pins are forced a bit too much by the card, check previous pages there are a few reports about this issue. Completely removing the PCB, thoroughly cleaning the contacts, check if any contact is twisted, etc., etc. may solve the problem, as well as re-tightening the screw nearest to the contacts once you remove the card. jaclaz

What do Seagate utilities report (EXACTly)? http://seagate.custkb.com/seagate/crm/self...&NewLang=en Though I don't think it is/will be a DIY job: http://www.acelaboratory.com/scsi.examples.php http://www.google.com/url?q=http://forum.h...lba-t12535.html Or at least definitely NOT a cheap one. In other words, unless you have valuable data on it it is NOT worth the cost of a repair. You can try the demo: http://en.hydata.com/program-ID=11.html just for the fun of it. jaclaz

jaclaz

My 7-zip (4.65 x64) is unable to open the .IMG file. I get an error "Can't open XP_INST.IMA as archiv." Did we find a x64 bug of 7-zip? Ok that's the wrong board for this type of error Well, I am running (32 bit) 9.07 beta, current is 9.10 beta, I guess it's time for you to ubgrade. jaclaz

You are welcome. jaclaz

Happy to see that the problem is solved, though I would like to understand WHAT are the differences between the "nlite integration" and the "plain integration" that do "trigger" a malfunctioning with latest version but does not with 0.2.3 . JFYI, Try open the .ima inside XP_INST_v04.7z (XP_INST.IMA) with 7-zip.... jaclaz

Link: http://www.msfn.org/board/index.php?showtopic=137714 jaclaz

Check this: http://www.withinwindows.com/2009/11/01/us...th-custom-isos/ cannot say if it applies to your case. jaclaz

Well, just in case: MBRBATCH http://www.boot-land.net/forums/index.php?showtopic=3191 CHS<->LBA spreadsheets: http://www.boot-land.net/forums/?showtopic=2959 (no VBA used as to make them "work" on "any" spreadsheet app) jaclaz

Well, "a SCSI hardrive" is a bit generic. A symmetrically generic answer is "maybe". Post model, make, original size, SCSI type, and what tells you it is a 0 byte (like an internal SCSI bus, an addon card, whatever. Please keep in mind that with SCSI drives out of 100 cases, 98 99 are solved by checking the connections, a bad SCSI cable or a mis-terminated bus is a very, very common issue. jaclaz

THe HP Format tool: partitions the stick in one single partition (often with "unbalanced" CHS/LBA) makes the partition have EITHER a bootsector for MS-DOS (invoking IO.SYS) or for NT/2K/XP/2003 (invoking NTLDR) Since FreeDOS kernel file is kernel.sys it won't work. Additionally, Freedos usually have problems with CHS mappings as the geometry of the device is sometimes detected wrongly (or however it is "pickier" than other OSs). Solutions: use grub4dos or syslinux as "main" bootlaoaders or, easier: use RMPREPUSB: http://www.boot-land.net/forums/index.php?showtopic=7739 that allows for having a bootsector invoking kernel.sys and partitions/formats sticks "correctly". This will provide you a bootable USB stick with FreeDOS. Converting the install .iso in a way that works from a USB stick may be tricky, as it is very possible that several modificatins to the batches that run th einstall are needed. A known to be working way is to use grub4dos mapping of the .iso to (0xff), this way the Freedos will "see" the .iso as if it were a CD. Read the stickies here (yes, ALL of them): http://www.boot-land.net/forums/index.php?showforum=66 Paricularly this one : http://www.boot-land.net/forums/index.php?...c=5041&st=4 So, given that newest RMPREPUSB allows for grub4dos booting too, you should use RMPREPUSB+grub4dos. jaclaz

Yep. Yes and No. Those are settings that could be allright for your present purpose, but that are by no means the "right" ones for a more "complete" grldr CD (like various NT based OS, PE's, etc. A "better" example is in the given link. Yes. Yes. No, meaning that you can, but the results are unpredictable, meaning that I do not trust any .iso editing app, when it comes to bootable .iso. Hmmm, the idea was using the iso and the VM, you remember (of course CDRW are OK as well ) jaclaz

Yes, that's a way, though I am pretty sure there should be Linux GUI tools for this - not really my field. (the Linux, not the MBR). An alternative is to access the Registry offline and delete the contents of HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices (or edit each \DosDevice entry with the new signature), but your mileage may vary with this. (it won't be anymore an image, but a "moved" system, IF it works) jaclaz

This was the reason for choosing the 7za.exe, I will try unRAR.exe Why not EXTRACT.EXE? jaclaz

Yep, but are you from Poland? Why don't you ask on the Forum where you found the reference? In that thread appears to be a link to this: http://odsiebie.com/pokaz/1666414---0f02.html which is dead. Besides the OP says: I believe that only a small subset of WPI addons can run at T13, but anyway, I'll shut up now and let the people really experienced with WPI reply to your questions. jaclaz

Do you save/restore the MBR (or at least the disk signature in it?). If not, it is very possible that this is the origin of the error on SAME hardware. 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