As mentioned in the replies to my above post about using a wire mesh (i.e. cage), a steel cage wouldn't cut it; it would only cut out the really high frequencies (i.e. 300MHz) but not the really low frequencies (in this case, 60Hz), so a solid steel sheet would be necessary.
-- Sig (120 chars) -- Your friendly neighborhood mIRC scripter.
I'm not sure... would a steel mesh also work for this? I know Faraday cages will block radio waves and electric discharges, but I'm not sure if they block magnetic fields as well.
If it did, it'd probably be a bit cheaper than a big steel plate...
-- Sig (120 chars) -- Your friendly neighborhood mIRC scripter.
As I mentioned, you can also try putting in an invalid address (like 0.0.0.0 or 255.255.255.255); this way, WinSock will immediately dump the connection with a "Can't assign requested address" error. This makes things go nice and fast with Netscape 4.x and IE, though I'm not sure how Mozilla behaves.
-- Sig (120 chars) -- Your friendly neighborhood mIRC scripter.
...that I find rather useful is to effectively blacklist the adbar sites. One way to do this (on your own system) is to add them to your hosts file (either c:\windows\hosts or/etc/hosts) to resolve to something like 255.255.255.255 or 0.0.0.0 (sample line: "255.255.255.255 ad.doubleclick.net"); most TCP/IP stacks (read: Winsock) will immediately error and refuse to connect to such IPs. If that doesn't work, put 127.0.0.1 instead and run a tiny program on port 80 to give a null response on all connect attempts (or just immediately disconnect).
It's also a good idea to add in some of the 'nasty' sites the trolls post on/. (like goatse.cx), so if you accidentally click on such a link, you'll just get an error message instead of actually seeing the page.
-- Sig (120 chars) -- Your friendly neighborhood mIRC scripter.
On a similar note, under Win95+Plus! or Win98:
Go to Display control panel, go to the Plus! (Effects in win98) tab and toggle the "Show icons using all possible colors" option. When you apply, you will be told that "For this change to take effect, you must restart your computer." i.e. reboot. Even if the system is multiuser (and the option is specific to each user). You only have to logout/login for the change to take effect.
-- Sig (120 chars) -- Your friendly neighborhood mIRC scripter.
Ah, but with Windows 3.1, you just exited Windows (to MS-DOS) and restarted it (win.com); with Windows 95, the entire system would reboot (from what I recall, anyways; using win98se right now).
Sometimes, if you're lucky, Windows will just restart itself without rebooting the system.
-- Sig (120 chars) -- Your friendly neighborhood mIRC scripter.
Somehow, it fails to make sense to me that switching between Small Fonts and Large Fonts should require a reboot (atleast under win9x), since a reboot is NOT required if you change any of the individual font sizes in the Display control panel...
-- Sig (120 chars) -- Your friendly neighborhood mIRC scripter.
Firewall wouldn't work, since the connection would go to 127.0.0.1 (which would never touch firewall).
Right now, I just use mIRC and have it do "/socklisten fakehttp 80" on startup. Crude, but works effectively.
Another way that will work with Win9x systems is to make the adbar sites resolve to 255.255.255.255 instead of 127.0.0.1. Winsock is known to give up on some IP addresses the instant you tell it to connect to them, knowing that they are invalid. Works fine with IE5.5 and Netscape 4.7x.
-- Sig (120 chars) -- Your friendly neighborhood mIRC scripter.
Or do what many other people (including myself) do:
Put the adbar sites in/etc/hosts (or C:\WINDOWS\HOSTS, for Windows users like myself) to resolve to 127.0.0.1, and then run a program to listen on port 80 (have it accept connection and then immediately disconnect; that way, you don't have to wait for connection to time out in your browser). All you get in your browser is an empty box with either an "image not loaded" icon or a "broken image" icon.
-- Sig (120 chars) -- Your friendly neighborhood mIRC scripter.
The only major benefits they offer are durability (very good for kids who like to toss cartridges around, whereas CD's will scratch rather easily) and piracy protection, at least until the standard is reverse-engineered by some enterprising bootleggers.
One other factor you have to take into account is speed. Cartridges will always be faster than disks, since you don't have to copy the data from the disk into the system's memory; the data is already visible in Read-Only Memory. The high latency of disks (milliseconds) also plays a role here, compared to the latency of ROM chips (nanoseconds).
This is one of the reasons why some people preferred the N64 over the PSX; the N64 didn't have any of the annoying "Loading..." screens and long delays.
-- Sig (120 chars) -- Your friendly neighborhood mIRC scripter.
Also seems there was no such article on forbes in the first place... a search for "censorware" got no matches, and searches for "akamai" and "censor" didn't get anything relevant.
-- Sig (120 chars) -- Your friendly neighborhood mIRC scripter.
But you can stick four of them side by side and get 64 bits without much difficulty (except maybe purchasing and affording them;-) ).
Sounds like a nice idea, but, as I recall, manufacturers were having a hell of a time just getting THREE RIMM slots on a motherboard because of the picosecond-accurate timing necessary.
Of course, that could be a completely different issue.
-- Sig (120 chars) -- Your friendly neighborhood mIRC scripter.
But remember, you're talking about the x86 here...
We all know that RISC processors (i.e. Alpha) are faster and better than CISC processors (i.e. x86), but that hasn't stopped Intel yet...
-- Sig (120 chars) -- Your friendly neighborhood mIRC scripter.
considering that NT normally doesn't let you have files with names like.signature (it'd have to be "my.signature" or preferably "JWEILL.SIG").
Really? I thought NTFS supported that. Then again, I could be wrong...
I know that Windows 9x's LFN support allows such filenames (I've got one such file on my system right now), though their 8.3 components look slightly ugly.
-- Sig (120 chars) -- Your friendly neighborhood mIRC scripter.
Slashdot Mirror
On the contrary, it DID point to slashdot.org a few minutes ago, though it seems to be fixed now, along with the cuecat/python links.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
While I was in the process of tracking down the /. articles, the links in the article automagically fixed themselves. Oh well. :)
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
As mentioned in the replies to my above post about using a wire mesh (i.e. cage), a steel cage wouldn't cut it; it would only cut out the really high frequencies (i.e. 300MHz) but not the really low frequencies (in this case, 60Hz), so a solid steel sheet would be necessary.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
That answers my question :)
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
I'm not sure... would a steel mesh also work for this? I know Faraday cages will block radio waves and electric discharges, but I'm not sure if they block magnetic fields as well.
If it did, it'd probably be a bit cheaper than a big steel plate...
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
As I mentioned, you can also try putting in an invalid address (like 0.0.0.0 or 255.255.255.255); this way, WinSock will immediately dump the connection with a "Can't assign requested address" error. This makes things go nice and fast with Netscape 4.x and IE, though I'm not sure how Mozilla behaves.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
Thanks, that's the one I got :)
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
...that I find rather useful is to effectively blacklist the adbar sites. One way to do this (on your own system) is to add them to your hosts file (either c:\windows\hosts or /etc/hosts) to resolve to something like 255.255.255.255 or 0.0.0.0 (sample line: "255.255.255.255 ad.doubleclick.net"); most TCP/IP stacks (read: Winsock) will immediately error and refuse to connect to such IPs. If that doesn't work, put 127.0.0.1 instead and run a tiny program on port 80 to give a null response on all connect attempts (or just immediately disconnect).
...
/. (like goatse.cx), so if you accidentally click on such a link, you'll just get an error message instead of actually seeing the page.
A good list of adbar sites to blacklist:
ads.1for1.com
connect.247media.ads.link4ads.com
ads.admonitor.net
ads.amazingmedia.com
view.avenuea.com
image.avea.a7.avenuea.com
www.banerz.com
www.burstnet.com
www.commission-junction.com
ad.doubleclick.net
netgrav.ea.com
adimg.egroups.com
js-adex3.flycast.com
ad-adex3.flycast.com
jeeves.flycast.com
ads.focalink.com
ads01.focalink.com
ads02.focalink.com
ads34.focalink.com
ads35.focalink.com
w25.hitbox.com
www.hostreview.com
adforce.imgis.com
ad.linksynergy.com
ads.msn.com
ads.mysimon.com
server3.pennyweb.com
adserver.ugo.com
oz.valueclick.com
www.virtuads.com
a32.g.a.yimg.com
a372.g.a.yimg.com
us.a1.yimg.com
It's also a good idea to add in some of the 'nasty' sites the trolls post on
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
On a similar note, under Win95+Plus! or Win98:
Go to Display control panel, go to the Plus! (Effects in win98) tab and toggle the "Show icons using all possible colors" option. When you apply, you will be told that "For this change to take effect, you must restart your computer." i.e. reboot. Even if the system is multiuser (and the option is specific to each user). You only have to logout/login for the change to take effect.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
Ah, but with Windows 3.1, you just exited Windows (to MS-DOS) and restarted it (win.com); with Windows 95, the entire system would reboot (from what I recall, anyways; using win98se right now).
Sometimes, if you're lucky, Windows will just restart itself without rebooting the system.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
Somehow, it fails to make sense to me that switching between Small Fonts and Large Fonts should require a reboot (atleast under win9x), since a reboot is NOT required if you change any of the individual font sizes in the Display control panel...
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
Actually, only the Part II Page 1 'The DRAM "read" revisited' link is broken; all of the others work fine.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
Oh, forgot to mention...
if there's no hosts file, look for hosts.sam to see the proper syntax.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
Firewall wouldn't work, since the connection would go to 127.0.0.1 (which would never touch firewall).
Right now, I just use mIRC and have it do "/socklisten fakehttp 80" on startup. Crude, but works effectively.
Another way that will work with Win9x systems is to make the adbar sites resolve to 255.255.255.255 instead of 127.0.0.1. Winsock is known to give up on some IP addresses the instant you tell it to connect to them, knowing that they are invalid. Works fine with IE5.5 and Netscape 4.7x.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
Or do what many other people (including myself) do: /etc/hosts (or C:\WINDOWS\HOSTS, for Windows users like myself) to resolve to 127.0.0.1, and then run a program to listen on port 80 (have it accept connection and then immediately disconnect; that way, you don't have to wait for connection to time out in your browser). All you get in your browser is an empty box with either an "image not loaded" icon or a "broken image" icon.
Put the adbar sites in
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
This is one of the reasons why some people preferred the N64 over the PSX; the N64 didn't have any of the annoying "Loading..." screens and long delays.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
Also seems there was no such article on forbes in the first place... a search for "censorware" got no matches, and searches for "akamai" and "censor" didn't get anything relevant.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
Interestingly enough, I seem to remember N2H2's "Bess" blocking babelfish.altavista.com at one time (still does?), most likely for that very reason.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
Of course, that could be a completely different issue.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
What about flow control? A program becomes somewhat limited if you can't do a conditional (or unconditional) branch.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
But remember, you're talking about the x86 here...
We all know that RISC processors (i.e. Alpha) are faster and better than CISC processors (i.e. x86), but that hasn't stopped Intel yet...
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.
I know that Windows 9x's LFN support allows such filenames (I've got one such file on my system right now), though their 8.3 components look slightly ugly.
-- Sig (120 chars) --
Your friendly neighborhood mIRC scripter.