jaclaz

Well NO, you know, you cannot have an "Unattended CD" on a partition, but you can do three things, in order of difficulty: 1) make a bootable hidden partition with DOS files that restore a pre-recorded hard disk image (just like the Dell does with GHOST) 2) make a bootable hidden partition with DOS files and a copy of the (Unattended) setup files, starting them using WINNT.EXE 3) make a bootable hidden partition that boots directly (SETUPLDR.BIN) to a copy of the (Unattended) setup files Read these: http://www.msfn.org/board/index.php?showtopic=26185 http://www.msfn.org/board/index.php?showtopic=37939 http://www.911cd.net/forums//index.php?showtopic=14723 http://www.msfn.org/board/index.php?showtopic=61384 (seemingly unrelated, but not much) I don't know how your Dell hides/unhides partitions, does it have a "hot" key or you need to use a special floppy or something else to hide/unhide it? jaclaz

Yep, it is really slow, however the problem is not when compressing, after all we could well adopt a COUM (Compress Once Uncompress Many) approach, the problem is that it is exceptionally slow at UNcompressing! I wouldn't mind having a far longer time when compressing IF uncompressing is fast and with the promised 20% smaller archives... jaclaz

Looky here, this one must be tested too: [url="http://www.msfn.org/board/index.php?showtopic=68523&hl=firewall"]http://www.msfn.org/board/index.php?showto...523&hl=firewall[/url] jaclaz

Thanks DigeratiPrime, it looks like nice! jaclaz

I think is something connected to the Refresh settings (right click on a page), but it happened to me too, and now it works, cannot really say why. jaclaz

The fact that TESTDISK lets you see the files, does not mean that everything is OK. If TESTDISK did not report any error, assigning a drive letter can be the solution. If TESTDISK reported errors, you should read the docs and repair those errors with TESTDISK. jaclaz

The LVUMSFD.SYS seems like a Win98 Logitech Driver: http://drivermagic.com/p/nph-display.php?a=2943.141 for a USB camera: http://drivermagic.com/p/nph-detail.php?a=2943 Cannot see anything Winamp related.... jaclaz

Most probably it will be enough to recover the MBR and Partition Tables, read these: http://www.msfn.org/board/index.php?showtopic=59145 http://www.msfn.org/board/index.php?showtopic=30378&st=30 jaclaz

looky here: http://www.911cd.net/forums//index.php?showtopic=16048 jaclaz

I think that Maks is referring to changing a boot.ini entry while unattendedly installing, there is something like it here: http://www.msfn.org/board/index.php?showtopic=66101&hl= jaclaz

Here you are: http://www.msfn.org/board/index.php?showtopic=55041 Links to other proggies: http://www.msfn.org/board/index.php?showtopic=55041&st=16 http://www.msfn.org/board/index.php?showtopic=55041&st=23 I use the one from Nirsoft: http://www.nirsoft.net/utils/product_cd_key_viewer.html jaclaz

It's not really my "field" of knowledge, but should you not stop the Service and re-start it? net stop wuauserv net start wuauserv Maybe you can get more help here: http://www.wsus.info/forums/index.php?act=idx jaclaz

You mean something like nmap: http://www.insecure.org/nmap/ http://www.insecure.org/nmap/nmap-fingerpr...ng-article.html jaclaz

Wow, how many PC's did you recover this way? If we average 50 US$ per RAM stick, it needs to make US$ 2,000,000 (the bare minimum to say millions) : 2,000,000/50=40,000 sticks Assuming that less than 5% of all the PC's develop this kind of problem, and averaging two sticks per PC, it means that you were managing (prudentially) something like 40,000/0.05=800,000/2=400,000 PC's Supposing this chore was spread over a 5 year period, averaging 230 working days per year: 40,000/5=8,000 sticks per year 8,000/230=34.78 sticks per day Assuming 8 hours of work per day: 34.78/8=4.35 sticks per hour i.e. more or less one stick every fifteen minutes. ...or you had just one day per week for "RAM laundry" say Friday? in the latter case we have 34,78 x 5=173.91 sticks to be washed on friday that makes: 173.91/8=21.74 sticks per hour, i.e. something like one stick every three minutes. I know that "hundreds" sounds very similar to "millions", but maybe you got confused.... jaclaz

Read these: http://www.msfn.org/board/index.php?showtopic=41643&st=5 http://www.msfn.org/board/index.php?showtopic=40837&st=0 Or, if you can wait a couple of days, try this: http://www.loginrecovery.com/ jaclaz

As you might know there is no such command in batch files, the equivalent of UNIX "sleep" but there are two solutions: 1) use an external app: DOS/Win9x/ME http://short.stop.home.att.net/freesoft/batch2.htm NT/2k/XP Doze v1.0 http://sac-ftp.externet.hu/utiltask3.html (+many more) 2) use a workaround: (please note that it is different if the environment is DOS/Windows 9x/ME or NT/2k/XP) http://www.robvanderwoude.com/wait.html jaclaz

Very useful post, I am sure it will help a lot! @SarahC You will need to download an ME floppy image from here: http://www.allbootdisks.com/index.php?opti...der&filecatid=3 and create a bootable floppy. In the BIOS of the computer you must have boot order floppy/HD/CD or floppy/CD/HD. If the PC boots, post again, I will try to help you with next steps. jaclaz

NO, you will have an UNBOOTABLE SYSTEM. NTLDR needs to be pointed to EITHER: an arcpath, like in: multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Pro" /fastdetect or to a copy of a bootsector like in: C:\Bootsect.w98="Windows 98" But the IO.SYS, MSDOS.SYS and COMMAND.COM, and AUTOEXEC.BAT and CONFIG.SYS have to be on the C:\ drive (First Active Primary partition), i.e. on the SAME partition where NTLDR BOOT.INI and NTDETECT.COM are. In one of the links from the page I previously pointed to there is a workaround, without using a bootmanager on a single drive on which XP on a NTFS partition is already installed: http://thpc.info/dual/dual9xonntfs1.html Just for the record, I personally suggest to always have a VERY small FAT16 or FAT32 partition as First Active Primary Partition, as it allows for the greater flexibility and allows the use of bootpart to manage boot.ini entries. Finally it is possible, though not widely known, to install Win9x to a Logical Volume inside an Extended Partition though it is a bit tricky, and NOT recommended. jaclaz

The SMALLEST possible amount, have a look here: http://www.heatsink-guide.com/content.php?...=compound.shtml http://www.arcticsilver.com/arctic_silver_instructions.htm but ENOUGH to make sure that contacting surfaces are covered. This is a nice simple way to do it : http://www.overclockers.com/tips692/ jaclaz

Well, I am already relaxed, no problem. ..and I don't want to put more stress on you that you already have with the problems you are facing, sorry, but I have to recommend you have an Uninterruptable Power Supply when doing this kind of work, and this applies always, let alone if there are known problems on the power line or if you are running on a generator. jaclaz

Just for the record, there is a (quite obviously VERY simple) bootmanager that fits in the MBR (512 bytes), so that it is quite easy to revert the system back being SURE there is NO leftover. Read about it and more here: http://www.msfn.org/board/index.php?showtopic=47206 @Takeshi, with Partition Manager comes a small program that can run from WITHIN your Windows Installs, or you can use the FREEWARE MBRWIZARD Read here: http://www.911cd.net/forums//index.php?sho...ic=14181&st=611 posts by me to sisal and back jaclaz

Well, it's a problem related to disk(s) or memory: http://support.microsoft.com/?scid=130801 The problem happens in file WIN32K.SYS, there is no WIN2K.SYS file. What I would try: 1) CHANGE cables to harddrive(s) 2) REMOVE ALL MEMORY but ONE stick 3) TEST the PC 4) ADD another stick of memory 5) LOOP to 3) until all memory is back in and no errors 6) IF errors, the last stick of memory put in is BAD, change it 7) IF NOT RESOLVED run Hard Disk Manufacturer tests 8) IF errors try with another Hard Disk 9) IF NOT RESOLVED you will need help from a technician, probably it's the motherboard, either the memory connectors or the Hard Disk controller jaclaz

TRUE FALSE, you can use a bootmanager - WITHOUT using the double boot features of standard NTLDR - to hide/unhide partitions and set/unset them bootable at startup. jaclaz

No you are not, unless you need a hypothetical help instead of practical one. If you are not from CIA, NSA or the like, maybe you could disclose a couple of lines of your batch... However, you just execute the other batch file, invoking it with desired parameters, example: :: This is batch #1 Batch_1.cmd :: Do whatever I am supposed to do :: do something else :: Set the path to the other batch file (if NOT in the same directory of Batch #1) Set Batch_2_path=C:\directory\Batches\Batch_2 :: Set parameters needed for Batch_2 :: ONLY needed if parameters are somewhat calculated before in batch Set param1=some_parameter_1 Set param2=some_parameter_2 Set param3=some_parameter_3 Set param4=some_parameter_4 Set param5=some_parameter_5 Set param6=some_parameter_6 Set param7=some_parameter_7 Set param8=some_parameter_8 :: now invoke Batch #2 passing parameters to it Batch_2_path\Batch_2.cmd %param1% %param2% %param3% %param4% %param5% %param6% %param7% %param8% :: otherwise just put the parameters on invoking line Batch_2_path\Batch_2.cmd some_parameter_1 some_parameter_2 some_parameter_3 some_parameter_4 some_parameter_5 some_parameter_6 some_parameter_7 some_parameter_8 :: END of Batch #1 :: This is batch #2 Batch_2.cmd :: The parameters are batch variables: :: %0 name of Batch #2 (Batch_2.cmd in this case) :: %1 parameter #1 :: %2 parameter #2 :: and so on :: If you want to recreate the same parameters Set param1=%1 Set param2=%2 Set param3=%3 Set param4=%4 Set param5=%5 Set param6=%6 Set param7=%7 Set param8=%8 :: Do whatever I am supposed to do :: do something else :: END of Batch #2 Please note that in this case, Batch #1 will pass command to Batch #2, if you want to return to batch #1, you need to use the CALL statement: http://www.robvanderwoude.com/call.html as in CALL Batch_2_path\Batch_2.cmd %param1% %param2% etc. jaclaz

The most complete windows dual booting resource ever found: Dual-Boot Centre http://www.thpc.info/dualboot.html jaclaz