1) The Castle RiscPC predates the LART project by a few years (the RiscPC came out in '93 FWICR, the earliest bit of news on the LART is '99). This/does not/ run RISC OS 5 (it runs RISC OS 4).
2) The Iyonix uses the XScale processor, whilst the LART uses the StrongARM - the XScale's predecessor.
V6 engines normally outperform a V8 with the same size - the V6 has less rotary momentum to worry about, and so has a faster rev increase. V8s have a higher rotary momentum (more pistons), and so will be slower to rev.
Try removing the space in the second "privacy", and it works. For some reason (probably IE's fault), the URL always ends up with a space in it (it was doing it when I was previewing this).
Just because an image file consists of data, if a poorly designed decoder has been written, then if the data is corrupted, you could end up spewing data over stack or even main memory.
If you had some control over what data is written, then you could get the decoder to write out what amounts to a virus, and then get the decoder to execute it (by trashing the stack).
I won't use JPEG as an example, but some lossless compression, such as GIF. Instead of having the image compressed, you could have your program compressed. Decompressing the data would effectively copy the code into some memory location. The difficult bit would be getting the decoder to actually execute it.
Don't forget that such a virus doesn't actually need to spread itself in images; it could be a simple bootstrap loader in the images that downloads a larger virus with its own payloads.
The main differences between PAL/SECAM and NTSC are due to the country's mains electrical supply frequency. By having a vertical sync that is synchronised with the mains supply reduces EMF induced interference on the display.
Quite why there's different standards for the same frequency, I don't know (or why there's PAL-I and PAL-II for that matter).
I used to work at Burger King, and we had our cash registers upgraded (this was about 9 years ago now). Inside the registers was basically a 386 processor, networked to the office (and then on to the head office) so the managers could keep track of how much we were selling.
It was quite amusing wathcing them reboot every so often...
We have an ex-employee from SGI working for us, and he's told me that SGI have an event called "Lip sync", where departments have to come up with the most outrageous and over the top songs for their department. Notable entries were "CAD to the bone" ('bad to the bone') and "Drugs do work"...
As I live in Britain, I'm not worried at all by all the cameras that we have here. It doesn't bother me that I can be seen going from A to B to C - the only thing I'd like to know is why someone would want to know where I've been;-)
We've had a number of high profile cases where surveillance cameras have been instrumental in solving crimes, and I really don't have a problem with that - in fact, I'm pretty pleased with the results.
It's by the WAP Forum, but you'll need to register to get the specifications.
Basically, it's a serialisation of XML using a tokenisation system - tags, attributes and even values become tokens, and has extensions for unknown items.
It also has extensions for string tables, where commonly used words or phrases can be given, with a lookup into the string table index used.
Although it doesn't actually compress XML per sé, it does do a fairly good job (unfortunately, I don't have any figures to hand).
I rather like the idea of having an on-board IEEE-1394 controller; now all we need are some mLan compatible synthesisers, so everything can be controlled from one wire!
Cool!
I suppose if you take a multidimensional array to mean a contiguous array of data (as the document later asserts), but the code given really does look like the above code.
You know, I'm not entirely sure that his assertion that subdimensions of a multidimension array must have the same dimension (topic 5).
After all, in C, I'd use:
I really enjoy it if the spammers have a telephone number I can call, or better still a fax number.
One spammer I called I tied up his line demanding why I was being spammed for so long, he put the phone down on me.
Another I faxed with an invoice for $300. I live in the UK, and this guy was in the States. About a month later, I received by **post** a print-out of my invoice, with hand-written notes (in orange highlighter pen) effectively telling me to get stuffed, and wishing my mother would die. A few people in the office suggested I reported them for threatening behaviour, but I never got around to it - after all, there's only so many hours in the day...
There was a slashdot posting here. I'd made the point that ARM were very protective of their IP, and it doesn't surprise me at all that it was taken down. I'd seen that it wasn't there for a while now, but hadn't heard that this was the case until today.
I believe that their patents include the use of banked registers in a particular way. I have been wondering if it's possible to create an ARM code compliant processor, but don't do all the patentable features of the ARM itself...
The StrongARM processor is an ARM RISC processor, originally developed by Digital, and now manufactured by Intel.
According to some old documentation I have here, @200MHz, it delivers 230MIPS, consuming <900mW. However, there are other variants in the StrongARM family, and it's unclear as to which it is.
It's been quoted that an ARM processor @14MHz is roughly equivalent to an x86 @40MHz, so you're looking at the equivalent of around 600MHz in x86 power.
Since it's a RISC processor, it isn't too expensive - unfortunately I haven't bought any for a while (last ones I bought were about 2-3 years ago), so I can't quote a figure.
I can't believe you're saying that you don't need power;-)
It's been superceded by Intel's XScale processor, which FWICR is 1GHz and greater.
Slashdot Mirror
Almost impossible to kill.
:)
Like hell. I tried my first tomatoes last year. Two things you must do:
1) When they grow too large for the seedling pots, put them in something larger. Don't leave it for 3 months and then do it.
2) When it's nice and sunny, make sure they're watered.
3) If you don't put a solid stake in the ground, they tend to wander around and then fall over.
Guess which 3 things I didn't do
I've still got their dried up stalks in the plant pots - haven't come around to remove them yet. I don't know if I'll try again this year...
Other way around, and also incorrect.
/does not/ run RISC OS 5 (it runs RISC OS 4).
1) The Castle RiscPC predates the LART project by a few years (the RiscPC came out in '93 FWICR, the earliest bit of news on the LART is '99). This
2) The Iyonix uses the XScale processor, whilst the LART uses the StrongARM - the XScale's predecessor.
So to say it's a ripoff of the LART is incorrect.
Under RISC OS 3.5, we get something similar:
oflaoflaoflaoflaoflaoflaofla
(except with accented characters).
I call it the "ofla" crash...
...must remember to leave the door open on the microwave and see how my food's doing ;-)
V6 engines normally outperform a V8 with the same size - the V6 has less rotary momentum to worry about, and so has a faster rev increase. V8s have a higher rotary momentum (more pistons), and so will be slower to rev.
Just a little side-piece...
Romans?
;-)
What have the Romans ever done for us?
Try removing the space in the second "privacy", and it works. For some reason (probably IE's fault), the URL always ends up with a space in it (it was doing it when I was previewing this).
But yours would'nt clear the screen...
I'd already thought of this:
sub plotRandomStars()
{
srand(123456);
foreach (0..500) {
$image.plot(rand() & 127, rand() & 127, rand() & 255);
# Assuming grey-scale image
}
}
It's kinda Perl, but won't work...
foreach $frame (0..100) {
$image = newImage(128, 128);
$image.plotRandomStars();
$image.plot(10 + $frame, 10 + $frame);
$image.write();
}
Just because an image file consists of data, if a poorly designed decoder has been written, then if the data is corrupted, you could end up spewing data over stack or even main memory.
If you had some control over what data is written, then you could get the decoder to write out what amounts to a virus, and then get the decoder to execute it (by trashing the stack).
I won't use JPEG as an example, but some lossless compression, such as GIF. Instead of having the image compressed, you could have your program compressed. Decompressing the data would effectively copy the code into some memory location. The difficult bit would be getting the decoder to actually execute it.
Don't forget that such a virus doesn't actually need to spread itself in images; it could be a simple bootstrap loader in the images that downloads a larger virus with its own payloads.
The main differences between PAL/SECAM and NTSC are due to the country's mains electrical supply frequency. By having a vertical sync that is synchronised with the mains supply reduces EMF induced interference on the display.
Quite why there's different standards for the same frequency, I don't know (or why there's PAL-I and PAL-II for that matter).
Practically every story I've seen on /. has been "RMS doesn't like X", or "RMS condems Y", or "RMS speaks against Z".
Is there anything that he likes?
I used to work at Burger King, and we had our cash registers upgraded (this was about 9 years ago now). Inside the registers was basically a 386 processor, networked to the office (and then on to the head office) so the managers could keep track of how much we were selling.
It was quite amusing wathcing them reboot every so often...
Hook it up to your Bluetooth GPS, and have your own "where am I today?" web server. Or a bluetooth web-cam for "what am I doing today?"
We have an ex-employee from SGI working for us, and he's told me that SGI have an event called "Lip sync", where departments have to come up with the most outrageous and over the top songs for their department. Notable entries were "CAD to the bone" ('bad to the bone') and "Drugs do work"...
Your plastic pal who's fun to be with!
Wouldn't Amazon complain about this?
We've had a number of high profile cases where surveillance cameras have been instrumental in solving crimes, and I really don't have a problem with that - in fact, I'm pretty pleased with the results.
Basically, it's a serialisation of XML using a tokenisation system - tags, attributes and even values become tokens, and has extensions for unknown items.
It also has extensions for string tables, where commonly used words or phrases can be given, with a lookup into the string table index used.
Although it doesn't actually compress XML per sé, it does do a fairly good job (unfortunately, I don't have any figures to hand).
I rather like the idea of having an on-board IEEE-1394 controller; now all we need are some mLan compatible synthesisers, so everything can be controlled from one wire!
Cool!
I suppose if you take a multidimensional array to mean a contiguous array of data (as the document later asserts), but the code given really does look like the above code.
You know, I'm not entirely sure that his assertion that subdimensions of a multidimension array must have the same dimension (topic 5).
After all, in C, I'd use:
int* array[2];
array[0] = (int*)calloc(sizeof(int), 3);
array[1] = (int*)calloc(sizeof(int), 9);
True, this doesn't use heap-based stack, but to me, the functionality is the same...
I really enjoy it if the spammers have a telephone number I can call, or better still a fax number.
One spammer I called I tied up his line demanding why I was being spammed for so long, he put the phone down on me.
Another I faxed with an invoice for $300. I live in the UK, and this guy was in the States. About a month later, I received by **post** a print-out of my invoice, with hand-written notes (in orange highlighter pen) effectively telling me to get stuffed, and wishing my mother would die. A few people in the office suggested I reported them for threatening behaviour, but I never got around to it - after all, there's only so many hours in the day...
I believe that their patents include the use of banked registers in a particular way. I have been wondering if it's possible to create an ARM code compliant processor, but don't do all the patentable features of the ARM itself...
According to some old documentation I have here, @200MHz, it delivers 230MIPS, consuming <900mW. However, there are other variants in the StrongARM family, and it's unclear as to which it is.
It's been quoted that an ARM processor @14MHz is roughly equivalent to an x86 @40MHz, so you're looking at the equivalent of around 600MHz in x86 power.
Since it's a RISC processor, it isn't too expensive - unfortunately I haven't bought any for a while (last ones I bought were about 2-3 years ago), so I can't quote a figure.
I can't believe you're saying that you don't need power ;-)
It's been superceded by Intel's XScale processor, which FWICR is 1GHz and greater.