Okay, that flame just didn't work. Your post really DID say "Hours of Fur" on my screen.
Looks like Firebird ate a piece of your 'n' for a minute there. Usually it just mysteriously italizes the odd line here and there. I wish they would fix that (6.1 and 7.0).
> hold the "windows logo key" and the Pause/Break key together!
Hey, Neat!
Know what's neater? I've been typing on this [my wife's] keyboard at night for two years now. I never noticed it had a Windows Key 'till you made me want it.
I guess that's what I get for typing on a Sun Type 5c and an IBM 5-tonne-slab all day.
Not to put too fine a point on it, but it's entirely possible that every last one of these dweebs is, in fact married, and not even *somewhat* available.
And it's not like playing a chord on the piano, crossing your fingers like that would get you slapped in my class. If you wanted to imitate playing a chord (on the world's most awful piano), use thumb/alt, ring/ctl, pinky/del.
This instead, I think you'll find it easier (assuming you can play an octave on your right hand) -- thumb/alt, index/ctl, middle/del. Then you can tap del easily as many times as you need to.
It may kill XFree86, but equating X with XFree86 is tatamount to equating mail with sendmail, news with inn, qpopper with POP3, and Microsoft Windows with "Operating System".
I sure hope you're not an OOP programmer. OOP programmers who don't know the difference between an instance and class frighten me.
FWIW, the Sun type 5c keyboard is like that, too. IIRC, the type 4 wasn't. What's the type 6? I don't think I've seen one of those.. although we do have some funky-looking keyboards with wrist rests around here somewhere... junked in a box because they came with the control key in the wrong place..
What I can't figure about my "Any" key, though, is why it's dirty. WTF? I can understand why the other keys are dirty, I've had this keyboard at my desk for five or six years. But I don't think I've *ever* hit the "Any" key in all that time.
Huh. Guess I'll have to clean the keycap so I can label it.. Now, where are my rub-on letters...
Provision bandwidth for work and home from the same ISP. Don't let your X packets hit the internet. 1.5 mbits @ 5ms is plenty fast for darn near _any_ X app, even without LBX. And xemacs19 positively *flies* -- it's hard to tell I'm not at my desk.:)
> they are actually taking NX to court? > I thought that truly intelligent AI was years off.
Corporations can sue. Darl McBride can sue. Your proposition that entities must be "truly intelligent" (or, in fact, intelligent at all) is wildly off-base. Therefore, your conclusion (that truly intelligent AI is no longer years off) is invalid.
Are you sure? I think some instructions (NOP, NMI?) are one clock. But it's been ten years since I've looked.
Of course, your point is still valid, IIRC most of the indirect load/store instructions were three clocks, more if you cross page boundaries, one less if you're dealing with zero page.
From a cursory glance at the board, it looks like it plugs into the user port. That means it has access to the data lines from the 6526 VIA, which yields a single memory-mapped address for I/O.
That means the fastest you could write a page would be something like this:
STA 56579, 255 LDX, #0 LOOP:
LDA $BUFFER,X
STA 56577
DEX
BEQ LOOP...I think that adds up to 3 + 3 + 1 + 2 cycles per byte, and an overhead of at least 6 more cycles per page crossed. You could shave off two cycles out of the loop by using addresses in the zero page, but since some of those addresses are reserved, you wouldn't be able to use all 255 bytes.
In order to do DMA, the controller would need to plug into the expansion port, which gives you direct access to the address and data lines of the system bus. But as another poster pointed out, you have to blank the video during transfers to achieve maximal throughput due to the VIC-IIs habit of stealing cycles for itself.
Actually, I'd bet you a doughnut that it was the 9VAC lines from the power supply (or fuse in the box) that "burned" out. The 1520 datasette is nearly indestructible; C= power supplies are not, and the VIC (unlike the '64) only used those 9VAC lines for one thing...
What I always have a hard time with is my five year calling my female Jack Russell a "little bitch". She's completely accurate, but doesn't mean it that way.
> Because I'm just a simple caveman home networker, > and your logs and timestamps frighten and confuse me
Don't you mean simple unfrozen caveman home networker?
I agree with your point, BTW. There really isn't anything NetGear can do at this point that they haven't done (operationally, not financially), except start advertising in magazines/websites and sending out letters to people who actually sent in those warranty registration cards.
I'm lucky, it looks as if all my netgear stuff is too old to be affected (RT311 and ISDN bretheren.. 341s?). I don't do ISDN any more, and my RT311s have all been replaced by Linux kernel 2.4 and iptables.
I'm surprised the American Federation of Musicians, commonly known as the AFM, didn't come after him.. but they tend to be a more sensible organization. I'm surprised the AFMA is claiming the letters AFM as their trademark, when clearly it belongs to... the AFM.
I don't know for sure if this is the same in the US (I think is), but in Canada it is perfectly legal to listen in on a private conversation whose radio waves enter your property (cell phone, cordless phone, baby monitor, whatever) -- as long as you neither use that information for personal gain nor divulge it to a third party.
> I haven't built a system for close to 8 years and my knowledge > might be a bit dated
A little over 6 for me, I know how you feel.
As for his in-rush problem (I'm pretty sure that's exactly what it is, BTW), depending on his SCSI drives and controllers, he may be able to get the controller to spin them up one at a time after the controller's BIOS has initialized (and hence all the fans, etc are running).
Back in the day, the Adaptec-1542 supported this if you hit Ctrl-A during boot-up and walked the menus appropriately. And most SCSI disks had a jumper enabling or disabling auto-spin up.
Alternatively, an extra STDP switch hooked to the +5 and +12 lines of one of those disks might do the trick. Power on the machine, count to three, throw the switch to power on the last disk... Probably safer than what he's doing now (but still a lousy solution, especially if his OS is on that second disk;)
Slashdot Mirror
I'll bet your turbo key alternates between sending Control-Alt-NumberPadPlus and Control-Alt-NumberPadMinus.
That's the old AMI BIOS (or was it Phoenix?) keyboard shortcut for hitting your turbo button.
That must be a really old keyboard. Are the letters still on it?
Okay, that flame just didn't work. Your post really DID say "Hours of Fur" on my screen.
Looks like Firebird ate a piece of your 'n' for a minute there. Usually it just mysteriously italizes the odd line here and there. I wish they would fix that (6.1 and 7.0).
> Slashdot just screwed it!
Funny, I thought if that key was getting you "Hours of Fur" that you would have screwed it.
> hold the "windows logo key" and the Pause/Break key together!
Hey, Neat!
Know what's neater? I've been typing on this [my wife's] keyboard at night for two years now. I never noticed it had a Windows Key 'till you made me want it.
I guess that's what I get for typing on a Sun Type 5c and an IBM 5-tonne-slab all day.
Not to put too fine a point on it, but it's entirely possible that every last one of these dweebs is, in fact married, and not even *somewhat* available.
And it's not like playing a chord on the piano, crossing your fingers like that would get you slapped in my class. If you wanted to imitate playing a chord (on the world's most awful piano), use thumb/alt, ring/ctl, pinky/del.
This instead, I think you'll find it easier (assuming you can play an octave on your right hand) -- thumb/alt, index/ctl, middle/del. Then you can tap del easily as many times as you need to.
It may kill XFree86, but equating X with XFree86 is tatamount to equating mail with sendmail, news with inn, qpopper with POP3, and Microsoft Windows with "Operating System".
I sure hope you're not an OOP programmer. OOP programmers who don't know the difference between an instance and class frighten me.
FWIW, the Sun type 5c keyboard is like that, too. IIRC, the type 4 wasn't. What's the type 6? I don't think I've seen one of those.. although we do have some funky-looking keyboards with wrist rests around here somewhere... junked in a box because they came with the control key in the wrong place..
What I can't figure about my "Any" key, though, is why it's dirty. WTF? I can understand why the other keys are dirty, I've had this keyboard at my desk for five or six years. But I don't think I've *ever* hit the "Any" key in all that time.
Huh. Guess I'll have to clean the keycap so I can label it.. Now, where are my rub-on letters...
Provision bandwidth for work and home from the same ISP. Don't let your X packets hit the internet. 1.5 mbits @ 5ms is plenty fast for darn near _any_ X app, even without LBX. And xemacs19 positively *flies* -- it's hard to tell I'm not at my desk. :)
> they are actually taking NX to court?
> I thought that truly intelligent AI was years off.
Corporations can sue. Darl McBride can sue. Your proposition that entities must be "truly intelligent" (or, in fact, intelligent at all) is wildly off-base. Therefore, your conclusion (that truly intelligent AI is no longer years off) is invalid.
Are you sure? I think some instructions (NOP, NMI?) are one clock. But it's been ten years since I've looked.
Of course, your point is still valid, IIRC most of the indirect load/store instructions were three clocks, more if you cross page boundaries, one less if you're dealing with zero page.
From a cursory glance at the board, it looks like it plugs into the user port. That means it has access to the data lines from the 6526 VIA, which yields a single memory-mapped address for I/O.
...I think that adds up to 3 + 3 + 1 + 2 cycles per byte, and an overhead of at least 6 more cycles per page crossed. You could shave off two cycles out of the loop by using addresses in the zero page, but since some of those addresses are reserved, you wouldn't be able to use all 255 bytes.
That means the fastest you could write a page would be something like this:
STA 56579, 255
LDX, #0
LOOP:
LDA $BUFFER,X
STA 56577
DEX
BEQ LOOP
In order to do DMA, the controller would need to plug into the expansion port, which gives you direct access to the address and data lines of the system bus. But as another poster pointed out, you have to blank the video during transfers to achieve maximal throughput due to the VIC-IIs habit of stealing cycles for itself.
Man, I feel old. The TS/1000 was also my first machine, and I just turned 30 a couple of days ago. Ouch.
I had *no idea* that The Canopy Group now owned a record label!
> Maybe it's me, but emacs comes to mind with Stallman.
Maybe it's me, but I'd have to wonder if the man was Lucid when he wrote it.
I have to admit, though, a project of that size in LISP. That's frightening.
Actually, I'd bet you a doughnut that it was the 9VAC lines from the power supply (or fuse in the box) that "burned" out. The 1520 datasette is nearly indestructible; C= power supplies are not, and the VIC (unlike the '64) only used those 9VAC lines for one thing...
> Wow...every country has it's easily believed thieves. I wonder what
> Canada's are Aboriginals...Arabs... Somalis...Vietnamese.
Americans. And, of course, Politicians.
What I always have a hard time with is my five year calling my female Jack Russell a "little bitch". She's completely accurate, but doesn't mean it that way.
*sigh*
> Because I'm just a simple caveman home networker,
> and your logs and timestamps frighten and confuse me
Don't you mean simple unfrozen caveman home networker?
I agree with your point, BTW. There really isn't anything NetGear can do at this point that they haven't done (operationally, not financially), except start advertising in magazines/websites and sending out letters to people who actually sent in those warranty registration cards.
I'm lucky, it looks as if all my netgear stuff is too old to be affected (RT311 and ISDN bretheren.. 341s?). I don't do ISDN any more, and my RT311s have all been replaced by Linux kernel 2.4 and iptables.
> const int SIXTY = 60.2;
The programmer would catch on pretty quick when it didn't compile. Now, if he declared it as a float, on the other hand...
Just get another phone which can do SMS over the serial port (e.g. Nokia 7190).
Authentication problem is solved, check the originating phone number.. well, as long as you trust the integrity of your provider's SMS infrastructure.
> No, it only applies to "use of the Emacs editor".
Don't you mean the GNU Emacs editor?
I'm surprised the American Federation of Musicians, commonly known as the AFM, didn't come after him.. but they tend to be a more sensible organization. I'm surprised the AFMA is claiming the letters AFM as their trademark, when clearly it belongs to... the AFM.
-- AFM local ?? Shit, I can't remember.
I don't know for sure if this is the same in the US (I think is), but in Canada it is perfectly legal to listen in on a private conversation whose radio waves enter your property (cell phone, cordless phone, baby monitor, whatever) -- as long as you neither use that information for personal gain nor divulge it to a third party.
Strange law, yes, pretty reasonable? I think so.
> I haven't built a system for close to 8 years and my knowledge
;)
> might be a bit dated
A little over 6 for me, I know how you feel.
As for his in-rush problem (I'm pretty sure that's exactly what it is, BTW), depending on his SCSI drives and controllers, he may be able to get the controller to spin them up one at a time after the controller's BIOS has initialized (and hence all the fans, etc are running).
Back in the day, the Adaptec-1542 supported this if you hit Ctrl-A during boot-up and walked the menus appropriately. And most SCSI disks had a jumper enabling or disabling auto-spin up.
Alternatively, an extra STDP switch hooked to the +5 and +12 lines of one of those disks might do the trick. Power on the machine, count to three, throw the switch to power on the last disk... Probably safer than what he's doing now (but still a lousy solution, especially if his OS is on that second disk