wolstech

I know this is a really old topic now, 9 months ago...but I might as well post this for the others who stumble across this and find themselves wondering about IPD and how to unpack it without running the package. Since nobody could figure out how to unpack IPD without the stubs...here's an IPD unpacker that doesn't require the SFX stub...http://raxdev.raxsoft.com/unpackipd.zip Be aware it's a compiled Autoit script with packed files, some AVs might kick a false positive on it. Command line and GUI versions included. Extract the CAB with 7-zip or the like, then point this tool to the folder with _sfx_manifest_ in it... Also, for what it's worth, I'm the primary author of SFXCAB Substitute. I never really maintained the app because I didn't realize there was actually a demand for this thing. I built its predecessor IPDTool in boredom one day while looking for a challenge. SFXCAB Substitute came about when I built Hotfix Hacker (a GUI tool for creating basic update.exe-based update installers) and needed a way to finish the compile process. I figured I might as well release it separately as well since it's already built...so I threw in a readme and stuck it on Softpedia for laughs. Expand.exe is the wrong way to unpack the SFXCAB IPD stuff, at least for NT5.x Windows Updates and stuff made with Substitute. You need mspatcha and an understanding of the manifest. You can unpack it manually, one file at a time, by opening the manifest in notepad and using apatch.exe (also from the SDK, it's the CLI for mspatcha.dll) in CMD. I'm not familar with msdelta, so can't speak to that one. The only thing Substitute does different from MS is that it will auto-exclude files from IPD if they get larger when packed. Those files get regular LZX instead. I've found MS IPD archives that had this issue, which means in theory Substitute will get slightly better compression with the same technology. Happy Holidays guys

OK, after four days, and this post yesterday, I've done it!. I have successfully made a hard disk image that starts recovery console, and runs off a DVD with memdisk. Also, thanks for those links, which proved very helpful! Here's what I did, or at least a brief overview of it anyway: I started with a VirtualPC VHD. That first link proved helpful when it came to the bootsector for it. (I patched the bootsector on that VHD using that information, MKBT from Bart, and a hex editor. Now i don't need NTLDR and boot.ini). It boots fine in VirtualPC. After making the working VHD, i added WinVBlock so memdisk wouldn't cause STOP 0x0000007b. I had to do some tweaking to TXTSETUP.SIF to get WinVBlock to work. Then, I used SelfImage to make an uncompressed, RAW IMG of the hard disk. Added it to ISOLINUX using memdisk, and, after a little more tweaking to the image, I now have a "SETUP->R key"-less Recovery Console! Image is around 6MB compressed. 150MB uncompressed (The large size: I couldn't make it boot using a FAT16 disk). If I gzip it, it doesn't waste space. Memdisk can decompress the GZIP on the fly when booting it. You wouldn't by chance know if I could upload the final .IMG do you? I'm not sure if distributing the RC itself would be permitted, seeing that it's MS software. Then again, I do frequently see patched files around here (prepatched UXTheme.dll on the Unattended guide for one), repacked installers, etc...

Thanks for the links. Someone in one of those links mentioned success with a hard disk image booted with memdisk. I'm going to try that once my disc is finished testing in Virtual PC (takes a good 4 hours on my older PC). A physical system installs the disc in under 2 hrs. I'll post my results.

Hi all, got a good question about Windows Recovery Console. I am trying to add Windows Recovery Console to my DVD as a separate entry. I already know I can press F10 at the F6 prompt of any setup, (no 'R' option here, since my setups are unattended). So far, I have managed to make a standalone recovery console folder on the DVD (it's basically just another boot folder of XP Pro's Setup program, minus the WINNT.SIF). The problem is, when I boot this folder's setup from the DVD boot menu, it stops and waits for me to press 'R' after setup loads...I just want it to go directly to the Console, with no interaction between me choosing it on the DVD menu and the console being loaded. Has anyone managed to do this? I've tried various options for OSLoadOptions (things like /cmdcons, etc.) in TXTSETUP.INF under [setupdata]. Some yielded interesting results (got the windows splash screen to show instead of "Setup is starting Windows" at one point), but none let me skip directly to the Recovery Console. If you're curious as to why I'm asking about this, the only reason I want to avoid F10 is because it really isn't mentioned anywhere. You just 'got to know'...I likely won't be the only one using this disc (7 others might use it), and not everyone knows this. 'R' in the standalone console's "Setup" is just a hassle, and what's worse if you press ENTER by mistake you get an error about the EULA missing and it reboots. Anyone got a clue here? By the way, sorry for the long post!

Hm, ugh. Going to have to try something else... Does anyone know if a copy of logonui.exe from XP Home would work, assuming both systems have the same SP? XP Home does not support the C-A-D for classic. I suppose i could try on a Virtual PC... EDIT: Doesn't work either... Does anyone know of a way to log a user on via a command line? I am running a program that watches for external hardware, and executes commands when said hardware is present. It runs as a service. I'm now wondering if i can simply use it to log a certain account on when the hardware is connected. (I'm not talking about Run As-ing a command, i need to get a desktop.)

Is it possible to completely disable the classic logon in XP Pro? Even if I turn the Welcome Screen on, users can still press Ctrl-Alt-Delete twice and get to a classic logon screen in XP Pro. Is there a way I can prevent that, making it more like XP Home? I haven't seen any group policy that can do that either (of course, an option for Classic Only does exist. Go figure...)

Thanks, that fixed it. The first solution to rename edb.log worked just fine. My drivers are showing up as signed correctly again.

Hi all, this problem has been stumping me for a few days now. Any time i try to install new hardware, I receive the typical Unsigned Driver "Continue Anyway" box. I am seeing these prompts for every driver i install, such as the "USB Mass Storage Device", and "Disk Drive" that install when I connect a new flash drive. On any other system, these drivers appear as signed and install without any dialog boxes, just the "Found new Hardware" balloon in the tray. I've gotten prompts to install the "driver" for "Unknown Device" as well. I'm not sure if the issues occurs with 3rd party drivers. If I look in Device Manager, the drivers for every device listed appear as "not digitally signed". This includes things like the HAL and processor. Anyone know exactly whats wrong here? I have no malware on the system and haven't been infected in over 2 years (last time i formatted). I haven't installed any updates recently that i'm aware of other than the IMAPI2 (KB932716) package, which i needed for testing a script that i'll be using on an unattended Windows DVD. The System has Windows XP SP3 Home on it, 640MB RAM.