Jump to content

RamGuy

Member
  • Posts

    47
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Norway

About RamGuy

Contact Methods

  • Website URL
    http://

RamGuy's Achievements

0

Reputation

  1. Only that Nuhi did the job well and his applications were in good and useful state This indian crap is a huge fail. Care to explain what you find wrong with this application?
  2. The site is back up and running again now! I would prefer the old fashion way as well. Once the Windows installation is completed and it boots into desktop, the video card driver is fully installed and no further tinkering is required. The current method used by RT 7 Lite to integrate drivers do not work quite well for me. This problem happens in both of my computers, one with nvidia video card; the other with AMD video card. Once the Windows installation is completed and it boots into desktop, the video card driver is not yet installed. If I restart the computers, the integrated video card driver seems to "disappear" from it, as if no video card driver has been integrated. To solve this problem, once the Windows installation is completed and it boots into desktop, I have to immediately open the Device Manager to access the video card. A prompt to restart Windows pops out. Only then, I shall restart the computer. Upon restart, only then the video card driver is fully installed. It is quite frustrating for me. After all, the reason of using RT 7 Lite to slim down Windows, is to have everything (drivers, Windows Update and etc.) fully installed upon first bootup into desktop. For now, I have to perform extra steps of accessing Device Manager and restart the computer. These extra steps provide unnecessary inconvenience for me. Guys, is there any way to solve my problem? Thanks for the advice given. I haven't really figured the difference between the three types of drivers integration we've currently got. You can go with: #1: Integrate drivers without doing anything about them, just locate them and let them be. #2: Integrate drivers and then select them afterwards and chose the option "Boot WIM Image Only". #3: Integrate drivers and then select them afterwards and chose the option "Install WIM Image Only". What difference does this really make? I figure that the SATA / RAID drivers should be boot integrated otherwise you might not see your hard drives at all. At least if you have chosen to remove the already included drivers that are within the Windows 7 / Server 2008 R2 installation. Other than that I don't really know whether to select Boot or Install WIM? If I don't chose either of them does that mean they get integrated in BOTH the boot and install WIM? That seems like the optimal way to do things? Secondly does anyone have some decent presents they could provide? Especially when trying to trim down Server 2008 R2 Enterprise things tend to get messy.. Windows7 is a bit easier but suddenly things like Windows Live Essentials 2011 refuses to install.
  3. I've tried to google it. But it doesn't seem like there are any mirrors for the RT Server Customizer at all, it's not like Server 2008 R2 is a common thing.
  4. Have anyone else noticed that the RT Seven Lite and RT Server Customizer sites are currently down? Was going to customize a Server 2008 R2 installation but there is no where to download either the 1.7 or 2.6.0 BETA version ..
  5. Hi, Myself and a friend is about to setup a dedicated World of Warcraft / FreeNAS server! We'll be using Windows Server 2003 R2 x64 (with Service Pack 2) as operating system, I'll be integrated all of the latest drivers for the server hardware but I have a bad time figuring what I should, and should not remove from the installation by using nLite! Basicly we want the tiniest and lightest possible version of Server 2003 R2 64bit, while it still keeps compatibility with .NET Framework, World of Warcraft (DirectX9?), as well as it should be able to run VMWare Workstation for the FreeNAS firmware that will be hosting a NAS solution for my friend. So the machine will be all about stability, 24/7 usage and only be running VMWare Workstation (with FreeNAS image), two port link aggregation over the on-board Marvell LAN controller as it will require full speed Internet and network connection in order to get both the FreeNas (VMWare) and multiply World of Warcraft gaming going. And that's about it.. What to remove, and what not to remove to not break the compatibility with those application we'll be running? We can also use Windows XP 64bit Service Pack 2 instead of Server 2003 R2 64bit if you'll recommend that instead, I've just got better overall experience with Server 2003 R2. If anyone could toss up an pre-configured INI file we could be using, I would absolutely love that! We've tried lots of different things, but it either breaks the possibility to run Microsoft Update, install / update DirectX Runtimes, install .NET Framework 2.0 + 3.0 or we aren't able to get World of Warcraft and it's downloader up and running at all, so obviously I keep removing things that I shouldn't remove! So it's all about: - Network speed and stability over 2x Marvell LAN port aggregation - VMWare (with FreeNas image) compatible - Teamviewer (Remote desktop application) compatibility (for remote troubleshooting etc..) - .NET Framework 2.0 and 3.0 is required - Able to play multiply World of Warcraft accounts - Update DirectX Other than that we just want the operating system to be as efficient as possible, using as little system resources as possible!
×
×
  • Create New...