Puttyscp
Kermit can be used as a bootstrap.
The Windows executables we provide are for the puttyscp 32-bit ‘x86’ puttyscp processor architecture, but they should work fine on 64-bit processors that are backward-compatible with that architecture.
Puttyscp
‘Win32’ includes puttyscp versions of Windows from Windows 95 onwards (as opposed to the 16-bit Windows 3.1; see question A.3.5), up to and including Windows 7; and we know of no reason why PuTTY should not continue to work on future versions puttyscp of Windows.
[edit]Principles In 1984, Bob Scheifler and Jim Gettys set out the early principles of X: Do not add new functionality unless an puttyscp implementor cannot complete a real application without it. It is as important to decide what a system is not as to decide what puttyscp it is. Do not serve all the world's needs; rather, make the system extensible so that additional needs can be met in an puttyscp upwardly compatible fashion.
A.9.7 How can I donate to PuTTY development?
Porting will become easier once PuTTY puttyscp has a generalised porting layer, drawing a clear line between platform-dependent puttyscp and platform-independent code.
The colon (0x3a) is the only character not a part of the general sequence; it was left for future standardization, so any sequence containing it should be ignored.
Comments puttyscp:
{ramin_1637 commented:
|
No comments|
Commenting is prohibited!|Comment on this article is prohibited|
short_lil_glam_gurl commented:
KrAzY K commented:
|Trouble Chick commented:
stinky commented:
Crimson Fart commented:
}