[RESOLVED] Network booting from TCP/IP DOS into Win2K
Results 1 to 6 of 6

Thread: [RESOLVED] Network booting from TCP/IP DOS into Win2K

  1. #1
    ViperZ2001
    Guest

    Resolved [RESOLVED] Network booting from TCP/IP DOS into Win2K

    I've successfully created a DOS TCP/IP boot disk to connect to our Win2K ADV server machine.

    I'm only having one issue: ghosting is slow

    Specs are:

    PIII 933
    512 MB PC133
    (5) 20GB drives in a RAID-5 array
    3c905B 10/100 NIC
    Switched ethernet via Cisco

    I can ghost from our Novell server (lower hardware specs though) and I typically get about 300-500 megs per minute (yes...this is correct)

    With Win2K, I get about 100-125 ghosting the exact same laptop.

    Any ideas? I know that there is a reg setting for the TCP receive window and I have increased that from 8k (8192) to 64k.
    Also, I am the only one on this box right now until I finsh the setup.

    Any help would be appreciated.

  2. #2
    rangersfan
    Guest

    Post

    I'm no expert. but can you set background application priority to highest?

  3. #3
    Ya_know
    Guest

    Post

    Is the Novell server using TCP/IP, or IPX/SPX. If it is the latter, that would have to explain some of the speed difference, (but perhaps not that much of a difference)

    This registry setting you refer to, you appied it to the 2k advanced server with the ghost image, I presume. Could you post that little tidbit? I would like to tinker with that just a bit myself...

    ------------------

  4. #4
    ViperZ2001
    Guest

    Post

    The reg key was applied to the 2000 server. Click on the link below and then click in the center of the screen 'Autofix now' and save the file.

    http://www.pcpitstop.com/pcpitstop/a...e=IntSpeed.hta


  5. #5
    ViperZ2001
    Guest

    Post

    Once you have saved the file, open it and choose the latency that best fits your needs.

    The actual reg key is:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters]
    "TcpWindowSize"=dword:00002000

  6. #6
    ViperZ2001
    Guest

    Post

    Anyone else have any ideas?

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •