GreenMachine

Almost ... that was XPCREATE.CAB (a file I made). I need LOGFILES.CAB.

Attach the whole LOGFILE.CAB. You do it from within the Add Reply Web Page (where you just wrote that message). There is a section called File Attachments, that allow you to add a file to your post. I'll add one here, so you can see what it should look like: (Attachment removed)

We'll talk after the weekend ... But everyone knows, even when they lose, they take it to the wire. I don't think my Dad could stand losing to The Birds three times in his lifetime, half of their post-Babe appearances: '46, '67 and '04. On a more statistical note, 1918 or not, only two teams have won more World Series than the Boston Red Sox. One of them we just put behind us. Now we have a chance to get the other one. I've never really seen any improvment after running BootVis, but I would suggest the Microsoft Baseline Security Advisor. Unless, of course, you are worried about not passing the test!

Then post them!

Not to be a pain in the neck, and I know you are trying, but I really WILL NOT even try to read your long post. You need to attach the log file to the post, not just cut and paste it. Then I will be happy to try and help you. Click on the Add Reply button, and in the File Attachments Section, browse for LOGFILES.CAB, in the NEWFILES directory of your XPCREATE directory.

I sure hope you people making localized versions of this have cleared it with RyanVM. He put a lot of work into this. If not, that would be ... not nice. @RyanVM: They have stopped saying "We Still Believe", and now it is "Can You Believe!" - We'll convert you, yet! (Sox in Six?)

Install it on a VPC/VMWare system, and then look in your TEMP directory. To find out where your TEMP directory is (it is not C:\Windows\TEMP), go to the command prompt and type: ECHO %TEMP%. It is somewhere in your Documents and Settings profile. Of course you could do it on a real PC were you so inclined ...

http://www.catb.org/~esr/faqs/smart-questions.html

Oh no ... Please don't post like that, I absolutly cannot read it ('specially first thing in the morning). LOGFILES.CAB should be attached. Please read this: http://greenmachine.msfnhosting.com/XPCREATE/help.htm Particularly the last paragraph, and please edit the above post to remove the all too long log file. I have not even tried to understand yet, but will after you edit it!

Welcome to MSFN, henna555! You are right, there are some issues with the Windows 2000 installation at this point. First, the current version does not support DX9C: you still need to use the OPK version of DX9B (for the moment). That could be the cause of your runtime error, but I am not sure. One of those new hotfixes is responsible for the GreenScreen error (actually teal, but let's not get picky). I don't remember which offhand, but it is one of the IE updates. It is discussed in another thread in this forum. I cannot say about the hotfixes you tested, as I have not tried them. I am working on my own list at the moment. Lastly, don't forget to check your MSFN mailbox sometimes: http://www.msfn.org/board/index.php?act=Msg&CODE=01 Good luck, and do take a look at the two other Windows 2000 threads that are near the top of this forum.

If the drivers yo are trying to add are already supported by XPCREATE, you just need to add the directories $OEM$\$1\DRIVERS into the FILESCD directory, and you should be OK. Hope that gets you going.

Sorry, I've been kind of busy lately, having to pull my team into the World Series nearly single handidly. I do plan on getting to the RAID.SATA questions next week. Please check back then.

Strange, I even looked at that link and did not catch that typo. Thanks for that, kurbycar32, and ... Welcome to MSFN!

I knew it was hard coded somewhere. It looks to me like you are editing Microsoft's file, not mine. In that case, I'd say you are in line with MY EULA. I do appreciate your concern: all to rare these days ... Glad you got it going!

I should be getting around to SATA/RAID issues next week. Please check back then to report your problems.

Thanks, BaTLeZone! I think I have an answer to the last update, but I'm still testing it. I'll keep you posted.

Now you do! I hope DLAUTO=NO got you going.

What's a matter, can't wait ten days? You mean there were some folks not watching? I don't know about The Team, but I'm sure exhausted! Not that I want to point fingers, but ... look what happened to those cellar teams Seattle and Texas when they got rid of the "Greatest Player In Baseball". If there are any unemployed out there, perhaps now is the time to talk to The Boss about working in N.Y.: I hear there are a lot of openings ... So ... Johnny B. Good, and I know who my Papi is! Happy Birthday, Mickey! Well, we have a couple of off days, so maybe I'll get back to work!

The final result is the same: the difference is in the tools used. Nilfred's method does create a smaller file, so perhaps it is better.

Amen from me, too! Those of us with over twenty years experience know that there is still a lot to be learned, and nothing like a younger hand to show us! Good work, Ryan. Now if you only would use some of that diligence in picking your baseball teams!

Error? I never got an error. I also don't see one mentioned in your post ... If I may suggest some reading for helping you help us: http://www.catb.org/~esr/faqs/smart-questions.html

Are you kidding? Then everyone and their mother would be trying it, and reporting (USER) errors! In fact, there is no download for CABARC.EXE only, though it is included with many, many Microsoft kits (CABSDK, IEAK, WM Enterprise Deployment, etc.). I figure that those who do not have it probably are not worried about running this from SVCPACK.INF. Which brings me to your second point. Of course I did not post it until I tested it, and if it would not work in SVCPACK.INF, it is not for me! The reason one sometimes has trouble with MSIEXEC.EXE is not because MSIEXEC.EXE is not "found", but because the *.MSI file must have either the full path specification, or be in the current, working directory. In this case, it is in the current directory, in order to avoid the need for hardcoded paths. Note that MSIEXEC.EXE in NOT included in the final package. CABARC.EXE, on the other hand, IS.

Just like last year ...

Thanks, Nilfred, for your guide. As I mentioned to you in a PM, I was "inspired" by your code to create a similar solution, using free Microsoft tools. Following is "my" answer to this problem. As stated elsewhere in this thread/forum, the "System Restore" message is caused by the Windows Media Redistributables included with Windows Media Connect. Specifically, WMFDIST95.EXE. This is the package that required re-packing. I have attached my WMC.CMD file that will create a new, optionally silent WMC package. The resulting file, WMC.EXE, is created using IEXPRESS, and is of similar format to standard Type II Hotfixes. That is to say, it requires the /Q:A /R:N switches to run silently. Otherwise, you will be prompted to confirm installation. Even when prompted, this package can be installed with System Restore disabled. In order to create this package, you will need these three files in a single directory: WMC.CMD (Attached to this post) WMCSETUP.EXE (The Windows Media Connect Installer) CABARC.EXE (Microsoft's CAB compression utility) Simply run WMC.CMD from this directory, and the new installer, named WMC.EXE will be created. The WMC.CMD file performs the following steps: Extracts the Install Files from WMCSETUP.EXE. Creates the Adminstrator Install Point from the MSI file extracted. Extracts the files from the WMFDIST95.EXE Redistribution file. Repacks the WMFDIST95.EXE Redistribution file adding the /DisallowSystemRestore switch. Compresses the whole Administrators Install Point into a CAB archive. Creates an IExpress Installer with the Adminstrators Install Point and CABARC (for de-compression) and the required commands. The resulting file is named WMC.EXE, and can be treated as any Type II Hotfix. Thanks, Nilfred, for doing the grunt work! WMC.CMD

Well thanks, baliktad, for popping in! I was starting to wonder if you got lost out in the Surf! I should have stated my objectives a bit more: I could do the SystemRestore On/Off thingy, but I have this thing about installing everything via SVCPACK.INF. It does not seem possible to turn on SystemRestore at that point. The reason for using SVCPACK.INF is that this allows me to produce a Windows Distribution that remains as true to the original as possible, does not require $OEM$ or WINNT.SIF in any way, and is complete upon the first boot into the GUI. And thank you, crahak, for your input. I was going along in the same direction of analyzing the problem, and also saw that it was wmsetsdk.exe that was causing the problem. Further investigation also showed that this file is nothing other than the setup_wm.exe file renamed. Finally, thanks to Nilfred, whose post crahak pointed to as the "Final Solution". With permission from Nilfred, I wrote a modified version of his solution using Microsoft tools only. I will post this solution in that thread. Again, thanks, all, for your time and efforts!