
Crazy man tweak
Crazy man tweak
I just put my TCP/IP protocol driver on my ramdisk (tcpip.sys) edited the nesaccary registry values and woot the net is faster as a result but beware this is for CRAZZY people only 

Head webcheese and geek guru @ http://www.cablenut.com
In Windows 2000 what controls all TCP/IP functions is a service called TCPIP now that service is the file tcpip.sys I have made a ramdisk with a bootable image file with the tcpip.sys file on it and have edited my registry to reflect where that tcpip.sys drive is. Since RAM has very much lower latencies then hard disks this speeds up the net cause it can access the protcol driver very fast.
Head webcheese and geek guru @ http://www.cablenut.com
Ramdisk and Ramdrive
Ya baby worked for me to
All the Information to this thread can be found here !
Windows 2000 http://dslnuts.com/ramdisk.shtml
As written and supported by Cablenut, Philip and others.
Windows 98 and 98SE here.
http://dslnuts.com/ramdrive.shtml
Both are up to date and this thread and Ramdrives are set just for the OS´s listed. WinXP will be supported in the future.
Thanks for the support
Dannjr
Cablenut team
All the Information to this thread can be found here !
Windows 2000 http://dslnuts.com/ramdisk.shtml
As written and supported by Cablenut, Philip and others.
Windows 98 and 98SE here.
http://dslnuts.com/ramdrive.shtml
Both are up to date and this thread and Ramdrives are set just for the OS´s listed. WinXP will be supported in the future.
Thanks for the support
Dannjr
Cablenut team
I haven't done any real testing yet I can tell you ping time and response time are greatly reduced.
Head webcheese and geek guru @ http://www.cablenut.com
Guys guys guys hold ON
this is a rather long, and serious process to do this. I will put up a guide after I get V4.0 out the door. Thanks

Head webcheese and geek guru @ http://www.cablenut.com
Sounds interesting... Here is some info:
The Ramdisk driver can be downloaded from here:
http://support.microsoft.com/support/kb/articles/Q257/4/05.ASP
1. Extract the inf file from the exe
2. From Control Panel: Add New Hardware > Choose From List > Other Device > Have Disk > Point to the inf file... You should have a Drive Z: after all that.
The path in the Registry for tcpip.sys is:
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\
ImagePath=System32\DRIVERS\tcpip.sys
The Ramdisk driver can be downloaded from here:
http://support.microsoft.com/support/kb/articles/Q257/4/05.ASP
1. Extract the inf file from the exe
2. From Control Panel: Add New Hardware > Choose From List > Other Device > Have Disk > Point to the inf file... You should have a Drive Z: after all that.
The path in the Registry for tcpip.sys is:
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\
ImagePath=System32\DRIVERS\tcpip.sys
Philip while that is good info it is not entirley correct. If you just create a RamDisk with the NT ramdisk service and put your tcpip.sys in there , then edit the tcpip service path. You will need to reboot and upon reboot you will lose all the info you had in that ramdisk. This is why you need a 3rd party application that loads a specific image file with the tcpip.sys file on it.
Head webcheese and geek guru @ http://www.cablenut.com
Yes a login script in Win2k would do that either way it is a long and tedious process. I also forgot about adding the AFD sys driver to this is important to networking activites I will tell you when I get back how it is.. *if I get back 
[ 02-06-2001: Message edited by: cablenut ]

[ 02-06-2001: Message edited by: cablenut ]
Head webcheese and geek guru @ http://www.cablenut.com
Well defintaly afd.sys, and tcpip.sys speeds things up maybe not on the DOWNLOAD side but other things like ping, response, basically anything that depends on time it speeds up.
Head webcheese and geek guru @ http://www.cablenut.com
Ok here goes the guide since you guys are begging for it:
This is for Windows 2000 only. Only Windows 2000 has the advanced service, and memory managment to run this.
This guide will show you how to put your TCPIP, and WINSOCK services onto a ramdisk to speed things up
NOTE: I'm not sure on how stable this is yet, but I can tell you I haven't noticed any crashes.
1) We will need a program that creates a ramdisk for us. The one I use is RamDiskNT
2) It can be found here http://www.jlajoie.com/ramdskNT/rdNTv12e.exe
3) Now once you have downloaded, installed, and have it running we will need to configure the settings for the ramdisk.
4)
Here we have our ramdisk configuration tool.
5) Use the settings I have on there except you can make any size you want under 'Disk Size' just as long as it is big enough to fit the .sys drivers which are about 600KB total.
6) After you have configured everything according to the picture. You can now start the driver. It will then place the ramdisk at whatever you named it in my computer. My ramdisk is z:\
7) Now we need to get the sys files onto the ramdisk. we will need 'afd.sys', and 'tcpip.sys' they are by default in C:\WINNT\system32\drivers
8) right click on the file and go to copy and paste them into the ramdisk.
9) Now we have the sys files on the ramdisk open your ramdiskNT tool up again and go to 'Save Disk Image' this will save a disk image to c:\ramdskNT.img by default.
10) So now we have a copy of the ramdisk in .img format. We now need to hack up the RamDisk Tools registry options.
11) Go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\ramdskNT\Parameters
12) Here we will see several registry entries. We want to edit 'LoadImageOnStart' to a value '1'
13) We want to Edit the 'SharewareKey' to hex: ffffffff
14) Note: if you do not edit the Shareware key ramdiskNT (unregistered) will not load image files on start.
15) Now we will need to point the services to the new path of the sys files.
16) for the afd.sys driver we will need to go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\AFD
17) Modify the ImagePath key to refelect where the afd.sys is on the ramdisk. I have mine set to \??\Z:\AFD.sys
18) Note: the \??\ before drive name is crucial for it to work
19) Now onto tcpip.sys go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Tcpip
20) Modify the ImagePath key to reflect where the new tcpip.sys file is. I.e. mine is set to \??\Z:\tcpip.sys
21) You have now configured your computer to run the TCPIP and AFD services on the ramdisk instead of the hard drive
22) Note if you run the config tool after you edit the shareware key you will need to edit the shareware key again.
23)reboot the machine If TCPIP or AFD doesn't start up you did something wrong I suggest just going back and editing those image path values to where they were. You can try and starting it in command line. start > run > cmd. Type net start tcpip, and net start afd
[ 02-07-2001: Message edited by: cablenut ]
This is for Windows 2000 only. Only Windows 2000 has the advanced service, and memory managment to run this.
This guide will show you how to put your TCPIP, and WINSOCK services onto a ramdisk to speed things up
NOTE: I'm not sure on how stable this is yet, but I can tell you I haven't noticed any crashes.
1) We will need a program that creates a ramdisk for us. The one I use is RamDiskNT
2) It can be found here http://www.jlajoie.com/ramdskNT/rdNTv12e.exe
3) Now once you have downloaded, installed, and have it running we will need to configure the settings for the ramdisk.
4)

5) Use the settings I have on there except you can make any size you want under 'Disk Size' just as long as it is big enough to fit the .sys drivers which are about 600KB total.
6) After you have configured everything according to the picture. You can now start the driver. It will then place the ramdisk at whatever you named it in my computer. My ramdisk is z:\
7) Now we need to get the sys files onto the ramdisk. we will need 'afd.sys', and 'tcpip.sys' they are by default in C:\WINNT\system32\drivers
8) right click on the file and go to copy and paste them into the ramdisk.
9) Now we have the sys files on the ramdisk open your ramdiskNT tool up again and go to 'Save Disk Image' this will save a disk image to c:\ramdskNT.img by default.
10) So now we have a copy of the ramdisk in .img format. We now need to hack up the RamDisk Tools registry options.
11) Go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\ramdskNT\Parameters
12) Here we will see several registry entries. We want to edit 'LoadImageOnStart' to a value '1'
13) We want to Edit the 'SharewareKey' to hex: ffffffff
14) Note: if you do not edit the Shareware key ramdiskNT (unregistered) will not load image files on start.
15) Now we will need to point the services to the new path of the sys files.
16) for the afd.sys driver we will need to go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\AFD
17) Modify the ImagePath key to refelect where the afd.sys is on the ramdisk. I have mine set to \??\Z:\AFD.sys
18) Note: the \??\ before drive name is crucial for it to work
19) Now onto tcpip.sys go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Tcpip
20) Modify the ImagePath key to reflect where the new tcpip.sys file is. I.e. mine is set to \??\Z:\tcpip.sys
21) You have now configured your computer to run the TCPIP and AFD services on the ramdisk instead of the hard drive
22) Note if you run the config tool after you edit the shareware key you will need to edit the shareware key again.
23)reboot the machine If TCPIP or AFD doesn't start up you did something wrong I suggest just going back and editing those image path values to where they were. You can try and starting it in command line. start > run > cmd. Type net start tcpip, and net start afd
[ 02-07-2001: Message edited by: cablenut ]
Head webcheese and geek guru @ http://www.cablenut.com
Yes I just tried this I set it down to 16MB while it was trying to use my 128MB image file it kept bluescreening in Windows so I had to boot from bootdisk and remove the ramdiskNT service from the OS and restart and set it up all again this time with a 33MB disk.
Head webcheese and geek guru @ http://www.cablenut.com
I wouldn't recommend a size of 128MB it eats to much of the memory pool and causes other problems. 33MB is good for systems with 256MB of ram or more.
[ 02-07-2001: Message edited by: cablenut ]
[ 02-07-2001: Message edited by: cablenut ]
Head webcheese and geek guru @ http://www.cablenut.com
I know this has been said before, but please remeber to backup your registry.
I have just returned from a semi-heart attack trying to use this tweak... with the RAM drive on and the registry edited, i rebooted the machine only to find that I have lost my video... as in, i can see NOTHING on the screen after window boots.
I had to go into safe mode and import my backup registry to get the system back. I don't know why this tweak doesn't work for me... but i don't think i want to try again... just yet.
I have just returned from a semi-heart attack trying to use this tweak... with the RAM drive on and the registry edited, i rebooted the machine only to find that I have lost my video... as in, i can see NOTHING on the screen after window boots.
I had to go into safe mode and import my backup registry to get the system back. I don't know why this tweak doesn't work for me... but i don't think i want to try again... just yet.

Me and phillip are working on a better way. If we can get it to do what we want it will be much better.
Head webcheese and geek guru @ http://www.cablenut.com
Ok guys we have figured it out!!
NOTE: This will slow down the startup process by 3 Minutes or more due to it has to start TCP/IP services upon startup. Make sure to BACKUP your registry before doing this.
The ramdisk program we will use is:
http://download.microsoft.com/download/win2000ddk/sample01/1/NT5/EN-US/Ramdisk.exe
MS Ram Disk
1) Download this file and extract the contents somewhere.
2) The contents include source files, the sys file, and the .inf file
3) Control Panel > Add New Hardware > Choose From List > Other Device > Have Disk > Point to the inf file...
4) We then need to go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Ramdisk\Parameters
5)
6) The only thing we want to worry about is 'DiskSize' and 'DriveLetter'
7) 1MB is 1,048,576 bytes so if you wanted 2MB ramdisk you would enter a decmial value of 2,097,152. Drive letter of course means what drive letter the RamDisk makes itself.
8) So the next time we reboot our ramdisk will be whatever we made it. I made mine 1MB and Drive Letter Z:\
9) So before I rebooted I would also have to due some other things.
10) First I need to edit the TCPIP, and AFD ImagePath entries like this:
The \??\ before the drive letter is crucial.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AFD
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip
In those key is where the 'imagepath' key is we want to edit these to reflect where are new sys files will be on our ramdisk.
11) Now we need to make a login script to copy the needed sys files and start the services. Create a new text file and the require text is:
@echo on
Echo Starting TCP/IP Services
copy c:\winnt\System32\DRIVERS\tcpip.sys r:\
copy c:\winnt\System32\DRIVERS\afd.sys r:\
net start tcpip
net start afd
notice on the copy command I have r:\ after it change this to whatever drive you made it. Save the text file and rename it as login.cmd.
12) Now we need to auto start the login.cmd file. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run and create a new string value name it whatever you want. Modify it to reflect where your .cmd file is you just made.
13) Now we have everything ready to restart and start the process.
14) when you reboot and login. It will then run that script file. It will TAKE a long time to start TCPIP probably from 3-5Minutes. After it runs the script file you should be set and able to work fastly on the internet.
NOTE: This will slow down the startup process by 3 Minutes or more due to it has to start TCP/IP services upon startup. Make sure to BACKUP your registry before doing this.
The ramdisk program we will use is:
http://download.microsoft.com/download/win2000ddk/sample01/1/NT5/EN-US/Ramdisk.exe
MS Ram Disk
1) Download this file and extract the contents somewhere.
2) The contents include source files, the sys file, and the .inf file
3) Control Panel > Add New Hardware > Choose From List > Other Device > Have Disk > Point to the inf file...
4) We then need to go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Ramdisk\Parameters
5)

6) The only thing we want to worry about is 'DiskSize' and 'DriveLetter'
7) 1MB is 1,048,576 bytes so if you wanted 2MB ramdisk you would enter a decmial value of 2,097,152. Drive letter of course means what drive letter the RamDisk makes itself.
8) So the next time we reboot our ramdisk will be whatever we made it. I made mine 1MB and Drive Letter Z:\
9) So before I rebooted I would also have to due some other things.
10) First I need to edit the TCPIP, and AFD ImagePath entries like this:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AFD
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip
In those key is where the 'imagepath' key is we want to edit these to reflect where are new sys files will be on our ramdisk.
11) Now we need to make a login script to copy the needed sys files and start the services. Create a new text file and the require text is:
@echo on
Echo Starting TCP/IP Services
copy c:\winnt\System32\DRIVERS\tcpip.sys r:\
copy c:\winnt\System32\DRIVERS\afd.sys r:\
net start tcpip
net start afd
notice on the copy command I have r:\ after it change this to whatever drive you made it. Save the text file and rename it as login.cmd.
12) Now we need to auto start the login.cmd file. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run and create a new string value name it whatever you want. Modify it to reflect where your .cmd file is you just made.

13) Now we have everything ready to restart and start the process.
14) when you reboot and login. It will then run that script file. It will TAKE a long time to start TCPIP probably from 3-5Minutes. After it runs the script file you should be set and able to work fastly on the internet.
Head webcheese and geek guru @ http://www.cablenut.com