Jump to content

awilliamson

Member
  • Posts

    22
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Canada

Posts posted by awilliamson

  1. This is an opinion question, about the best development hardware setup for a .NET Web programmer. The company I work for is reviewing our existing setup for our developers:

    * Laptop for VPN, MS Office Applications, and RDP

    * VMware Virtual Machine with Visual Studio 2005 installed for all Web Development Projects

    * Central Windows Server 2003 with IIS and SQL Server 2005 installed, and all web project code is local to these servers (everything is accessed through the network)

    We are wondering if we should allow for local development on the laptops, instead of the VM, but I'd like to get additional feedback on what other people/companies have that works best.

    Thanks for all who reply,

  2. I'm trying to find a tool to help monitor the network bandwidth from a server. I have a server powering a website, but my total throughput for a month is 500GB. I'd like to be able to to monitor the total used bandwidth for a month on the server, and possibly pull reports about usage as well. People are not logged into the server, so it would need to run as a service on the machine. It is a Windows Server 2003 server.

    Does anyone have any suggestions?

  3. If you have the SATA driver downloaded, I would suggest using nLITE to slipstream the driver to your windows CD. It can create the ISO file for you when complete, and its a simple burn and install afterwards.

    To add the driver, just search for the txtsetup.oem from the manufacturer within nLITES driver add wizard, and select the drivers you wish to import (you can do multiple, or just the one you wish for), and it will do the rest.

    I have not used the DriverPacks before, so I can't say if that's easier or not.

    Good luck,

  4. I have an IIS 5.0 FTP server running on 2000 Server. The FTP Site has a root folder (c:\FTPROOT), with user folders underneath (c:\FTPROOT\{userid}). Each user has a username and password, and the username=FTP Folder under the root.

    IE7 Users are seeing the FTP server ROOT Folder (c:\FTPROOT), instead of the users ROOT (c:\FTPROOT\{userid}). They can navigate to it, and all is well, but I don't want them to be able to see ALL the folders.

    Older browsers, like IE6 and Maxthon don't have an issue. It's only users with IE7 that seem to have the issue. I've tried to change the PASV option, and the Browse FTP Folder options within IE, and it had no effect.

    Thanks, Al

  5. XP Home does not have the support for Remote Desktop. It does have Remote Assistance, but that is not quite the same. To remote the Home systems, you may want to try using VNC (A free remote PC product). You could also setup NetMeeting on the Home systems to run, allowing you to remote the systems.

  6. I had the same problem with our image here, but I was not able to get the SATA driver working, unless I built the image on the SATA hardware. I found myself under the impression that the SATA driver information did not load to the image, because it had no reason to, on the VM hardware.

  7. You're right ripken, it's not true at all. As I'm sure you know, defragmenting causes excessive disk usage by moving files to reorder them to eliminate free space gaps between files. If you do this every day, that's far more wear and tear on your computer's hard drive.

    Defragmenting once every month or two I can see being feasible. Daily is far too excessive and will cause more problems than what it's worth.

    I'm really surprised that people don't realize that defragging frequently (even daily) does more harm than good.

    I'd really like to understand this further. NTFS does not cure disk defragmentation, but it may help to deter it. I've worked on XP systems, and 2K systems both with NTFS, and disk defrags when run, can run for an hour or more (The record being 27hours for 14GB of data, on a 20GB drive though).

    VMware disks will fragment as they grow, and even if you allocate the disk data before hand they fragment. I use Diskeeper Pro 10 to defrag my drive, and it runs daily. I have been doing this (with previous versions) for 2 years.

    I would assume that the extra wear and tear MAY occur on the Read/Write Head moving back and forth, but unless you have set your HD's to stop (which slows the PC up and is a pain to wait for them to spin up) after XX minutes, your wearing the bearing and the motor our anyway.

    I would also argue that defragmenting moves the data closer together, eliminating dead space. The dead space eliminated the need to move the R/W heads, meaning less wear on them.

    This argument is not to dissimilar to the war on whether it's better to shutoff your computer, or leave it running all the time. Which is worse on the Processor/RAM and other chipsets?

  8. If you performed a factory repair using a CD, it is possible the drive was cleaned to a previous state removing your files. If not, you just used a Windows XP CD, and ran a repair, the files would likely be located in the C:\Documents and Settings folder, but under a different folder. If, for example, on your old setup, the username was JimBob, and you later performed the re-install, it is probable that if you re-created the useraccount JimBob on the new installation, it would look like this.

    c:\Documents and Settings\JimBob

    c:\Documents and Settings\JimBob.MyPCName (the PC name is tagged on the end.)

    If not, try some disk recovery software such as EasyReovery or Recover My Files

  9. If it opens, and blinks, I would check to make sure in Task Manager the Excel process is not still running. If not, I would suggest re-installing the Office software, performing a repair of the application. Another item to try would be to have someone else open the file, re-save it, and send it back. I have had in the past a file someone could not open, but I could. After I re-saved the file, and sent it back, the file worked without a hitch.

  10. I'm having an issue with our Sysprep'd image, and a new HD controller on our laptops. The computer will continually restart, regardless of what I manage to do. The computer is a dual-core laptop, and has an Intel Sata controller.

    The image that I'm working with is sysprep'ed from an older system, but does not seem to work, and I've tried to integrate the new SATA driver in the image, post sysprep (not sure if you can do this. I've included a Sysprep.txt to the txtsetup.txt to this for review.

    I checked the preload on the image, and the HAL is using HALMACPI.DLL, and I have set the HAL in the sysprep to match. Our image is based on HALACPI.DLL. Typically, when the image needs a different HAL file, I copy the correct one in as the HAL.DLL in the image using an NTFSPRO boot CD. This has worked wonders for me, and allows me 1 image for various HAL's that would be otherwise incompatible.

    For the actual driver files, I have attempted to place them in c:\sysprep\i386\$oem$\textmode, and also c:\sysprep\$oem$\textmode.

    sysprep.txt

    txtsetup.txt

  11. Ghost is my personal choice, but it really depends on what you want to do. I have a PXE Boot server setup so that I can Ghostcast across my network. This is fast, and fairly easy to setup. I've had some difficulty with Acronis, but I haven't spent much time with it to get it figured. Ghost was just easier to learn. I use version 8, with 3com boot services from version 7.5.

  12. 3,306.6 MB in size, and the Sytem32 Folder is 1,116.1 of that. This is a month old installation from an XP2 slipstreamed CD, with all the Windows Updates applyed using Autopatcher. If you use offline files, those are stored in a folder under the WINDOWS folder, and can contribute to the total size. Contrary to your findings, I have a winSXS of 24.1MB, so don't know why it's so much smaller by comparison.

  13. Here is I recommend, as an alternative to adding the UPDATE HAL line to Sysprep.

    Include in your image a folder containing the HALAACPI.DLL, HALACPI.DLL, HALAPIC.DLL, HALMACPI.DLL, HALMPS.DLL, HALSP.DLL (ie. c:\HAL). Windows loads the driver necessary automatically, but what is really occuring is Windows is copying, and renaming the above DLL files as HAL.DLL in the %SYSTEMROOT%\System32 folder. If you right click the HAL.DLL file, and Version -> Original File Name, you will see what I mean.

    Now, you can sysprep the computer. If the computer locks on startup, and it isn't the MassStorageController problem, boot into the recovery console. Rename the HAL.DLL as HAL.OLD, and copy the correct DLL in it's place. Make sure to rename as HAL.DLL. Most new computers are HALAACPI.DLL if they are desktops or laptops. Older machines typically are HALACPI.DLL.

×
×
  • Create New...