Jump to content

Aaron

Patron
  • Posts

    5,640
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Everything posted by Aaron

  1. Aaron

    Build 2600

    Yup its a good one.
  2. Aaron

    Build 2600

    We need a little more info, download the WinInfo tool and execute the application http://vzone.virgin.net/aaron.stevens/wininfo.zip If it says Activated, and no expiration, then you have the Final Corp version
  3. Wavelet would probably know the answer to that (he comes to the forums sometimes) But if I were you, I would do a clean install *always*. But you may have your important reasons for upgrading only.
  4. Kewl! Now I can set ACDSee 3.1 as my default viewer!
  5. 800MHz Pentium 3 320MB SDRAM 133MHz Microstar 6163-Pro Mobo ATI Radeon 64MB DDR SB Live! 1024 30GB IBM 7,200rpm and 20GB Fujitsu 5,400rpm NEC 12xDVD 40xCD-ROM Yamaha 8x4x24 CD-RW Netgear FA311 10/100 NIC Belinea 17" Monitor Logitech Speakers with subwoofer 56k U.S Robotics Ext Modem v.90 Some s*** terra multimedia keyboard MS Wheelmouse Optical Dual booting Win2k Pro SP2 and XP Pro Corporate Soon to come.... 1.3GHz AMD Athlon DDR Crucial 512MB SDRAM DDR 266MHz Microstar 6380 K7T 266 Pro ATI Radeon 64MB DDR SB Live! 1024 sound card (bah, Sonicfury wouldn't work :grump ) DUAL 30GB IBM 7,200rpm Hard Drives Pioneer Tray drive 16xDVD 40xCD-ROM Plextor 16x12x40 CD-RW 3COM 10/100 NIC Belinea 17" Monitor Logitech Speakers with subwoofer Standard Keyboard MS Wheelmouse Optical Should Dual boot Win2k Pro SP2 and XP Pro Corporate
  6. The reason why I don't like PerfectDisk and always haven't, is because it puts half of the files at the front of the disk, and the other half at the end of the disk. I have to ask... "why?!!!" Data loads a lot faster when its at the front of the disk, so most other commercial defragmenters place data at the front.
  7. I heard Norton Speeddisk 2002 is good, it has the ability to move the paging file to the front of the hard drive, something which past commercial NT Defragmenting apps hasn't done before.
  8. This question only applies to anybody using NTFS in Windows XP. I have doubts about Diskeeper 6 second edition because it was released to the public before NTFS 5.1 was finalised.
  9. IntenseGhetto.com are so full of themselves. They BELIEVE ANYTHING they see on the net instantly. First of all, they said that there was a Corp version of RTM in #microsoft-network so I just went back in there this morning and found their topic said [ No OEM Leak - someone packeted me! ] (lame excuse...:mad: ) #Win-Gate now claims to have a proper OEM though (no timebomb and just the 30 day WPA) We've yet to know if they really have it, and it could just be a patched RTM EVAL version underneath.
  10. Here's some more info that should help, from =epyx= (thanks!!) There seems to be a lot of confusion about build numbering in here, so I thought I would try and set the record straight about build number "2600". As some others have tried to pointed out, there are actually two "2600" builds in circulation: * usa_2600__x86fre.pro_whistler.iso * usa_2600_x86eval.pro_whistler.iso Only the second one (the 120-day Evaluation build) truly qualifies as RTM. The other "2600" was created several days prior to RTM and MS openly admitted that a few bugs were fixed right up until the night before Aug 24. So even though they share the same build number, they aren't identical and should properly have different numbers. The "2600" released about a week ago is not RTM. =epyx=
  11. Here's some extra info: from http://www.microsoft.com/piracy/basics/act...on/mpavlfaq.asp it says: "A VLK must be used with Select CD or Worldwide Fulfillment (WWF) CD media (aka volume licensing CD media). VLKs cannot be used with retail full packaged product or OEM CD media." Volume Licence Keys are like corporate keys, that bypass activation completely. Unfortunately, it cannot be used on an OEM or Retail copy. So, to use a VLK, you will need a corporate version of RTM for the key to work. Its unknown when we will see a VLK leak....
  12. [img:8a6e7293e0]http://vzone.virgin.net/aaron.stevens/windowsbeta_rtm.gif[/img:8a6e7293e0] Above, is WindowsBeta, which beta testers can access. As you can see, the RTM OEM is not available on there. The second file "usa_2600_x86eval.pro_whistler.iso" is the final build, WITH the 120/180 day evaluation Timebomb.
  13. Last night and this morning, IRC has been plagued with questions and a lot of different answers/views were said. There was so much confusion going about. After reading for hours and hours it soon cleared up in my head, and these are the facts: Windows XP is final, and has been released to manufacturers (RTM), It is build 2600 (not 2600.1 or 2600.3 or anything 2600.x its just build 2600) The manufacturers have the OEM version, it has no 120/180 day evaluation timebomb included. It only has the 30 day activation. After 30 days you will be locked out. (This is called RTM OEM) The RTM Build 2600 that appeared on WindowsBeta.mirosoft.com last night for beta testers is the final RTM build WITH the timebomb. So Beta Testers have the final copy, but they can't use it for very long. (This is called RTM Evaluation) Neither versions (OEM and EVAL) have debug code. The one we want leaked is the RTM OEM. *** If you are having trouble understanding this, please reply with the parts you don't understand and I will try and make it more clearer as possible.
  14. You will need FTP Server software, such as BulletProof FTP Server or Serv-U (BulletProof is better IMO) Set up a user account for each friend you have, and share the drectory which has your 2600 rars/iso files. They can login to your FTP Server through your IP address and a user/pass. They can do it through their FTP Client (CuteFTP) or through a download manager (GetRight, Flashget) if they know the full path.
  15. From TweakXP.com Below are some Windows XP memory tweaks. They are located in the windows registry at: [b:02fa95bca0]HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession ManagerMemory Management[/b:02fa95bca0] [img:02fa95bca0]http://www.tweakxp.com/images/blue_block.gif[/img:02fa95bca0] [b:02fa95bca0]DisablePagingExecutive[/b:02fa95bca0] - When enabled, this setting will prevent the paging of the Win2k Executive files to the hard drive, causing the OS and most programs to be more responsive. However, it is advised that people should only perform this tweak if they have a significant amount of RAM on their system (more than 128 MB), because this setting does use a substantial portion of your system resources. By default, the value of this key is 0. To enable it, set it to 1. [img:02fa95bca0]http://www.tweakxp.com/images/blue_block.gif[/img:02fa95bca0] [b:02fa95bca0]LargeSystemCache[/b:02fa95bca0] - When enabled (the default on Server versions of Windows 2000), this setting tells the OS to devote all but 4 MB of system memory (which is left for disk caching) to the file system cache. The main effect of this is allowing the computer to cache the OS Kernel to memory, making the OS more responsive. The setting is dynamic and if more than 4 MB is needed from the disk cache for some reason, the space will be released to it. By default, 8MB is earmarked for this purpose. This tweak usually makes the OS more responsive. It is a dynamic setting, and the kernel will give up any space deemed necessary for another application (at a performance hit when such changes are needed). As with the previous key, set the value from 0 to 1 to enable. Note that in doing this, you are consuming more of your system RAM than normal. While LargeSystemCache will cut back usage when other apps need more RAM, this process can impede performance in certain intensive situations. According to Microsoft, the "[0] setting is recommended for servers running applications that do their own memory caching, such as Microsoft SQL Server, and for applications that perform best with ample memory, such as Internet Information Services." [img:02fa95bca0]http://www.tweakxp.com/images/blue_block.gif[/img:02fa95bca0] [b:02fa95bca0]IOPageLockLimit[/b:02fa95bca0] - This tweak is of questionable value to people that aren't running some kind of server off of their computer, but we will include it anyway. This tweak boosts the Input/Output performance of your computer when it is doing a large amount of file transfers and other similar operations. This tweak won't do much of anything for a system without a significant amount of RAM (if you don't have more than 128 MB, don't even bother), but systems with more than 128 MB of RAM will generally find a performance boost by setting this to between 8 and 16 MB. The default is 0.5 MB, or 512 KB. This setting requires a value in bytes, so multiply the desired number of megabytes * 1024 * 1024. That's X * 1048576 (where X is the number, in megabytes). Test out several settings and keep the one which seems to work best for your system.
  16. From WinsuperSite's Windows XP Tips It seems that a lot of people are interested in removing Windows Messenger for some reason, though I strongly recommend against this: In Windows XP, Windows Messenger will be the hub of your connection to the .NET world, and now that this feature is part of Windows, I think we're going to see a lot of .NET Passport-enabled Web sites appearing as well. But if you can't stand the little app, there are a couple of ways to get rid of it, and ensure that it doesn't pop up every time you boot into XP. The best way simply utilizes the previous tip: If you'd like Windows Messenger to show up in the list of programs you can add and remove from Windows, navigate to C:WINDOWSinf (substituting the correct drive letter for your version of Windows) and open sysoc.inf (see the previous tip for more information about this file). You'll see a line that reads: msmsgs=msgrocm.dll,OcEntry,msmsgs.inf,hide,7 Change this to the following and Windows Messenger will appear in Add or Remove Programs, then Add/Remove Windows Components, then , and you can remove it for good: msmsgs=msgrocm.dll,OcEntry,msmsgs.inf,7
  17. Aaron

    Build 2600

    Rumours go around that the 2600 ISO is just the Release Candidate 1 ISO renamed. Watch out!
  18. Aaron

    Build 2600

    Its a fake! The file is edited with Resource Hacker, changing the version number inside the dll file. Pretty easy to do.
  19. Aaron

    Build 2600

    [img:c3f2135aad]http://members.chello.nl/a.vanheumen1/images/2600.gif[/img:c3f2135aad] Let the votes start!
×
×
  • Create New...