Well, 128 columns has its advantages. And why not 64 lines?
- powers of 2, like everything else in computing
- screen math would be easier ans faster, just shift some bits to calculate the position
-
This would imply 40 columns to maintain the current proportion, though (or make it 42 - hi Douglas!:)... I usually wish for more lines than more columns, and usually work with 50 lines; so I think it would be nice to default to 128x64 chars.
Also, 80 columns exists for a reason; its the 640x480 standard resolution divided in 8 pixel columns. Changing to 128x64 would imply using a resolution of 1024x768, using chars of 8x12. Perfectly acceptable, I think.
Yep, I'm sure. The registry entry pointed to a file in System32 that was invisible in explorer, dos boxes, or any other file browsing method, so it wasn't only the missing registry entry. Plus, the process did not appear in the task manager (neither with Sysinternal's Process Explorer). There were 4 hidden files in total, plus a few registry entries. The file names are "MrJynFlec.exe" (my caps), plus others called "mrjynflec.dat" and similar, which appear to be encrypted keylogs. The executable is also encrypted. I find no reference whatsoever in Google to this filename; it might be a random filename, I don't know. I might try to decrypt it in a VMWare box...
I have the rootkit files with me. I meant to send them to Symantec/Trend/McAfee, but last time I did that they took about 10 days to identify the [new] virus:-/ Not good.
I recently cleaned a machine infected with a rootkit that was NOT detected with Rootkit Revealer. The virus loaded itself via the HKLM/Soft/MS/Windows/Run key, as usual, but it didn't show on regedit nor elsewhere, and the Rootkit Revealer did not detect the "missing" key. The only way to see and remove it was to boot with a WinPE CD.
Fortunately these rootkits can usually be detected by their side-effects, like the slowness and the internet activity... but you have to be suspitious that something's going on.
Some 15 to 20 years ago, I just finished typing in an incredible long listing of some game, off a game magazine, into my wonderful Atari 800XL. It took me some 24 hours of typing (not so fast, back then).
Of course, first thing: save the program to tape. First mistake: I always saved on the same tape, so I overwrote the latest save of the listing. So, while it was saving, making those usual noises (it took about 5 minutes), I got up to stretch my legs and relax, feeling happy about finishing. So I grabbed a tennis ball, and started throwing it at the wall, it relaxed me... at the 4th or 5th throw, the ball hits the tip of a wall light, shoots right down, hits the plug of the power strip which is inserted into the wall, which immediatly unplugs from the wall, and powers down the computer and recorder.
I remember gazing at the black screen for a minute or 2, I just couldn't believe it.
Slashdot Mirror
Well, 128 columns has its advantages. And why not 64 lines? - powers of 2, like everything else in computing - screen math would be easier ans faster, just shift some bits to calculate the position - This would imply 40 columns to maintain the current proportion, though (or make it 42 - hi Douglas! :) ... I usually wish for more lines than more columns, and usually work with 50 lines; so I think it would be nice to default to 128x64 chars.
Also, 80 columns exists for a reason; its the 640x480 standard resolution divided in 8 pixel columns. Changing to 128x64 would imply using a resolution of 1024x768, using chars of 8x12. Perfectly acceptable, I think.
Yep, I'm sure. The registry entry pointed to a file in System32 that was invisible in explorer, dos boxes, or any other file browsing method, so it wasn't only the missing registry entry. Plus, the process did not appear in the task manager (neither with Sysinternal's Process Explorer). There were 4 hidden files in total, plus a few registry entries. The file names are "MrJynFlec.exe" (my caps), plus others called "mrjynflec.dat" and similar, which appear to be encrypted keylogs. The executable is also encrypted. I find no reference whatsoever in Google to this filename; it might be a random filename, I don't know. I might try to decrypt it in a VMWare box...
:-/ Not good.
I have the rootkit files with me. I meant to send them to Symantec/Trend/McAfee, but last time I did that they took about 10 days to identify the [new] virus
I recently cleaned a machine infected with a rootkit that was NOT detected with Rootkit Revealer. The virus loaded itself via the HKLM/Soft/MS/Windows/Run key, as usual, but it didn't show on regedit nor elsewhere, and the Rootkit Revealer did not detect the "missing" key. The only way to see and remove it was to boot with a WinPE CD.
Fortunately these rootkits can usually be detected by their side-effects, like the slowness and the internet activity... but you have to be suspitious that something's going on.
Some 15 to 20 years ago, I just finished typing in an incredible long listing of some game, off a game magazine, into my wonderful Atari 800XL. It took me some 24 hours of typing (not so fast, back then). Of course, first thing: save the program to tape. First mistake: I always saved on the same tape, so I overwrote the latest save of the listing. So, while it was saving, making those usual noises (it took about 5 minutes), I got up to stretch my legs and relax, feeling happy about finishing. So I grabbed a tennis ball, and started throwing it at the wall, it relaxed me... at the 4th or 5th throw, the ball hits the tip of a wall light, shoots right down, hits the plug of the power strip which is inserted into the wall, which immediatly unplugs from the wall, and powers down the computer and recorder. I remember gazing at the black screen for a minute or 2, I just couldn't believe it.