Jump to content
xisto Community

dserban

Members
  • Content Count

    282
  • Joined

  • Last visited

Everything posted by dserban

  1. <sarcasm>Ronel, I want to vote for you to become a mod. Where do I sign up?</sarcasm>
  2. Me and the author of the article below think that since Alexa requires a toolbar otherwise the traffic is off the radar screen, their rankings are largely irrelevant. https://technosailor.com/2007/04/25/alexas-irrelevance/ Debate?
  3. Check out this super cool UNIX command line visual cheat sheet: http://forums.xisto.com/no_longer_exists/ I like it, although it has some quirks ("balt" instead of "halt") EDIT #1: Adding another one (not a visual one though, but still a cheat sheet), it's a hotlink to a PDF: http://forums.xisto.com/no_longer_exists/ EDIT #2: This article is reprinted from "The Official Ubuntu Book". While the cheat sheet is specific for Ubuntu Linux, most commands will work with other Linux distributions as well: http://forums.xisto.com/no_longer_exists/ EDIT #3: This one also provides links to online man pages: http://forums.xisto.com/no_longer_exists/ EDIT #4: Ubuntu Quick Reference (hotlink to a PDF): http://forums.xisto.com/no_longer_exists/ EDIT #5: 10 Linux commands you've never used - a must read in my opinion: http://forums.xisto.com/no_longer_exists/ EDIT #6: This is a linux command line reference for common operations: http://www.pixelbeat.org/cmdline.html
  4. Well, I didn't do anything special, but I just noticed how, as I kept posting more and more stuff, I went from newbie level 1 / member to newbie level 2 / hosted to active contributor, I just looked and saw that someone with 160 posts is an advanced member, someone with 210 posts is a premium member, and someone with 595 posts is a super member.So I think this is a function of the number of posts you made, and there are thresholds where you go from one level to the next.EDIT: Oh wait, I see that I too am an advanced member now, I guess it's because I went past the 100 posts threshold.
  5. I found this on Digg and thought it might be of interest for all of you digital artists out there. This is apparently something that Photoshop, CorelPainter, Krita (Linux package) and Paint Shop Pro do differently - it's called 'natural paint mixing', just like in real life painting. Demo video showcasing Krita: http://forums.xisto.com/no_longer_exists/ (I wish there was a way to embed YouTube videos in forum postings here, if anyone knows how to do it, please let me know, my experience so far has been that copy / paste HTML isn't rendered.) Informative background details about color mixing in Krita here: https://commit-digest.kde.org/issues/2007-08-12/ Some people have created a demo of how Paint Shop Pro does it. Also check out this forum posting about how CorelPainter does this sort of thing: http://www.conceptart.org/forums/showthread.php/103786-Color-mixer-gt-painting-feel Apparently in Photoshop it's done using layers and mixer / opacity control.
  6. Hmmmmm, good luck with that if people's IP addresses are going to be dynamically allocated by their ISP's every time they establish a connection.I suggest you learn more about how ISP's work - and do some reading on DHCP (Dynamic Host Configuration Protocol). Bottom line, it's not as easy as you may think it is.
  7. It depends on whether or not you want proxy detection.Use PHP's getenv() function to read the value of the environment.Your choices are:- Without proxy detection => REMOTE_ADDR - get the remote client's IP address- With proxy detection => HTTP_X_FORWARDED_FOR - get IP address of proxy server
  8. There is an ongoing discussion about the nature of PHP that is taking place in the shoutbox, and I think it should be moved into a topic in its own right. People seem to be divided into 3 camps. Some people are saying things like: "but php is a programming language..." "it is a full-fledged programming language; it's actually quite similar to c++, and also offers classes, which I consider a powerful feature" Then again others are saying: "by official definition I would imagine, I don't like thinking of it as one" "someone i know is making a php bnc, but in all other cases, Php is scripting to me" The third group of people chime in with: "well, sure it's a programming language, but it's still a scripting language. Traditional programming languages allow stand-alone applications, which PHP doesn't yet" I would like to start this formal discussion with an example of how you can run a PHP piece of code from the command line, outside of the context of a web rendering engine. When you download and decompress PHP, you end up with a directory that looks like this: CONSOLE C:\Apache\Apache\php>dir Directory of C:ApacheApachephp 08/15/2007 11:24 AM <DIR> . 08/15/2007 11:24 AM <DIR> .. 05/23/2006 08:00 AM <DIR> cli 05/23/2006 08:00 AM <DIR> dlls 05/23/2006 08:00 AM <DIR> extensions 02/16/2003 12:02 AM 32,881 install.txt 02/15/2003 11:20 PM 3,276 license.txt 02/15/2003 11:20 PM 36,823 magic.mime 05/23/2006 08:00 AM <DIR> mibs 02/15/2003 11:20 PM 142,387 news.txt 05/23/2006 08:00 AM <DIR> openssl 05/23/2006 08:00 AM <DIR> pdf-related 02/16/2003 12:02 AM 45,056 php.exe 02/15/2003 11:20 PM 3,872 php.gif 02/15/2003 11:20 PM 38,898 php.ini-dist 02/15/2003 11:20 PM 39,502 php.ini-recommended 02/15/2003 11:20 PM 7,952 php4embed.lib 02/15/2003 11:58 PM 1,282,048 php4ts.dll 02/15/2003 11:20 PM 169,956 php4ts.lib 05/23/2006 08:00 AM <DIR> sapi 08/15/2007 11:23 AM 47 standalone.php 07/13/2006 03:58 PM <DIR> uploadtemp 12 File(s) 1,802,698 bytes 10 Dir(s) 278,102,016 bytes free C:\Apache\Apache\php> Please note the existence of the executable php.exe. I created a little PHP piece of code in a file called standalone.php: CONSOLE C:\Apache\Apache\php>type standalone.php <? echo "I am a standalone PHP application." ?> C:\Apache\Apache\php> Let's imagine for a moment that Apache isn't installed on my PC and let's try to execute that PHP piece of code: CONSOLE C:\Apache\Apache\php>php standalone.php Content type: text/html X-Powered-By: PHP/4.3.1 I am a standalone PHP application. C:\Apache\Apache\php> There is a way to suppress the extra fluff at the beginning of the output, by specifying the "-q" (for quiet) flag: CONSOLE C:\Apache\Apache\php>php -q standalone.php I am a standalone PHP application. C:\Apache\Apache\php> Edit: I just realized now, after looking over my posting again, that putting stuff inside the console tag interprets the backslash as an escape character, so wherever you see C:ApacheApachephp - it was originally C:\Apache\Apache\php
  9. I found a pretty looking HTML table on some site and I would like to adopt it for all table-related content that I'm publishing at work. The table looks like this: and the site where I found it is: http://forums.xisto.com/no_longer_exists/ I have most of the stuff figured out, but my only remaining problem is that these two image files: and have the text embedded in them. Is there a well-written tutorial on the Internet that I can go read and figure out on my own how to get rid of those texts ("Play all songs" and "Play") while preserving the aqua look and feel of the image files? I don't have experience working with Photoshop, but I do have access to a PC where it's installed.
  10. This seems to be an emerging trend: bands selling recordings of concerts on USB sticks as you leave the venue. The Barenaked Ladies are reportedly selling their concerts without DRM on USB sticks, along with albums in the same format. Metallica have been doing this since 2003 and they actually take the time to mix it and make it sound good. The only drawback is sometimes it takes a couple of days to a week to finish it up. http://forums.xisto.com/no_longer_exists/ One issue is production costs. It is fairly costly to produce audio and video for an event like this, and to have the sticks ready for people to buy within like 10 minutes, or however long it takes for the applause to die down. But some people think this is financially doable. If someone was doing a serious bulk buy of 32 meg sticks, they could probably get them for 5 or 6 bucks a piece, sell the thing for 15 dollars and they are making some serious money. I can imagine a super-powerful UNIX server with lots of RAM and 4 CPUs cranking away at a big video file, copying it to a ... USB stick farm.
  11. Bonzi Buddy?https://en.wikipedia.org/wiki/Bonzi_Buddy One of the worst pieces of spyware. "Spyware isn't such a threat?" I beg to disagree. It can be a threat to your social life if you have a lot of contacts in your Yahoo messenger list and there a piece of spyware running on your PC without your knowledge bulk-sending an instant message like "hey sexy" (or even nastier) to all your contacts without your approval, of course.
  12. For the intranet where I work, I had a requirement that, after you kick off a long running database job, the PHP application should take you to a page that would display a progress bar for how much of the job was done, and the idea was that you had to go back to that page every once in a while and check the job's progress. However, it is very difficult to find a working and easy solution without using Flash. Well, I found a decent looking progress bar that is licensed under the Creative Commons license here: http://www.webappers.com/progressBar/ Now the only thing I have to do is add auto-refresh in the meta tag or a little bit of AJAX to spare the user the "pain" of clicking the Refresh button.
  13. The very idea of a terabyte of hard drive space available on my PC makes me salivate. I'm already thinking how long it would take to fill that up. I think by that time the first exabyte drive will come out. The article below takes the latest Hitachi Deskstar 7K1000 for a spin and tests its performance, noise levels, and power consumption against 18 other drives to find out how it stacks up. http://forums.xisto.com/no_longer_exists/ As for myself, I think I'll wait until the price comes down a bit, and I also think it's a good idea to let many other people test these drives out over extended periods of time. I will also wait for Seagate to come out with their version, because the Seagate drive will have a 5 years warranty, but this one has only 3 year warranty. Also, after reading around a bit more, some people seem to suggest that Hitachi drives have earned a nickname as "Deathstars" for dying so much. No comment there. It's a good comparative exploration of recent high-capacity drives, with the smart money being on the Caviar SE16 (750GB).
  14. This is a set of apparently well illustrated modification instructions to allow you to run your WRT54G router without external power supply. http://www.linksysinfo.org/index.php The site is very, very popular at the moment, so you may have to bookmark the page to check it later. Although this is a website dedicated to routers and networking products, I was barely able to pull the bare bones page down using wget. They may think of putting a leaner version of the page at some point. Anyway, the trick does not consist in somehow squeezing a battery pack inside, but instead there is a simple modification inside the router that implements Power Over Ethernet (POE). You can power the router through the CAT5 cable. So instead of having a power supply plugged into your router, you have a power supply plugged into the other end of a CAT5 cable. Still a power supply. By reading around some more, some people suggest that this isn't even a mod. Their WRT54G routers have never had the power supply plugged in, they have just always been powered over the Ethernet. Below the text I was able to pull down with wget:
  15. I'm wondering if there is a way - like a hardware test - to determine whether you have such a Fritz chip in your recently purchased computer.
  16. The title says it all. http://forums.xisto.com/no_longer_exists/404.png I don't think this is some person's actual PC. I think it's just a test PC used by an anti-spyware software company to test how toxic this spyware soup would be. Like to test whether various types of spyware would "jump at each other's throats" so to speak. Although to be fair I did spot the VMWare systray icon right next to the clock, so that says something.
  17. This a very useful PHP tutorial page for people who have never attempted learning PHP because it looks confusing to them. This site is going to change that, and humor is also included. http://forums.xisto.com/no_longer_exists/
  18. This is a very well-written article explaining all the ways in which aptitude is superior to the built-in Debian / Ubuntu package management tools. As a courtesy to the author (he's been having severe bandwidth problems due to the huge popularity of his article, he has a small PIII 700 with 192MB RAM in his basement hosting the post - his database just can't keep up), I am posting here a copy of the article, as well as the direct link at the end of this posting, for completeness. Link: https://pthree.org/2007/08/12/aptitude-vs-apt-get/ Edit: I just realized I don't know how to make it render the HTML inside the quote tags, and the BB code help doesn't help. Ideas anyone?
  19. This an article entitled "Google, Microsoft and Apple building online storage havens: you win" I just found on digg. http://forums.xisto.com/no_longer_exists/ My comments: - Yes, I suspected that ever-growing gmail storage space wouldn't last forever. Caveat: check this out: "Gmail Going Huge: 9000MB+" http://mashable.com/2007/08/09/gmail-going-huge-9000mb/ - They can promise you 50 GB of online storage, but if they are going to impose limits on the file size, that's going to make the whole thing worthless. - I'll be sticking with my existing options for storing large files for now (skaffers.com and uploadingit.com, both of them free) unless and until I find a better service.
  20. SSH is an important tool in Linux / UNIX and an amazing piece of software. It's one of the top 2 or 3 things that an experienced Linux / UNIX system administrator uses every single day. People use SSH to connect to their home machines from work and to their servers from both work and home. People use SSH in backup scripts. People use SSH for lots of other things. There is some interesting history about SSH - it was originally developed by some company and the original versions were actually open-sourced, and then they closed it up at some point but then some other developers took the last open source version and created a new open source release which was then later picked up by all the OpenBSD guys and turned into OpenSSH, which is the actual piece of software that we all use (ssh being one of the tools that comes with OpenSSH). Basically, SSH is a secure replacement for telnet. It lets you network in remotely to machines from other machines (either across a local network or through the Internet), so you can access a server that is sitting across the room as easily as you can access a server that is on the other side of the world, or you can access your workstation that is sitting in the basement of your house from your laptop while you're sitting upstairs. It's very secure both in the connection as well as of course in the transmission of the data back and forth. I'm hesitant to say it's totally secure, knowing what I know about another technology called IPSec. SSH encrypts the data at the TCP level. IPSec, as the name implies, encrypts the data at one level below in the OSI model, the IP level, which makes it more secure than SSH. SSH is so essential that every distribution comes with it. I would be really surprised if there was any distribution that didn't. So you can open up a terminal and type: man sshand find some information about SSH.The SSH configuration files are in /etc/ssh typically. There are two files in there: ssh_config (the configuration file for the SSH client) sshd_config (the configuration file for the SSH daemon / server) How you start, stop or restart SSH usually depends on the distribution, but in most of them you would type at the command prompt as root - or by prepending sudo: sudo /etc/init.d/sshd (start|stop|restart|status)So how do you use it?Let's come up with a hypothetical scenario. Let's say you have a Linux server in the basement, and let's say the machine is called "server" and then let's say you have a laptop, and you want to be able to connect to your server from your laptop, and let's say your server has two users defined on it: root (obviously) and a regular user called joe. Let's say the laptop runs Linux and also has users root and joe. So you have the same users on both machines. You need to start the SSH daemon on the server machine, then, from the laptop, open up a terminal and simply type: ssh serverThat's all you have to do to start with.Now a couple of things are going on here. First of all, by not using a user name in the command, SSH assumes that you are going to try to ssh in as the same user that you are logged in as on the laptop. So if you are logged in to the laptop as joe, you will be ssh'ing into the server as joe. You don't need to include that because it's the same user. If you want to log into the server machine as a user other than the one you are logged in as on the client side (root, for example), you would simply type: ssh root@serverAnd then the other thing that's going on here is using the word "server". That's the machine name of the computer you want to connect to, and that's assuming that on your network you can find that name. You can always edit your /etc/hosts file and put the IP address of the machine in there and associate it with the string of characters "server", as another way to connect the IP with the name.You can also use an IP address in the ssh command, so you could also do: ssh 192.168.1.50if that is your server's internal IP address. When you first try to ssh into the server from the laptop, you will see on the laptop screen, in your terminal, some text that prompts you to accept the fingerprint of the machine you are trying to connect to. Basically, the laptop is going to "save the fingerprint" of the server that you are connecting to. That way in the future it can recognize that it's the same machine, the idea being that this way if some other machine is pretending to act as your server and doesn't have the same fingerprint, the ssh client will immediately warn you that the fingerprints don't match. That fingerprint gets added to a file called known_hosts on the laptop, in a hidden directory called .ssh in your home directory. That hidden .ssh directory is where all of your ssh-related user files are kept. At this point ssh will ask you for the password of the user joe on the server machine, you type it in and you're in. That's it - very easy, very secure (the whole thing is encrypted from the beginning to the end, the connection itself where you type the password is encrypted all the way along the way). Something else that you can do with SSH is you can use a facility / command called "secure copy" or scp. It acts just like the cp command (the Linux copy command), except the copying process is taking place in a secure manner. To give an example, let's say you have a file called file1.txt on your laptop, and you want to copy it over to joe's home directory on the server. On the laptop you would open up a terminal and type: scp file1.txt server:file1.txtBasically, it's the same convention as with cp - you enter the command name, and then the first argument is the name of the file you're copying, and the second argument is the destination. Technically, the destination is the fully qualified file name (with the full path prepended to it), so you would really type server:/home/joe/file1.txt (and of course you can use the ~ character instead of /home/joe).That will copy file1.txt from the laptop over to the server, using scp, which is basically secure copy over SSH. That's fairly easy and straightforward, but what I would encourage you to check into and adopt is the concept of public and private keys with SSH. There is a lot of information out there about the whole idea of cryptography using public and private keys, so I won't get into it in very much detail. Basically, you create a private key and a public key that kind of fit together and work together to "unlock the secret" (unlock the e-mail in the case of GPG or unlock the connection in the case of SSH). It's a way to make a connection without using passwords and it will only work if you have both the private and the public key together - they have to fit together and you can't figure out the private key from having the public key. The public key is supposed to be out there, given away, put on other machines, given to other users (in the case of GPG) etc... and you keep the private key to yourself. The idea of using public and private keys is really great because it does 2 things. One is that it's more secure than using a password, simply because passwords can be compromised more easily than you can imagine, unless you are really good at remembering a really long random alphanumeric password. Public and private keys really can't be compromised. I'm sure theoretically of course anything is crackable, but in practice, these types of public and private keys have not yet been cracked, so it's very, very secure, much more secure than using passwords. The other benefit of using public and private keys is that it makes the SSH connection completely seamless. In our previous example, we had to enter joe's password on the server machine, but with keys you don't need to enter passwords. To accomplish that, and supposing we are logging in as another user (different from the one we are logged in as on the client side), we are going to create a key pair on the client machine. In the terminal, we would type: ssh-keygen -t rsaThis will create 2 files in the .ssh directory: id_rsa and id_rsa.pub, with id_rsa.pub obviously being the public key.So now that we have both the private and the public key on the laptop, the idea is that we need to get that public key over onto the server somehow, because when we connect to the server, we will have the private key on the laptop and the public key on the server, the two will match together, and our session will be authenticated, and we can come right in without any password. It is very easy to copy a key over: you go into the .ssh directory on the laptop, and you type: scp id_rsa.pub server:/home/joe/.ssh/.and that would just copy the file over to the server.And there is still another step. You now need to ssh into the server and cd to the .ssh directory: ssh joe@servercd .ssh... and so joe is in the hidden .ssh directory, where that id_rsa.pub file now resides. Look for a file called authorized_keys, and if it's not there, type the following: touch authorized_keysThat authorized_keys file is going to contain all the public keys of the users who are connecting to the server, but now there is nothing in it yet, so type the following: cat id_rsa.pub >> authorized_keysand what this command is doing is it's taking the contents of the id_rsa.pub file and appending it to the bottom of the authorized_keys file.Make absolutely sure that you use two "greater-than" signs - you don't want to overwrite the contents of the authorized_keys file, should any keys have previously been stored in it. At this point, joe should be able to open up a new terminal and type: ssh joe@serverand he should be logged in right away without having to enter any password. Because it doesn't ask for any passwords, this is actually very handy because it opens up a whole new world of possibilities for securely automating administrative stuff. You can kind of see now some of the things you can do with it: scripts that do automated backups over SSH, business application interface file transfers ... there are all different kinds of things that can be done when you have these public and private keys. But obviously the important thing is that you don't want to lose your private key that is stored on the laptop - that is the real bottom line security issue. That, in a nutshell, is basically the way to use ssh with public and private keys. I will describe the configuration and security stuff further down below, but there is one little neat trick with ssh - one of the other switches for the ssh command is "-D", and that stands for "dynamic". What that does is that, if you put a port number after it, it will let you sort of tunnel an SSH connection to a local port. It specifies a local "dynamic" application-level port forwarding. You can use it as a web proxy. An example of this is the following: ssh joe@server -D 8080from a terminal on the laptop, and you're connected. Now, what you can do with a browser like FireFox or Konqueror is you can go into the advanced preferences in the section where you have the option to manually set the proxy server, go down to the SOCKS proxy configuration line, and in the first box enter localhost, and then in the port box enter 8080, and then confirm / save it. The next time FireFox is going out to browse a web page, it is going to be tunneling its web browsing through SSH. You can actually verify this with one of those sites that shows you your IP address, like http://www.ipchicken.com/ ... what I've done is I've opened up FireFox, gone to ipchicken, looked at my IP address, then I've done this ssh thing with the "-D 8080" option, changed the proxy settings in the browser, refreshed the ipchicken page and my IP address had changed, because I'm now browsing through the server, through the remote machine. It's very handy if you're in places like hotspots, where you may be concerned about people sniffing or whatever is being tracked through your web browsing - you can just connect to another machine over SSH and pull down this dynamic port to your local machine on 8080, change your browser's proxy settings, after which your browsing will go through your encrypted SSH session - very slick. There is a FireFox extension called SwitchProxy ( http://forums.xisto.com/no_longer_exists/ ) which lets you create "proxy profiles" so you can have one without this SOCKS setting, for just normal browsing when you're at home and you're not worried about invasion of privacy, and then one with the 8080 proxy SOCKS setting for when you're wanting to do this SSH tunneling thing. Some basic security things with SSH that I would recommend: One thing I would do is go into the /etc/ssh directory and then open up for editing the sshd_config file (again, this is the configuration file for the SSH daemon), so this would be on the server machine, not the laptop, because you want to make the security changes on the machine that is going to be offering up SSH. The first thing you want to do is change the default port from its default of 22 - that's very simple to do. It's amazing - someone I know had a web server and they had the SSH listening port set to 22 for one single day before he got around to changing the default port (he had everything set up with passwords so he wasn't worried about anyone actually getting in) but at the end of that day he was checking the logs with LogWatch, which is a great little utility that parses through your system logs and you can set it up to e-mail you a daily log of everything that had been going on with the server, and it listed all the SSH attempts, and he said it must have been like a thousand in that one single day, and it was all of course script kiddie scripts and bots, but it was amazing because it was showing you the attempted user names, and it just went through the alphabet, but it's pretty frightening actually that they would try all these different random names that were in this script and see what works and I guess that if they find one that connects, then they'll just start doing a dictionary attack on the passwords. So, anyway, what I would do is definitely change the default port from 22 to just some random port number - pick a high number (you know, 11500 or something), and of course, whatever port you end up using, if you are going to connect from the outside world to your machine, don't forget about your firewall and your NAT router. You will need to set up a port forwarding rule to forward whatever port it is to the machine that's going to be serving up the SSH server (just like with any service that you've got running behind your firewall, if you want to get to it from the outside, you have to forward that port to that machine). A couple of other tweaks to the sshd_config file: I would change the protocol from 2,1 to just 2 - that's because SSH protocol 1 is slightly less secure. Most things that I've come across suggest changing that to 2 only. I would also disable root logins (you will see a line in there somewhere that needs to be set to PermitRootLogin noit's usually either set to yes or the line is commented out, which also gives it a default meaning of yes). And if it's yes, it means the root account on the server could ssh in - you don't want to do that, just from a security standpoint. You want to limit it to just regular users, and then, once you've connected in through ssh, if you need to do something that requires root privileges, just su to root or do the sudo thing - that way someone would have to get through two levels to get to a root level of authorization, they would have to go through SSH with a regular user, and they would also have to know your root password. So disabling root logins is a good idea.The last thing I want to mention is somewhat dangerous. Once you get your public and private keys set up, if you want, look through this sshd_config file and you will see a couple of lines in there about disabling passwords entirely - meaning it will only look for keys. SSH by default will first look for public-private key combinations, and then it will ask you for passwords, if it doesn't find the keys. So you can set it up to just take keys only, and that's pretty secure because using a public-private key combination is better than using a password, but that also means that if you lose your private key you can't get in (at least remotely) - you would have to go sit in front of the server and log on from the physical console and change it back to allow passwords to be able to ssh in. But that's an option to keep in mind. That, in a nutshell, is SSH. There is a lot more you can do with it. You can for example forward X sessions, meaning you can run graphical applications over SSH. If you're using Windows and need to SSH into a Linux / UNIX box, your first option is to use the command line tool ssh.exe that comes with cygwin, as a second option look for an open source program called PuTTY, which is a full-blown SSH client with the ability to create key pairs, and it can also deal with pre-existing pairs.
  21. No.The idea is that you need to kick-start this house keeping process and have only one instance of it running at any point in time.I can imagine that you would have an administration / superuser section for your game, where you pull all kinds of levers to control the game.The above code would be part of a page in this administration section called "Kick-start housekeeping process".The link to this page would be active if the process is not already running, and would be greyed out or missing altogether if it is.Or something to that effect, it's really up to your imagination, personal preference and talent for designing systems.
  22. This is an article from a guy with an obviously very inquisitive mind who isn't afraid to dive deep into the registry and uncover funny / scary internals. http://forums.xisto.com/no_longer_exists/ A couple of things caught my attention: - less drive thrashing. Huh? What does this say about Vista to a person who has never used it? Do you mean to tell me that a vanilla installation of Vista is grinding away at your hard drive by default? - the new option to create a recovery disk. - SUA (Subsystem for UNIX Applications) - Microsoft's response to cygwin?- After you resume the computer from hibernation, the computer loses its default gateway address? Nice job.
  23. I wish I had a powerful enough portable laser device that makes traffic cams permanently blind.
  24. By the way Alegis, are you happy with NetLimiter? Which features are you using from what it offers?I was tempted at some point to install it, I downloaded the installation kit, but never got around to actually installing it.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.