Tripredacus

Sorry I didn't see that post. Yes you can create "patches" to this using the Application Compatibility Toolkit. Its a pretty crazy program. I've used it once to get the sound in Destruction Derby 2 to work in XP, but I was following step-by-step instructions in creating the patch. I have no idea how to properly use the program if I try to figure it out myself. As far as BurnInTest goes, Passmark says that it should work in Win PE as a demo via their instructions. I acquired a trial license to use for testing, and it came down to the fact that this is incorrect as far as Win PE 2.1. It will not run without a license. I have it running tests now and now I get to write up an SoP for its prospective use. Oh boy!

The guides I use are on paper. This looks like a good guide. http://technet.microsoft.com/en-us/library/cc766219.aspx

Yes, the distribution and/or Reminst folders should be on a different volume, but that shouldn't cause a problem. That is merely a best practice method. OK, your Winpe booted to a prompt, which is exactly what it does by default. The fact that this worked means that your issue isn't with PXE or WDS but with your other Boot Image. You can safely remove the Winpe from the Boot Images if you want. I recommend, try using the boot.wim from the DVD instead of the one WDS made for you.

Welcome to the MSFN!

yes sorry I got that backwards... however they do not sound the same. The pronunciation used during the song is different from the english liner notes. and now Covenant - Like Tears In The Rain

The service packs supercede the normal installs in most cases. It also depends on how you install Windows. For example, slipstreamed updates do not appear in Add/Remove programs. You may also only see them if you check the "show updates" box. So you would see a 1.1 SP1 and not a 1.1. The only time you would see both is if you installed the original some long time ago and then got the update later. I think that is how it shows up on my computer at home. OK, if you click show updates, the original one appears in a branch under the SP1 listing. For example, this computer has: - Microsoft .NET Framework 2.0 Service Pack 2 - Microsoft .NET Framework 3.0 Service Pack 2 - Microsoft .NET Framework 3.5 SP1 Now if I click show updates, it appears like this: - Microsoft .NET Framework 2.0 Service Pack 2 --- .NET Framework 2 --- .NET Framework ASP .NET --- .NET Framework WinForms --- Dr. Watson --- .NET Framework PreXP --- .NET Framework CLR --- .NET Framework CA --- .NET Framework CRT --- KB958481 --- .NET Framework 1 - Microsoft .NET Framework 3.0 Service Pack 2 - Microsoft .NET Framework 3.5 SP1 I didn't like the things in 3.0 and 3.5, but 3.0 has about the same amount of things under it as 2.0, and 3.5 has 2 things under it. Since 1.1 was included in the install CD that was originally used to install Windows on this computer (its Server 2003 Standard x86 btw) it does not appear in Add/Remove Programs at all.

That sounds great. That's how I was, I just registered and got to posting.

I got this code from a webpage that I can't find right now. See my original command used the input object, but just this one used button. This is because I can assign a hotkey to button and not to input.

It's really impossible to determine what caused the problem unless it can be reproduced.

Microsoft has allowed end users to create their own SP1 integrated media. This is how I created mine. I only have RTM install CDs downloaded from Microsoft. You must use the SP1 redistributable file, and run VSP1CLN and POSTREFLECT.

1. How much memory on the server and on the client? 2. Are you using any unattend files with WDS, either the WDSClientUnattend on the server properties, or the unattend on the install images? 3. Does this happen with all clients? 4. How many clients are you attempting to boot to the WDS at a time? In my experience, Server 2003 with 1GB of RAM can only deploy to 4 clients at once, adding additional clients (I tried up to 8) causes random errors, lock ups, or extreme deployment delays. Fortunately, this was only done in a pilot environment, and I recommended a Server 2008 machine to be used in production. This is because Server 2003 does not support multicast and Server 2008 does.

I have no problem deploying an attended 2008 install, but here is what is different in my case: 1. My server has 1GB RAM. See the other specs in the "My Servers" link in my signature, and look for UNCLESOCKS. 2. My client has 1GB RAM also. It is not a virtual client, it is an AOpen Digital Engine. 3. I copied the boot.wim and install.wim from the sources folder on the DVD to a folder on the hard drive. 4. I add a new Image Group (in Install Images) called server, and add the install.wim into the server container. 5. I add the boot.wim into the Boot Images, rename it to Server 2008. Default is Longhorn Setup, which would conflict with my Vista boot.wim that is already added. 6. Boot the client, select Server 2008. It boots normally. I log into the domain, and then it lets me select which version of Server to install. Incidentaly, my Vista Business image is also available in this list as well. So I am not seeing this issue, and can confirm that Server 2003 can deploy an attended 2008 setup over the network. Also I do not know much about the WDS logs as I've been lucky that it always works the first time. PXE was tough for me to figure out, and the Win PE is where I have most of my troubles.

I don't use the WAIK either, I use the OPK Tools. I have not attempted to deploy Server 2008 from a Server 2003 computer. I can try that later to see what happens. I have a few ideas for troubleshooting. 1. Make a Win PE and add it into Boot Images. When you boot to the network, you will receive a menu. Choose the PE option. See if it boots. 2. You may need more RAM in the 2003. My 2003 test server has 1GB RAM in it.

I'm thinking that this isn't working for me because I am testing it in VirtualBox. I will save this issue and check it when i recompile my source and test it on a live pc again.

You should keep them in there. .Net will allow a lot of other programs to run, specifically 3rd party programs and some Microsoft ones. The service packs are bug fixes. A notable .Net SP was for 3.5, since 3.0 broke stuff like RDP.

I'd be interested to see how Diskpart or PartInfo views the drives.

OK I am trying out some HTA scripting for a program I am writing. I need the ability to launch a program from a hidden control. Everything works, but the application closes immediately after opening it. However, if I put this action on a input button, it works fine. Here is a working code example: <script LANGUAGE="VBScript">Sub RunRestart Set objShell = CreateObject("WScript.Shell") objShell.Run "fscommand\restart.exe" On Error Resume Next Set objShell = Nothing End Sub</SCRIPT> <body> <input id=runbutton style="width:153" class="button" type="button" value="Restart" name="restart_button" onClick="RunRestart"> </body> Here is a non-working example <script LANGUAGE="VBScript">Sub RunAdmin Set objShell = CreateObject("WScript.Shell") objShell.Run "fscommand\admin.exe" On Error Resume Next Set objShell = Nothing End Sub</script> <body><button id=runbutton style="width:0" class="button" type="hidden" value="Admin Prompt" accessKey="k" name="admin_button" onClick="RunAdmin"></body> The main differences is that the working example uses an input object, while the other uses a button object. Setting the width to zero effectively hides the button. AccessKey allows me to use a keyboard shortcut to launch the program. If I change the onClick value in the "restart_button" object, the program launches properly. What do you supposed is causing this behaviour?

Try using the codebox tag for the XML above. What does the validator in WSIM say? Also, WinRE partitions are supposed to be at the beginning of the drive, not at the end.

Yes, you only have to worry about your ISP if you are running the servers yourself, or using an email client from your pc to send the emails. Since it appears you are using web-based solutions for your mailings, this isn't going to be an issue. I have an idea, but not sure if it will apply to you. I can think of a free way to send out emails, but it takes a lot of work. And a better solution may be out there as well. The simplest way is to install a forum on your site. You do not even have to have open registration, or allow the board to be viewed by anyone. I have a forum on my website that is like this right now. In order for you to do this, your website provider needs to support SMTP. You do not need to receive emails there. It would also need to support MySQL (in most cases) and PHP, although you can get .net boards too. So you install your forum software (be it IPB, phpBB, vBulletin) and set it up to use email. My experience comes from IPB, so I don't know exactly how to use the other ones, but they can all do the same thing. OK, you configure the forum to be able to send emails. Most forums will have an option that allows you to mass email a certain group, or all members about a forum update, news, whatever. This message will support the features you enable, such as being able to put pictures, links, full HTA, whatever in the message. After you type it up, the forum will send that email to all members. Setting up a forum can be frustrating, especially configuring it to work properly. But that isn't going to be the hard part. The time consuming part would be how you get all those accounts into the database so you can email them. You will be fortunate at least to be able to use SQL commands to do a mass member import, and setting it up would be faster in the long run than creating each account manually. So, this is an off-the-wall idea (as I seem to come up with often) and using forum software for something it wasn't intended for.

The best way I can describe this. When you buy Windows, you buy the license or the CD key. You get a CD with it, but you aren't really buying the media itself. The rules pertaining to the CD or the media are in the license agreement that you accept upon installing (or in some cases, opening the package) the software. Typically, you are allowed to make a backup copy for yourself. You are not allowed to lend, sell or recopy, or make available your copy. You also cannot technically sell the CD itself because it has no value, you get it for free when you buy the License. The gray area comes in this situation. If you lose your CD or it becomes damaged, how do you legally get another one? An official seller cannot sell the CD by itself. You cannot legally download it because you end up being involved in a crime. That crime is done by the person who put the download up online, which is not allowed. You become involved because you become a customer of the criminal, even if you aren't paying for it. Your only outlets to get the official media are from the following: 1. Go to the company that sold you the Windows CD. If it isn't a retail store, they may be able to get you a replacement. 2. Know someone that has access to MSDN or an OEM Channel so they can download the media. But this is a gray area as well. If someone has access to these websites, they can only use that media for the company's use. Blah, its a real sticky subject really.

I recommend that for any system running anything besides Vista Home Basic (or Starter) that you have a minimum of 2GB RAM.

Try using a codebox or attach the log instead of posting the whole thing. Check your settings with my WDS Guide to make sure you didn't miss a step. Also need to know some specs to better help: 1. The Server 2003, what architecture is it? 2. The Server 2008 image, what architecture is it? 3. The Server 2008 image, is it a captured WIM or are you using an Unattend image? 4. The client, how much RAM in it? 5. In WDS cpl, what do you have in Boot Images?

Basically, it comes down to this. You need to make sure your ISP (or your mail host) allows you to use email marketing. In other words, this is a business practice. You typically aren't allowed to perform business functions while using a residential or personal type account. You need to check your terms of service that you agreed to in order to see what is allowed and not allowed based upon your service level. This isn't to say that you can't actually just do it anyways, but they might get you for breaking ToS if you have a normal account. For example, if you are a normal residential internet subscriber (instead of having a business account) you are not allowed to have a server connected. You could still do it, and many people do, but its all about the legalese.

Welcome to the MSFN! We have a couple of forum sections you may be interested in: Unattended Vista vLite

Welcome to the MSFN!