Content Type
Profiles
Forums
Events
Everything posted by Tripredacus
-
Closing this topic. Please use your original one!
-
Im starting to hate spwizimg.dll!
Tripredacus replied to Orsi's topic in Setup Billboard Screens for Windows
Hope you've noticed all your customizing topics get moved to the Customizing sub-forum. Post these questions there. -
Does a zero byte file (as reported by Windows at least) really mean there is no data in it? What if you opened one in a hex editor?
-
I'll skip to the point on this one. Office 2010 SP1 is not made for pre-release or Leaked (Warez) versions of Office 2010.
-
Don't forget to make a backup of that UFD!
-
Welcome to the MSFN!
-
Pearl Jam - Spin the Black Circle
-
Strange Problem with DFI Motherboard... Please Help
Tripredacus replied to Shane's topic in Hardware Hangout
Ah no they aren't (or don't have to be that is) but if you don't have one already maybe just skip this step... I wouldn't say you should just jump into using a Multimeter without some training or other things (besides motherboards or other expensive things) to test on. -
How to avoid customer having to enter product key?
Tripredacus replied to Jimmo's topic in Unattended Windows 7/Server 2008R2
No it is not correct. It plainly states what is required. The only product key that should be "pre-installed" is the install key, which gets removed during sysprep anyways. If the information I pointed to you is not present in your OPK Guide, contact your rep to get an updated copy. Also ask your rep if you should be using the OPK or if you should be using the WAIK. -
How to avoid customer having to enter product key?
Tripredacus replied to Jimmo's topic in Unattended Windows 7/Server 2008R2
You are not allowed to do this. Since you are using the OPK, open the Windows OPK User's Guide. Under OEM User Experience Guidelines, License Requirements click OEM Requirements. Read the second paragraph under the "Anti-Piracy Support" section. If you have any further questions regarding Microsoft licensing, you should contact your Microsoft Partner account rep. Since specific OPK documentation is communicated under NDA, I cannot post a quote from that guide. -
Best choice of custom install tools and process
Tripredacus replied to Stilez's topic in Unattended Windows 7/Server 2008R2
Thanks I forgot about SCCM. MDT is pretty straight forward to learn and there is a lot of documentation and tutorials for it. -
Video I made my sig pic from Samael - Slavocracy
-
Best choice of custom install tools and process
Tripredacus replied to Stilez's topic in Unattended Windows 7/Server 2008R2
The amount of info you are requesting is difficult to fully answer. A lot of the answers are already on the forum. WAIK is your base toolkit. You'll need this either way. It includes DISM and WSIM, and also gives you the ability to create a WinPE as well as contains the documentation on the WAIK, WinPE and Unattended settings. Get this and read through the WAIK guide to get started. DISM is the tool you use to service Win7 and WinPE images. You can mount volumes, add drivers and updates/packages to an image offline. WSIM is the tool you use to create answer files for installation or sysprep. MDT is an enterprise level tool that you can create lite and zero touch deployments from either a deployment server or from bootable media. MDT is not licensed for use by a System Builder or an OEM to assist in deployment of systems destined for resale. Everyone does their base image creation differently. I don't use VMs but I use actual test systems. My workflow is: 1. Create answer file to deploy to Audit Mode. 2. Use answer file with install media to install OS to system. 3. In Audit Mode, make changes as necessary, then sysprep /generalize /audit 4. Capture image to server using Imagex Then I can add drivers to the image for whatever hardware its going on, or add programs to it or put an answer file that covers the OOBE pass. Yes Generalize will remove system specific infos such as what hardware is installed. When you boot an image that has been generalized, Sysprep will redetect all hardware and look for drivers in the driver store to install. I keep track of what drivers go into what image, so that there isn't multiple drivers included for the same HwIDs. These things are not touched during Generalize. I don't know about your other questions. Look at our topic of help guides here: -
Strange Problem with DFI Motherboard... Please Help
Tripredacus replied to Shane's topic in Hardware Hangout
Unless there is a severe bulge or leakage, yes. That type of cap is popular on boards now, the MSI and Intel boards I looked at just now use them. Maybe they are more resistant to the bulging? The only other way would be to use ye-olde-multimeter (and some math skills) to make sure you are getting the correct readings as marked on the caps. -
Strange Problem with DFI Motherboard... Please Help
Tripredacus replied to Shane's topic in Hardware Hangout
No! I apologize, I should have looked in your first picture. The caps on that board are not easily identifyable on visual inspection for failure, because they have a different casing. I forget what this type is named. You can only check for leakage visually. -
Did Microsoft go back on its policy?
Tripredacus replied to JorgeA's topic in Networks and the Internet
Maybe there were a lot of complaints about it? I know tons of people that use the address bar for searching. -
There's no way you'll get any help cracking the password! However are you certain that these have had their passwords changed? Did you try the default one as listed in the manual?
-
Strange Problem with DFI Motherboard... Please Help
Tripredacus replied to Shane's topic in Hardware Hangout
You can do a quick look at your caps to see if there any potential bad ones. The pictures on the right of this page: http://www.badcaps.net/pages.php?vid=5 can show you some examples. What to look for primarily is a slighy bulge on the silver colored top part (it should be flat) or ever a rust color on the tops. Of course, if you had leaks on the bottoms or blow outs (you can look for that as well if you want) I would expect even less performance than what you are currently seeing. Either way, if it ends up being caps they CAN be fixed without replacing the board but that comes down to your particular experience with electronics, so replacing the board may end up being a better solution for you. -
LS-120 SuperDisk drive under Win98 and DOS
Tripredacus replied to Multibooter's topic in Windows 9x/ME
Based on your report, it appears that you can actually fit 32MB of data on a 1.44MB floppy disk, but can LS-120 or a regular FDD then read this disk, or just the LS-240? -
Did Microsoft go back on its policy?
Tripredacus replied to JorgeA's topic in Networks and the Internet
Its marketing really. By the time IE9 hit release, the bing thing was to use the Bing BHO as the search option. Either way, I'm pretty sure you can search from the IE8 and IE9 address bar, as long as that option is enabled in the Advanced Internet Options. -
Your best course of action is to use the Windows Server Fulfillment site. It would help if you had a machine with a Server 2008 COA, but I am not entirely certain how exactly the site works. You might be able to get the media with just a 2003 COA. On the following link, click the plus [+] in the "Original Equipment Manufacturers (OEM) Customers" section. http://www.microsoft.com/windowsserver2008/en/us/downgrade-rights.aspx
-
Strange Problem with DFI Motherboard... Please Help
Tripredacus replied to Shane's topic in Hardware Hangout
I've seen other DDR3 chipsets retrofitted for DDR2, but that always confused me. Anyways, it seems there isn't a problem using a v2.1 card in a v2.0 slot, or even a v1.1 slot. But let's get down to the fact at hand. You had a working config and "suddenly" is acting up. I can think of two reasons for this: 1. Your config isn't supported. I'll take a look and see if your manufacturer has some detailed info like Intel does. 2. There has been degredation on the actual electronics. I'm specifically thinking of caps, as they are the easiest to spot. Most everything else is a lot harder... Since you were overclocking the CPU, this could be directly related. Don't always believe that heat is the only negative side-effect of overclocking. -
If you are getting the browse box after the PE boots, its because there is something up with your NIC. Either you can't get an IP or the NIC drivers are not installed. Open a CMD and verify you have an IP and can access the mapped network drive. Otherwise you'll need to use DISM to put your NIC drivers in the boot.wim. Also, in the imagex.hta, on line 25 is a "myFilePath" which is what you want to match against the map driver command in your startnet.cmd. For example, mine says: myFilePath = "Z:\" 'The folder that contains the *.wim files add "\" to the end of the path.