Free blocksize software for windows

SplitMania is a small application designed to help you divide a file into more smaller files SplitMania is a small application designed to help you divide a file into more smaller files.
Note that it doesnt use any form of compression! Could be used to split large files, so you wouldnt have to upload or download one big file.
SplitMania will register the file extension SMM the first time you run it, it will also create icons under the SendTo menu for faster splitting. Blocksize Array is an array of sizes in bytes in which SplitMania will write each file block.

An enhanced registry editor, which can do a lot of neat stuff that the Windows Regedit cant.
Features:
- - Registry Commander uses some standard shortcuts defined from back in the DOS days in applications such as Norton Commander.
- - A column always displays the size of a values data.
- - Supports all 12 data types in the registry, defined in the "winnt.h" header file. Most other registry editors only handles Strings, Binary, DWord & Expanded Strings sometimes even MultiString, thats only 5.
- - Copy or Rename/Move entire keys and values from one key to another.
- - A history list has been added to quickly jump from current key to a previously key.
- - Cut or Copy keys and values from one key and paste them into another, using the clipboard.
- - Able to change a values data type. E.g. you can change a string into a binary value without changing the contents of the data.
- - Ability to interpret one value for another, without modifying the data. This would allow you to view a string saved as a binary value.
- - Search part of or the entire registry database, not only can you search by a keyword, but you can also search by size or data type.
- - Registry Commander allows you to bookmark keys or values so you can access them more quickly.
Enhancements:
- - You can now control the format of the value data shown in the listview. The tab "Type Format" in the configuration dialog, contains an edit field for each data type, by editing these, you control the output.
- - Pressing Ctrl+R in the "Key Tree" dialog will refresh the tree, and allow new keys to be displayed.
- - Added a notify sound, which is played after some functions, e.g. after a search has completed. You can choose what wave file to be played, in the configuration dialog.
- - Fixed a very nasty bug that caused stack overflow in the search function. This could occur if RegQueryInfoKey() returned a pcbMaxSubKeyLen of zero, even if it was not. Am I looking at a bug in the Windows Registry API here? What I do, is to allocate a buffer with the size pcbMaxSubKeyLen+1, with the pcbMaxSubKeyLen of zero that leaves our buffer with a size of 1, not enough to store a key name, therefore all subkeys within this key would be reported as an empty string, and the search routine would go into an endless loop. If anyone could elaborate on this, Id be very happy to listen.
- - New option added in the configuration dialog, called "Re-read key when the program is focused". By enabling this option, the current key is automatically reread when it receives focus from another program, for instance tabbing between programs.
- - When you type in a registry path, you *must* use backslashes to divide the keys, in previous versions it was acceptable to use forward slashes as well. This was changed, because it was impossible to open a key, which had a forward slash in its name.
- - Fixed an error in the "Export Key" function, that in certain cases would save binary values, in a format that RegEdit wouldnt recognize and couldnt import.
- - Changed the names of the bookmarks. "Bookmarks -> User Bookmarks", "Search Result -> Search Bookmarks" and "Copied Items -> Cut/Copy Bookmarks". This has been done to make it clearer, that they are only bookmarks, not real registry entries.
- - The new functions "Find AutoRun Values" will list all values in HKEY_CURENT_USER and HKEY_LOCAL_MACHINE under Run/RunOnce/RunServices/RunServiceOnce in the key SoftwareMicrosoftWindowsCurrentVersion in the Search Bookmarks.
- - The "Key Tree" has been moved to the new "Tools" menu item.
- - The added "Rebuild File Associations" function is very neat, if you manually have changed a file association or default icon under HKEY_CLASSES_ROOT. It will tell Windows to rebuild its associations, so the correct icons will show.
- - I changed the way in which "Key Tree" scans the registry keys, this has made it a lot faster than in previous versions.
- - Rewrote the routine that deletes keys recursive, this fixes a problem, which only occurred on Win2k/XP. The reason is that you are not allowed to delete a registry key, on NT based systems, if it contains values. Previous versions had some problems doing this correct, because it didnt get all the values removed prior to the deletion of the keys.
- - Increased the data import blocksize to 32kb, compared to the previous versions, which only allowed 16kb. This was done, because someone notified me about a Microsoft support article, which required you to import a file into the registry, which was larger than 16kb. This was somewhat funny, since I read in the Microsoft SDK that data above 16kb should be stored in a file, and not in the registry, bah never trust Microsoft.
- - Showing the root list by pressing F12, wouldnt always draw the items from the top of the listview.
- - If you run a Windows NT based system, the write time of a key has been added to the key information.
- - Moved the "Value Data" column to be the right most column. It fits better this way I think.
- - Cut, Copy and Paste now works when you edit the name of a key or value.
- - Added the support for QWord; REG_QWORD is defined as 11. Its icon is light blue

FFT3dGPU is a GPU version of Fizicks FFT3DFilter. The algorithm (Fast Fourier Transform, denoising) is the same for the most part. Currently the following is not implemented: support for interlaced video or YUY2 colorspace or noise pattern.
In this version the next frame is processed while waiting for the GPU to end its work. Meaning the filters before fft3dGPU are working concurrently with it.
Installation
To use this filter you need directx 9.0c or better and a graphics card supporting directx 9 in hardware. That is at least an ATI Radeon 95xx or Nvidia Geforce fx 5xxx. Geforce 6xxx or better is recommended. If you have downloaded the installer just run it at youre done, else copy fft3dgpu.hlsl and copy FFT3dGPU.dll into the same directory, also copy d3dx9_30.dll to the c:\windows\system32 directory.
Older versions also had fft3dgpu9b.dll (not available at the moment) for Directx 9.0b support (DONT copy both dll into the autoload directory.) Directx 9.0c might be faster for people using Nvidia Geforce 6xxx because it adds support for pixelshader 3.0. If you dont have the latest version of directx installed (april 2006 or later) you can get it here or extract the file d3dx9_30.dll to the c:\windows\system32 directory. The installer will copy d3dx9_30.dll to the right location meaning that it shouldnt be neccesary to run the directx installer if you have Directx 9c installed.
Syntax
FFT3DGPU(clip, float "sigma", float "beta", int "bw", int "bh", int "bt", float "sharpen", int "plane", int "mode", int "bordersize", int "precision", bool "NVPerf", float "degrid", float "scutoff", float "svr", float "smin", float "smax", float "kratio", int "ow", int "oh", int "wintype" , int "interlaced", float "sigma2", float "sigma3", float "sigma4", bool "oldfft" )
Function parameters:
clip: the clip to filter. The clip must be YV12.
sigma and beta has the same meaning as in fft3dfilter. Default=2.
sigma2, sigma3, sigma4 If specified controls the sigma value for highest(sigma) to lowest frequency(sigma4). Default=sigma
bw,bh: blockwide and block height. It should be a power of 2 ie valid values is 4,8,16,32,64,128,256,512 (note that bw should be greater than 4 for best result). Default=32
bt: mode. bt=-1 sharpen only, bt=0 kalman filtering, bt=1 is 2d filtering, bt=2 uses the current and previous frame, bt=3 uses the previous current and next frame, bt=4 uses the two previous frames, the current and next frame. default 1
sharpen: positive values sharpens the image, negative values blurs the image. 0 disables sharpening. Default 0.
plane: 0 filters luma, 1,2 and 3 filters Chroma (both U and V). 4 filters both luma and chroma. Default 0.
mode: 0 only overlaps 1:1. This is faster but produces artifacts with high sigma values.
mode=1 block overlaps 2:1. This is slower but produces fewer artifacts.
mode=2 again 1:1 overlap but with a additional border. This reduces border artifacts seen with mode=0. The speed is between mode 0 and 1.
Kalman(bt=0) works well with mode=0. Default 1
bordersize: only used with mode 2. Defines the size of the border. Default is 1.
precision: 0: to use 16 bit floats(half precision),
1: to use 32 bit float(single precision) for the fft and 16 bit float for the wienner/kalman and sharpening.
2: allways use 32 bit floats.
Using 16 bit float increases the performance but reduces precision. With a Geforce 7800GT precision=0 is ~1.5 times faster than than mode 2. Default=0.
NVPerf: Enables support for NVPerfHUD (http://developer.nvidia.com/object/nvperfhud_home.html). Default false.
degrid: Enables degriding. Only works well with mode=1. Doesnt degrid the Kalman filter (but it does degrid the sharpening (if enabled) after kalman filter). default 1.0 for mode=1, 0.0 for mode=0 or 2
scutoff, svr, smin, smax:Same meaning as fft3dfilter. Controls the sharpening. default scutoff=0.3, svr=1.0, smin=4.0, smax=20.0
kratio: same as fft3dfilter. Control the threshold for reseting the Kalman filter. Default 2.0
ow,oh: this only works with mode=1. This specifies how big the overlap between the blocks are. Overlap size must be less than or equal to half the blocksize. Ow must be even. Default: ow=bw/2 ,oh=bh/2
wintype: Change the analysis and syntesis window function. Same as fft3dfilter
interlaced: Set to true for separate filtering for each field. Default=false.
oldfft: Set to true to use the old fftcode (used in version 0.6.2 and lower) false to use new fft code. If not defined fft3dgpu will use the fastest code.
FAQ:
Q: What does it mean when I get a popup box Unexpected error encountered with Error Code: D3DERR_OUTOFVIDEOMEMORY.
A: It means that fft3dgpu needs more memory than there are availebol on the graphics card. So either you will have to upgrade or try lowering the resolution,bt,bh,bw,ow,oh or use usefloat16=true or mode 0 or 2
Q: What setting gives the same result as fft3dfilter?
A:fft3dGPU(mode=1,precision=2) is similair to fft3dfilter() but please note the different default values for bw,ow,bh,ow
Q: Is there any differences between fft3dfilter and fft3dgpu?
A: Some of the features from fft3dfilter is still missing.
Q: Why is fft3dGPU so slow compaired to fft3dfilter?
A: either you have a slow graphics card like a Geforce FX 5200 or you are not using it while doing cpu heavy encoding (like XviD/DivX)
Q: How do I use NVPerfHUD?
A: set NVperf=true and used this commandline or make a shortcut to run it: "PATH TO NVPerfHUD\NVPerfHUD.exe" "PATH TO VIRTUALDUBMOD\virtualdubmod.exe" "PATH TO AVS\test.avs" and enabled "force NON PURE device"
Q: I get this errormessage: "Only pixelshader 2.0 or greater supported"
A: It is because you need a graphics card that has hardware support for Directx 9.