Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×


  • Content Count

  • Joined

  • Last visited

  • Donations


Community Reputation

0 Neutral

About prathapml

  • Rank
    Follow the rules please :-)

Contact Methods

  • Website URL

Profile Information

  • OS
    Windows 10 x64

Recent Profile Visitors

3,168 profile views
  1. I think i'm going to bang my head against this wall, next up, thank you Escorpiom and maxXPsoft. This info should set me sailing, if not i will come back to report what happens...
  2. Hi all, I suddenly noticed that the games built into Windows 7 by default, do not get installed in my unattended installs. I have my AutoUnattend.xml at the root of the DVD. The portions that created problems are commented out (in the normal way as is done for XML files, using tags like <!-- xyz -->). And the configuration settings that are NOT commented, are implemented just fine by the installer from what I see (in other words, everything is just fine, except for the games being exempted). Currently need help with the Professional edition, x64, Windows 7 SP1 (integrated image download
  3. Under the conditions you describe, the first thing I might do is to NOT use the Office Integrator, put the MSP files for SP2 and the hotfixes in the Update folder, then test the install. See if it then accepts your SP2 as having been installed already. If it does, then the problem is with the Office Integrator.
  4. SLC drives (not only Intel, but also other brands like OCZ) are indeed faster. Think of SATA3 if you'll be getting one of those. Yep. Especially since most content is small files (example, 10 saved webpages with associated files, totaling up to 2 MB with 600 files in all, or file operations in a different context like a browser's cache folder). On a normal HDD (Seagate 7200.12 1TB) sweetspot, speed for writing small files drops from (for example) 130 MBps to 104 MBps. The same write operation on an SSD (in a best case scenario of the best SSD) can drop from 140 MBps to 2 MBps. Note the singl
  5. The "SATA2 is not enough" thing applies to only the costliest drives with amazing read speeds, so you can safely ignore that for now (unless you want to gladly spend a few thousands of dollars on "fast storage").
  6. Not bad sectors, but an SSD can have bad flash cells. Plus the slow write speed for small+multiple write situations gets to be annoying and worse than a normal HDD, within 2 days. I'm not talking of theoretical dis-advantages, you clearly know your stuff - having tested a number of current-gen SSDs, I'm talking about how the practical benefits fail to keep pace with the expectations and price. If your data is still located on a different spinning drive, then you've divorced yourself from atleast some of the benefits. And the write speed thing can suck real bad even with the newer drives. TRIM
  7. From what I've seen in my tests, the Intel X25-M drives have gone downwards in the charts, even though they still rock. The best performance (at an acceptable price) today is with the Kingston SSDNow V+ 128GB (google for product reviews, too lazy to link any at the moment ). Note the V-plus in the model name there, do not go for non-plus series drives, their performance versus price just might make a grown man cry. Of course, as you said you are not interested in paying extortionist prices for the lower-capacity SLC-based SSD drives, so I leave those out of the picture. An Intel X25-M 80GB c
  8. Yep, it got uploaded to MSDN quite late on 22nd... All constituents including the Web Apps, SharePoint Server, and Office 2010 KMS server keys are present. Just annoyed about how I still must wait till 30th to get the remaining 9 keys.
  9. Ah, that clarifies it then. I did seem to remember that the VB scripts are not removed unless specified. (the vague memory is because I moved away from WinXP many years ago)
  10. At the risk of drawing wrath, may I suggest we all back off from the "how much pagefile is appropriate" discussion. Different strokes for different folks, and "johnhc" here might have his reasons for what he wants, and all of you that have commented definitely have strong technical reasons and experience to back their recommendation. I might personally disable pagefile altogether, but everyone need not HAVE to share that view. But at the end of the day, the question is (*or was, and has probably been abandoned) "how to set my pagefile AND not have it fragmented on disk". Let us get back on top
  11. Hmmm, what I'm gonna mention is a circuitous route, but I'm just looking at this as throwing an idea into the open from where you could take it forward if it's workable. 1. Use the VBS the first time around to disable pagefile entirely, and reboot in 2 mins (you are using autologon, I guess). 2. Autologon a second time and run a defrag command, and set the next task to reboot. 3. Autologon a 3rd time and enable pagefile as per your preferences, then reboot automatically. One other possibility, is to see if one of the defragging apps (DisKeeper, Raxco, O&O, Defraggler, Vopt, whatever) offer
  12. Hi icemanzh, After seeing the screenshot posted above, I have a hunch that it is because of one of these. Are you sure you have all (and i mean ALL) of these options applied in the XML as mentioned in my first post in this thread? Quoted below, just to clarify what I mean. For any further details, please refer to my step-by-step description of both methods, in the first two posts of this thread. <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />Do post back to let me know what happens. As for the 60-day pre-installed Office.... those are usually the resul
  13. You mean that when you use the CONFIG.XML method, there is a dialog box at the end of the install ? And this problem does not happen when you use the MSP method?Now that is interesting, can you please post a screenshot of this dialog box?
  14. Hmm, haven't tried without a key. Maybe the VLK insists on a key because there's no other way of verification/activation after install? The Retail/OEM editions of Office 2007 probably allow for installing without a key, and run for 25 times before you need to insert a key and activate. Hi Greg, I have no idea how to get rid of that "pop up" as you call it. Tried a few things in the MSP and XML initially, but didn't manage to make that part silent. Maybe this can be done through a registry entry. Try this:1. Install Windows fresh. 2. Install Office 2007 (in your customized style, in whatever wa
  15. If the old version isn't being removed, you might have to run a one-time command that all computers must execute at next logon. For example: MsiExec.exe /X{10140000-0011-0000-0000-0000000FF1CE} You can find the exact product components to uninstall and their GUID codes in the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall You can also refer to this URL for GUID info and explanations - http://support.microsoft.com/kb/832672 Hmm, for these purposes, an enterprise edition (or VLK license) is the best for ActiveDirectory environments. Other editions don't li
  • Create New...