X11 FrontEnd for the Rio Utility v1.07 made by guys from the Snowblind Alliance. Surely not the best nor the most beautiful of all GUIs made to manage the famous Rio MP3 Player, but I tried to implement some of the ideas that the "real" managers doesn't implement. List of some "interesting" features:

• 2 windows side-by-side like in Norton Commander legacy managers
• treats M3U playlists as directories
• displays the space remaining on the device as you select files to upload
• current file & overall progress bars
• realtime display of the transfer speed

P.S. - if you get problems downloading files with long names, apply the patch I provided below on the Rio Utility source (not XRio itself!) and recompile it.

This is a tiny and highly experimental HTTP/1.0 proxy software that I have written to debug HTTP protocol & it's clients. It is very small and simple, yet useful to reverse-engineering purposes. It's interface is quite obvious. The Server frame controls the IP, port and connection limit of the proxy server. It also shows how many connections are active at moment. The Data Traffic frame shows in/out packets & bytes. Service frame allows you to stop, start and quit the proxy. These are the very minimalist controls for the very minimalist proxy server.

The interesting stuff begins at the Plugin frame. All the packet passed through this proxy server are forwarded to the selectable plugin module. By default, it is logger.dll. It simply saves every single packet into separate file, which uses the following name scheme: from_IP.from_port-to_IP.to_port.log (for example, 127.0.0.1.4322-127.0.0.1.21.log). The files can be ordered by their modification date in your file explorer, so you can track the entire session:

The logger.dll can be set up to include a sequence counter at the beginning of each packet and to output saved packets into some specific directory:

Plugin module is also capable of injecting packets. Load the replicator.dll file and check the setup screen:

When you click the Capture button and then make some action in your proxied web client, the replicator plugin will prompt you if it got a corresponding packet. This packet may be resent automatically, at the period specified in the Period box. You can capture & replicate several packets, and manipulate their resend period. A very interesting application of the replicator plugin is to flood web chats and to spin up web counters. Of course, the right way is to use logger.dll and to make a clone that imitates the "real" web client.

The final note: this is, and always will be, an alpha-state code. I do not develop this proxy application anymore. It is useful to me the way it is. But you can grab the source and make a whatever plugin you like, or even rewrite the code entirely. I don't care. Just give me the proper credits!

inPEct means "infect", applicable to PE ("Portable Executable") format. It is an executable binder, thus, it's able to join two .exe files in one. Now, why should anyone want to do that, is a question apart (screenshot is self-explanatory
At the time I've wrote inPEct, most executable binders were similar to SFX ("Self-Extract") stubs: they simply extracted their content to somewhere (commonly %TEMP% directory). inPEct is a bit different, as it expands the host executable and encrypts & inserts the hosted executable inside it. When someone executes the bound application, the host executable runs normally, and the hosted executable is extracted and then executed. inPEct also has a feature to execute the hosted executable only once ('smart feature'): if the bound program is executed by user again, hosted file won't be extracted anymore. And inPEct is very fast and small, as  it's written entirely in pure assembler (in fact, inPEct's loader has only 800 bytes!). It's encryption algorithm is very cheap, but still uses a random seed. Thus, I expect that inPEct is more stealthy than similar binders.
Please note that almost every AntiVirus program detects and quarantines inPEct (and files produced by it)! This shows it's popularity in the past, I guess

But today it's useful mostly as a pure assembler programming example... And for AntiVirus research, as this paper actually shows.

• Convert from ACF (aircraft) & WPN (weapon) formats to TXT format and vice-versa.
  
• Extract AC3D model from TXT file, along with wings and propellers (using the real airfoils!).
• Import AC3D model into TXT file (fuselage, nacelles, wheel fairings & external fuel tanks only)
  

##############################################################################
[ACFTools v0.62a] Set of tools to play with ACF files outside of Plane-Maker
Perl script and modules coded by Stanislaw Pusep 
Site of this and another X-Plane projects of mine: http://xplane.sysd.org/

Allows you to:
 * export X-Plane (www.x-plane.com) aircraft data files to human-editable
   plaintext format and 3D mesh editable in AC3D modeler (www.ac3d.org).
 * import plaintext/3D mesh back to ACF file.
##############################################################################

Usage: acftools.exe  [parameters]
 o Commands:
	-extract [DEF]	: extract TXT from ACF (opt: using DEF definition)
        -generate       : generate ACF from TXT
        -merge          : merge body from AC3D file to TXT
 o Parameters:
        -acffile FILE   : name of ACF file to process
        -txtfile FILE   : name of TXT file to process
        -ac3dfile FILE  : name of AC3D file to process
        -noorder        : DO NOT sort vertices while merging bodies
        -noac3d         : DO NOT generate AC3D
        -(min|max)body N: write all bodies in specified range to AC3D
        -force LIST     : force extraction of bodies LIST (comma-separated N)
        -normalize N    : normalize wings to N vert/surface (N>=2 or no wings!)
 o Notes:
        * You can use abbreviations of commands/parameters (-gen or even -g
          instead of -generate).
        * The only required parameter for "extract" command is -acffile.
          Both -txtfile and -ac3dfile are derivated from it.
        * "generate" command and -txtfile has the same relation.
        * By default "extract" uses the latest DEF file.
        * "generate" doesn't need DEF at all (it is implicit in TXT)
        * If file to be created already exists backup is made automatically.
 o Examples:
        acftools.exe --extract=ACF700 --acffile="F-22 Raptor.acf"
        (extract 'F-22 Raptor.txt' from 'F-22 Raptor.acf')

        acftools.exe -e -acf "F-22 Raptor.acf"
        (same as above)

        acftools.exe -me -ac3d ladar.ac -txt "F-22 Raptor.txt"
        (merge *single* 3D body from 'ladar.ac' to 'F-22 Raptor.txt')

        acftools.exe -g -txt "F-22 Raptor.txt"
        (reverse operation; generate 'F-22 Raptor.acf' from 'F-22 Raptor.txt')

3fb2924c8fb8098dbc8260f69824e9c437d28c68  FC4-i386-disc1.iso
31fdc2d7a1f1709aa02c9ea5854015645bd69504  FC4-i386-disc2.iso
032455cdf457179916be3a739ca16add75b768b7  FC4-i386-disc3.iso
f560f26a32820143e8286afb188f7c36d905a735  FC4-i386-disc4.iso
736e1555e88740d6131c5c84fbe69ed1073ba82d  FC4-i386-rescuecd.iso

D:\_INSTALL_\stentz-binary-i386\FC4-i386-rescuecd.iso

expected:	736e1555e88740d6131c5c84fbe69ed1073ba82d
computed:	736e1555e88740d6131c5c84fbe69ed1073ba82d

SHA1 checksum OK!

Installation:

1. Unzip the "checksum.wcx" to the Total Commander or Windows Commander plugins directory
2. In Windows Commander 4.0 (or newer) or Total Commander, choose 'Configuration => Options'
3. Open the 'Packer' page
4. Click 'Configure packer extension WCXs'
5. Type md5 as the extension
6. Click 'New type', and select the "checksum.wcx" file
7. Click OK and then 'Configure packer extension WCXs'
8. Now type sha as the extension
9. Click 'New type', and select the "checksum.wcx" file again
10. Click OK
    

Usage:

(This section uses MD5 checksums as example; for SHA1 the procedure is the
same, just replace every "md5" you see by "sha" )

1. Generate MD5 checksum:
   1. Select files you wish to compute checksum.
   2. Then go to "Files => Pack".
   3. Select "md5" as packer.
   4. PLEASE NOTE THAT ARCHIVE PATH WILL BE IGNORED!!! ".md5" 'archive' is ALWAYS generated in current directory (where checked files are), and NOT in the opposite panel! The only exception is creating checksum of the files stored on CD-ROM media as there's no way to create files there.
   5. Press OK and check CURRENT directory for ".md5" list generated.
2. Verify MD5 checksum:
   1. Certify that ".md5" list is in it's right place (filenames listed in it should be relative to the current directory).
   2. Select it and do "Files => Test Archive(s)".
   3. If any file doesn't matches stored MD5 checksum then "CRC error" message box appears.
   4. If everything is clear Total Commander remains quiet.
3. Browse MD5 checksum list:
   1. Certify that ".md5" list is in it's right place (filenames listed in it should be relative to the current directory).
   2. Select it and enter it as it were a normal archive.
   3. If any file is present in the ".md5" list but wasn't found in the current directory then "?" is displayed instead of file date/time and size.
   4. PLEASE NOTE THAT FILES CAN NOT BE EXTRACTED TO YOUR DISK! ".md5" isn't an archive, it stores only the hash of the file.
   5. Select file you wish to check and press F3 (call Lister).
   6. Lister will show complete file name, expected checksum and generated checksum. If both checksum matches then the last line is "MD5 checksum OK!".

Installation:

1. Unzip rio.wfx & rio.cfg files to Total Commander directory
2. Choose "Configuration => Options => Operation => FS-Plugins"
3. Choose rio.wfx
4. Click OK.
5. You can now access the plugin in the "Network Neighborhood"
6. Open rio.cfg file and set the correct LPT port address (see below for more details)
   

Configuration:

# Assume that Rio is connected to LPT1
IOPort		0x378

# default
IODelayInit	20000
IODelayTx	100
IODelayRx	2

# "turbo" mode (UNSAFE!!!)
#IODelayInit	5000
#IODelayTx	1
#IODelayRx	1

• DOS (DJGPP, Turbo C)
• Windows 9x/NT/2K/XP (Borland C, Microsoft Visual C, MinGW)
• Linux (gcc)
• FreeBSD (gcc)

This one looks like and feels like the popular "Microsoft ® Registry Editor" (A.K.A. regedit.exe ), specifically one that comes from Win2k default installation.
It only has one (significative) difference... It will never prompt you with following message box, when started:

"Registry editing has been disabled by your administrator."

REGEDIT4

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System]
"DisableRegistryTools"=dword:00000001

regedit.exe

P.S. - reg3dit has nothing to do with the leaked Win2k source!!! I've created it by my own.