Jump to content

kenb

Member
  • Posts

    5
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    South Africa

About kenb

kenb's Achievements

0

Reputation

  1. Could be that you have forgotten to select DVD as the media type in the new compilation dialog - There is a drop down at the top left of the dialog above the compilation type list - from here you must explicitly select DVD before you can burn a DVD (This is for nero - not express)
  2. Maybe I should have been a bit more specific. I assumed a clean install of win2k with HT enabled. Yes I agree that individual programs are unlikely to benefit from HT on win2k. What I was saying is that HT helps to keep the pc responsive from a user perspective when running multiple cpu intensive tasks (again within limits). For example try running 2 copies of seti@home on a win2k HT enabled pc and again on a non HT pc. From a user perspective you will find that the HT enabled pc remains responsive to user input whilst the non HT pc feels like it is ploughing through mud. On a less subjective analysis you will find that the processing time for an individual seti@home work unit will nearly double on the non HT pc whilst on the HT enabled one the processing time per work unit will increase between 10-20% enabling it to process more work within a given time.
  3. Been running w2k -sp4 with HT enabled for about a year and have experienced no problems. I can also confirm that running several cpu intensive programs with HT enabled significantly improves the responsiveness of the machine. No additional drivers are required.
  4. SteveB - Thank's for responding. Yes you are correct about ics setting up it's own dhcp and dns functions. My issue is that after upgrading to 2003 server, this functionality stopped working with any NEW pc that is brought into the workgroup. When the ics server was running w2k I was able to add a new pc to the workgroup and it immediately had all access functionality. I suspect that this may have something to do with enhanced security under Win2003 but am unsure as to how to overcome this. In any case I have finally decided to go with your 3rd option. I am interested to know the solution to this for future reference.
  5. I have a small network (all w2k) with one pc sharing a dsl connection using ics. I recently replaced the OS on the connection sharing pc with Windows 2003 standard with ics enabled. All the pc's that were connected to the network when the upgrade was done continue to receive their IP's and share the internet connection from the server as before. The problem that I am experiencing is that any new pc that is added to the network (workgroup) is not assigned an IP in the standard range (192.168.0.x) and is unable to connect to the internet or access resources locally. This was previously possible when the sharing pc was running ics on w2k. I set up a dhcp server on the 2003 server which then allocated a local IP and any new pc is able to access the local network, but still not access the internet.. My questions are: Why were all previously connected pc's able to function as before with no additional steps required? What steps are required to enable newly added pc's to function as before? Many thanks.
×
×
  • Create New...