Really, all you need to do (both as virus and anti-virus program) is install your own Int 0x13 (disk services BIOS) and Int 0x21 (DOS services) handler. AFAIK, no viruses actually attempted to patch DOS code, since this makes it bloated. Some virus, however, relocate themselves into unused DOS data segments.
You still have access to prestine Int 0x13 entry points, though. It can be found in ROM-BIOS. If you're an anti-virus software writer you should know that, rather than trusting the actual interrupt.
By the way, I used my own Int 0x13 handler to circumvent diskette protection of a chess game, without patching the game itself.
Documentation of DOS came in the form of printed manual (or on-disk reference), and not as a website. It was otherwise fairly accessible.
I guess other troublesome cyrillic characters include U+0435 ("es", looks like small e), U+043e (looks like small o), U+0440 ("er", looks like small p, derived from greek letter "rho"), U+0441 ("es", looks like small c), U+0443 ("u", looks like small y), U+0445 ("ha", looks like small x), U+0455 ("dze", looks like small s).
Other spoofing candidates are from the latin extended region, for example U+0131 (dotless i) and some characters with accents that are rendered too small to see clearly on screen, for example, double grave or inverted breve.
The IPA extensions also provide some candidates: U+0251 (an alternative latin a without the top hook); U+0261 (alternative latin small g).
Okay, I get tired of enumerating the possibilities. Rather than trying to be a karma whore, I just want to point out for the last thing that vast majority of Chinese unicode has already suffered this problem. When unicode produced unified CJK characters, they admitted some variants of ideograph that only have minor difference (perhaps some are in the main unified section and some in the compatibility section). It's impossible to tell the difference in small point sizes. The reason why those characters have so many variants in the first place is because they're both structurally complex and frequently used. Also, there is a separate section for CJK radicals. Some radicals are valid ideographs, appearing twice in unicode.
On Mac OS X, there is a small, free software program called "Desktop Manager" that provides multiple desktops. You can configure the desktop "transition" to look as if it's a multiple faced cylindrical polygon (where each side face is rectangular) rotating. This transition is advertised as cube rotation rather than polygon rotation, but you can have more than 4 desktops/faces, and it certainly doesn't make a cube.
Approval from the OSI is required for all open-source licenses, which are used on thousands of products, from the Linux operating system to the Firefox Web browser. As open-source software expands in popularity, though, the number of open-source licenses is growing, which opens up myriad legal questions and creates some confusion over the definition of open-source.
I'm not sure I like the idea that OSI is pitching itself as "the authority" of license evaluation. Although it is a lot easier to ask the question, "is license A approved by OSI" to mean "is the software licensed under A open source for me" but the question is flawed. One has to recognized that free software licenses are not created equal. The difference of them, and the choice involved, is what makes open source great.
Some towns have ordinances that ban public burning of anything at all. Burning in the public is a safety hazard. It also produces unpleasant fumes that are an environmental hazard. If smoking in the public is to be banned for the polution it causes, certainly flags shouldn't be an exception. It is especially important that flags made with nylon (which are more durable in extreme weather conditions) are not to be burned, since burning nylon produces dioxin.
I'm all for freedom of speech expressed in the form of flag shredding, though.
I guess this is too late a suggestion, but the left page would look very nice if the text aligns also to the right margin (except for the last line). The way text just falls off to the next line makes it look "grassy," or simply someone who hasn't shaved in a week.
I decided to run to the closest Barnes and Nobles before they close at 9pm, and bought a copy of NY Times.
On the left page, the names in the solid black print are legible, but the area covered by shaded graphics looks fudgy due to halftoning of greys. However, it seems that no name was masked in the two white "comma shaped" highlights. They printed the names around the white hallow.
I'm not sure how you could refute the official objective caml license, which clearly states that runtime system and standard libraries are licensed under LGPL (to allow linking with commercial programs), and the compiler and tools are licensed under QPL, which allow you to distribute unmodified code as is, or your modification "in a form that is separate from the Software."
The example given in QPL is using patches, but I don't see why you can't fork the source, since it would still be "separate" (just don't call it Objective CAML, but something else). QPL does not say your modification has to be in the form of patches.
I decided to repeat the author's experiment, i.e., put the powerbook to sleep, unplug the firewire drive that is previously mounted, then wake the computer up. When my powerbook wakes up, it still sees a ghost image of the firewire volume (I suppose due to cache) and I could navigate as much as what the cache has retained. Once I go beyond, the system tries to read from the drive and realizes it's gone, then unmounts the drive and pops up a dialog box telling me I should gracefully unmount the drive before I unplug it.
Brutely unplugging a drive while it's mounted really isn't a big deal nowadays, that we have journalled filesystem. Filesystems like reiser4 feature atomic operation, so it would be provably robust against brute removal. You only ought to worry if you're still using FAT (for example, digital cameras). Maybe the author should have acknowledge this "bug" being dependent on the filesystem, but then, this is beyond an end-user's (possibly also the author's) knowledge.
If you look at the BSD family tree here, you'd see that at one point in time, all Free/Net/Open BSD changed to use the codebase from 4.4BSD Lite, the unencumbered version.
"it looks like a great way to turn a lot of people off MSIE without just cause"
Yeah?! I'm still nodding along...
I never recall seeing a story with negative MSIE coverage that comes from an individual user. MSIE bug stories that I read were all reported and acknowledged by security companies who have a phone number to call if you don't like what they're reporting.
It makes me wonder why people bashing firefox or defending IE aren't willing to stand up to their words with their reputation (or they simply have no reputation so to speak). Are they all related to the same FUD department funded by a certain company or what?
If it makes you feel happier... everything bad I hear about MSIE come from security bulletins of well-known reputation, and later acknowledged by Microsoft for a security patch release. I don't think your assessment is fair to accuse people of believing in hearsay and cutting more slack for Firefox.
do you leave firefox in a page with flash animations? nowadays many of the animated figures in a web page are flash and not animated gifs anymore. a badly made flash can take up tons of CPU even when you leave it there. also, are you viewing web sites with automatic page refreshing? it will eat up the CPU everytime the page refreshes.
if that bothers you, you can always use the task manager to set the process's priority to either "below normal" or "low".
however, games are memory intensive. so as a browser, which uses memory caching to be fast. when real memory is used up, "thrashing" occurs (to swap some memory pages to the disk). even adjusting task priority won't help here, since thrashing is inherently slow. whenever a web page that you leave in the background refreshes itself, the OS has to swap out a few pages of game memory and swap in memory pages for the browser. as the game continues, it needs the memory back, and the OS has to juggle around memory pages again.
if you see a periodic frame loss, then self-refreshing web pages are definitely the culprit.
If an accident happens, one can use the collected data to show that auto manufacturer is at fault, and this can be a powerful support when filing insurance claim. On the other hand, providing this data should be voluntary. The owner should be able to deny any other party's request of such data, if this cannot be used to his/her advantage. I'm not sure if allowing the device to be turned off is a good idea, as the driver may forget to turn it back on again.
Build failure can be caused by the following: (1) the code has problem with the gcc version you use. or (2) library dependencies are not installed. The first could happen if they bumped the version of gcc used. I think programs written in c++ are more prone to this problem. For the second possibility, if you upgraded your existing installation, it may be the case that your old -devel packages were obsoleted by new versions of the library, but the new version -devel is not picked up during installation. If you installed anew, then you definitely should install the -devel packages again. Definitely check your dependencies again.
Also, mp3 hasn't been included in RedHat distro since 8.0 or so. You should check this out instead. Freshrpms is a complement distribution to RedHat that contains everything missing, such as mplayer, mpg321, and audacity.
cauz you're talking about average, but i'm talking about worst case. Try clicking on the 15th page, then the 23rd, then the 6th, etc. You get the idea. Search engines that give out search results "lazily" (evaluate only upon request) tends to be hit hard by this random access method.
When yahoo gave me 0.25, that was a rare worst case scenario. Same as when I said when Google gave me 0.70. Actually, I just hit another worst case of Google that gave me 0.88 seconds.
From TFA: Yahoo: 0.18 seconds. Google: 0.97 seconds. MSN: 0.92 seconds. Others not available.
I think the author got these numbers from the search page, where the time is shown along the number of search results. However, the meaning of this number is not well-defined. I don't think it's even guaranteed to be accurate.
(btw, I tried on Google for "raleigh" and I got 0.30 seconds. Yahoo gives me 0.12 seconds. Trying jumping around the search results page, Yahoo gives me about 0.25 seconds, and Google sometimes goes as high as 0.70 seconds. However, I must note that Yahoo doesn't let me jump over as many as +/- 5 pages, but Google lets me jump over +/- 10 pages.)
LADSPA has been around for a long time. It is not meant to duplicate VST, but it is a simple plugin interface just "good enough" to chain together effects like freeverb, compression, etc. It relies on the host (audio program that uses the plugin) to provide a user interface of the parameters to program the plugin. The plugins tend to come in a bundle, from dedicated plugin developers, such as Steve Harris and Richard Furse, who are experienced in DSP. There is also some kind of XML-based GUI description for LADSPA plugins around, but I'm not on the state of the art affair on that.
You see, you definitely have a lot of itch you want to scratch. Rather than whining about why they haven't scratched yours, why don't you make a program that will:
!) have good low latency options for the MIDI
2) have a vocoder, pitch matching, multipass filters, FFT based filter. (sorry, automatic noise reduction is for the whimps, so as automatic gain control)
3) where is the third one? did you point out the third example? I'm missing something...
There you go. And the program will be open source, right?
You may as well stay in Windows Wonderland if that suits you the best. The least I want to hear from people is an extortion of features "or else I'll just stay on Windows." I'm glad you have considered open source solutions, but it's the wrong attitude, man.
Just for information, to rip ISO files in unix (Linux, Mac OS X, etc), just do a:
dd if=/dev/cdrom of=~/cdimage.iso
Furthermore, on Mac OS X 10.3, "Disk Utility.app" will do the same. It also burns ISO images. I've also used cdrecord on Mac OS X with some success (specifying the device was a bit puzzling).
Actually, don't talk to Apple. They're interested in you? They must have other things on their mind. Furthermore, don't entice them of any features that you think is a cool unique idea in your app. Features can easily be duplicated. Look at what happened to song ratings and play counts in Audion. Now Apple put them in iTunes.
Really, if you keep quiet about it, maybe Apple will never notice you, and you get to survive.
... You obviously missed this important piece of fine Japanese manga/anime character, Doraemon. A museum of the gadgets in his pocket is a museum of the future!
Slashdot Mirror
Really, all you need to do (both as virus and anti-virus program) is install your own Int 0x13 (disk services BIOS) and Int 0x21 (DOS services) handler. AFAIK, no viruses actually attempted to patch DOS code, since this makes it bloated. Some virus, however, relocate themselves into unused DOS data segments. You still have access to prestine Int 0x13 entry points, though. It can be found in ROM-BIOS. If you're an anti-virus software writer you should know that, rather than trusting the actual interrupt. By the way, I used my own Int 0x13 handler to circumvent diskette protection of a chess game, without patching the game itself. Documentation of DOS came in the form of printed manual (or on-disk reference), and not as a website. It was otherwise fairly accessible.
I guess other troublesome cyrillic characters include U+0435 ("es", looks like small e), U+043e (looks like small o), U+0440 ("er", looks like small p, derived from greek letter "rho"), U+0441 ("es", looks like small c), U+0443 ("u", looks like small y), U+0445 ("ha", looks like small x), U+0455 ("dze", looks like small s).
Other spoofing candidates are from the latin extended region, for example U+0131 (dotless i) and some characters with accents that are rendered too small to see clearly on screen, for example, double grave or inverted breve.
The IPA extensions also provide some candidates: U+0251 (an alternative latin a without the top hook); U+0261 (alternative latin small g).
Okay, I get tired of enumerating the possibilities. Rather than trying to be a karma whore, I just want to point out for the last thing that vast majority of Chinese unicode has already suffered this problem. When unicode produced unified CJK characters, they admitted some variants of ideograph that only have minor difference (perhaps some are in the main unified section and some in the compatibility section). It's impossible to tell the difference in small point sizes. The reason why those characters have so many variants in the first place is because they're both structurally complex and frequently used. Also, there is a separate section for CJK radicals. Some radicals are valid ideographs, appearing twice in unicode.
On Mac OS X, there is a small, free software program called "Desktop Manager" that provides multiple desktops. You can configure the desktop "transition" to look as if it's a multiple faced cylindrical polygon (where each side face is rectangular) rotating. This transition is advertised as cube rotation rather than polygon rotation, but you can have more than 4 desktops/faces, and it certainly doesn't make a cube.
I'm not sure I like the idea that OSI is pitching itself as "the authority" of license evaluation. Although it is a lot easier to ask the question, "is license A approved by OSI" to mean "is the software licensed under A open source for me" but the question is flawed. One has to recognized that free software licenses are not created equal. The difference of them, and the choice involved, is what makes open source great.
Some towns have ordinances that ban public burning of anything at all. Burning in the public is a safety hazard. It also produces unpleasant fumes that are an environmental hazard. If smoking in the public is to be banned for the polution it causes, certainly flags shouldn't be an exception. It is especially important that flags made with nylon (which are more durable in extreme weather conditions) are not to be burned, since burning nylon produces dioxin.
I'm all for freedom of speech expressed in the form of flag shredding, though.
I guess this is too late a suggestion, but the left page would look very nice if the text aligns also to the right margin (except for the last line). The way text just falls off to the next line makes it look "grassy," or simply someone who hasn't shaved in a week.
I decided to run to the closest Barnes and Nobles before they close at 9pm, and bought a copy of NY Times.
On the left page, the names in the solid black print are legible, but the area covered by shaded graphics looks fudgy due to halftoning of greys. However, it seems that no name was masked in the two white "comma shaped" highlights. They printed the names around the white hallow.
I'm not sure how you could refute the official objective caml license, which clearly states that runtime system and standard libraries are licensed under LGPL (to allow linking with commercial programs), and the compiler and tools are licensed under QPL, which allow you to distribute unmodified code as is, or your modification "in a form that is separate from the Software."
The example given in QPL is using patches, but I don't see why you can't fork the source, since it would still be "separate" (just don't call it Objective CAML, but something else). QPL does not say your modification has to be in the form of patches.
I decided to repeat the author's experiment, i.e., put the powerbook to sleep, unplug the firewire drive that is previously mounted, then wake the computer up. When my powerbook wakes up, it still sees a ghost image of the firewire volume (I suppose due to cache) and I could navigate as much as what the cache has retained. Once I go beyond, the system tries to read from the drive and realizes it's gone, then unmounts the drive and pops up a dialog box telling me I should gracefully unmount the drive before I unplug it.
Brutely unplugging a drive while it's mounted really isn't a big deal nowadays, that we have journalled filesystem. Filesystems like reiser4 feature atomic operation, so it would be provably robust against brute removal. You only ought to worry if you're still using FAT (for example, digital cameras). Maybe the author should have acknowledge this "bug" being dependent on the filesystem, but then, this is beyond an end-user's (possibly also the author's) knowledge.
If you look at the BSD family tree here, you'd see that at one point in time, all Free/Net/Open BSD changed to use the codebase from 4.4BSD Lite, the unencumbered version.
"it looks like a great way to turn a lot of people off MSIE without just cause"
... everything bad I hear about MSIE come from security bulletins of well-known reputation, and later acknowledged by Microsoft for a security patch release. I don't think your assessment is fair to accuse people of believing in hearsay and cutting more slack for Firefox.
Yeah?! I'm still nodding along...
I never recall seeing a story with negative MSIE coverage that comes from an individual user. MSIE bug stories that I read were all reported and acknowledged by security companies who have a phone number to call if you don't like what they're reporting.
It makes me wonder why people bashing firefox or defending IE aren't willing to stand up to their words with their reputation (or they simply have no reputation so to speak). Are they all related to the same FUD department funded by a certain company or what?
If it makes you feel happier
do you leave firefox in a page with flash animations? nowadays many of the animated figures in a web page are flash and not animated gifs anymore. a badly made flash can take up tons of CPU even when you leave it there. also, are you viewing web sites with automatic page refreshing? it will eat up the CPU everytime the page refreshes.
if that bothers you, you can always use the task manager to set the process's priority to either "below normal" or "low".
however, games are memory intensive. so as a browser, which uses memory caching to be fast. when real memory is used up, "thrashing" occurs (to swap some memory pages to the disk). even adjusting task priority won't help here, since thrashing is inherently slow. whenever a web page that you leave in the background refreshes itself, the OS has to swap out a few pages of game memory and swap in memory pages for the browser. as the game continues, it needs the memory back, and the OS has to juggle around memory pages again.
if you see a periodic frame loss, then self-refreshing web pages are definitely the culprit.
If an accident happens, one can use the collected data to show that auto manufacturer is at fault, and this can be a powerful support when filing insurance claim. On the other hand, providing this data should be voluntary. The owner should be able to deny any other party's request of such data, if this cannot be used to his/her advantage. I'm not sure if allowing the device to be turned off is a good idea, as the driver may forget to turn it back on again.
Build failure can be caused by the following: (1) the code has problem with the gcc version you use. or (2) library dependencies are not installed. The first could happen if they bumped the version of gcc used. I think programs written in c++ are more prone to this problem. For the second possibility, if you upgraded your existing installation, it may be the case that your old -devel packages were obsoleted by new versions of the library, but the new version -devel is not picked up during installation. If you installed anew, then you definitely should install the -devel packages again. Definitely check your dependencies again.
Also, mp3 hasn't been included in RedHat distro since 8.0 or so. You should check this out instead. Freshrpms is a complement distribution to RedHat that contains everything missing, such as mplayer, mpg321, and audacity.
cauz you're talking about average, but i'm talking about worst case. Try clicking on the 15th page, then the 23rd, then the 6th, etc. You get the idea. Search engines that give out search results "lazily" (evaluate only upon request) tends to be hit hard by this random access method.
Wow, and I keep getting worse numbers from google. 1.40 seconds. Maybe Google is now getting /.-ed?
When yahoo gave me 0.25, that was a rare worst case scenario. Same as when I said when Google gave me 0.70. Actually, I just hit another worst case of Google that gave me 0.88 seconds.
From TFA: Yahoo: 0.18 seconds. Google: 0.97 seconds. MSN: 0.92 seconds. Others not available.
I think the author got these numbers from the search page, where the time is shown along the number of search results. However, the meaning of this number is not well-defined. I don't think it's even guaranteed to be accurate.
(btw, I tried on Google for "raleigh" and I got 0.30 seconds. Yahoo gives me 0.12 seconds. Trying jumping around the search results page, Yahoo gives me about 0.25 seconds, and Google sometimes goes as high as 0.70 seconds. However, I must note that Yahoo doesn't let me jump over as many as +/- 5 pages, but Google lets me jump over +/- 10 pages.)
Several people above mentioned Audacity as a replacement on Linux. In fact, it has been ported to both Windows and Mac OS X as well.
LADSPA has been around for a long time. It is not meant to duplicate VST, but it is a simple plugin interface just "good enough" to chain together effects like freeverb, compression, etc. It relies on the host (audio program that uses the plugin) to provide a user interface of the parameters to program the plugin. The plugins tend to come in a bundle, from dedicated plugin developers, such as Steve Harris and Richard Furse, who are experienced in DSP. There is also some kind of XML-based GUI description for LADSPA plugins around, but I'm not on the state of the art affair on that.
You see, you definitely have a lot of itch you want to scratch. Rather than whining about why they haven't scratched yours, why don't you make a program that will: !) have good low latency options for the MIDI 2) have a vocoder, pitch matching, multipass filters, FFT based filter. (sorry, automatic noise reduction is for the whimps, so as automatic gain control) 3) where is the third one? did you point out the third example? I'm missing something... There you go. And the program will be open source, right? You may as well stay in Windows Wonderland if that suits you the best. The least I want to hear from people is an extortion of features "or else I'll just stay on Windows." I'm glad you have considered open source solutions, but it's the wrong attitude, man.
You don't think mpg321 is lightweight enough for you? What about mplayer? It plays audio just fine.
Actually, don't talk to Apple. They're interested in you? They must have other things on their mind. Furthermore, don't entice them of any features that you think is a cool unique idea in your app. Features can easily be duplicated. Look at what happened to song ratings and play counts in Audion. Now Apple put them in iTunes.
Really, if you keep quiet about it, maybe Apple will never notice you, and you get to survive.
... You obviously missed this important piece of fine Japanese manga/anime character, Doraemon. A museum of the gadgets in his pocket is a museum of the future!
See some of his gadget at work here and here.