I'm watching it now - Very different from the first version. Plot order is different, charactization are different, even basic pronucisation is very different.
So - is it better? It's surely different from both the book and the movie....
Other than implanting a homing beacon in your skull, I can't think of a way to "prove" anything. Anything else is subject to tampering or transmission.
I heard a rumor that satelite phone occationally wake up and broadcast their position the the satellites, even when they are not in use. Any truth to that?
I got an IBM PCjr, 8088, when I was 5 or so, with a 128k addon card, and it had a Microsoft BASIC cartridge. I rememeber doing very simple things with that--like probably a good fraction of Slashdotters, my first exposure to computer language was BASIC.
But it STUCK. And I had a very heavy BASIC class in high school.
Actually I liked the BASIC cartridge. You should of tried to pull the cartridge and using the built-in PCjr BASIC. It was much worse. With 256 colors and multiple graphic buffers, (SCREEN 5) It was quite bleeding edge. (The AT and XT could only do 16 colors)
I don't knock BASIC - It serves a good purpose even today.
I have been useing zip, jaz, flash, smartmedia, and CD-RW for sometime now.
Zip is alot more reliable than floppy. I've bought about 40 disks, and only two have bit it over the years. I actually used to install/use MS Office 95 (using drvspace) so that might have hasten it's death, as it was constantly thrashed. I love my zip plus drive, and have not had any issues with it.
Of the 4 1GB jaz and 2 2GB jaz, only 1 1GB disk has died on me so far. Not too sure if this common, but that one disk never seemed right from the start. It spins at a very high speed, so maybe any misalignment could be blamed.
Smartmedia is pretty flimsy, and limited in capacity (64MB). Flash is a lot stronger better, and can go larger (I have a 96 MB flash which is very useful) My biggest fear is losing them - they are so small. On the flip side, it's the only media types that can be stored easily in a pants pocket.
I have not used my CDRW media recently, I currently only have one, and it was expensive at the time. If it's anything like CD-R, then I worry about scratches. I'm constantly re-burning the same images over and over due to wear from foreign CD-ROM drives.
I'm pretty hard on my media, so hopefully this useful info. I'm for Flash first, but it is expensive. Transferring info to them can be slow if your "flash drives" are cheap too.
I'm getting a brain overload from all the different encryption tools/stories/specs. It was not too long ago that I remember that all that was out there was PGP and DES. Now there are so many that I only remember the ones with funny names. (twofish? blowfish?)
At least with PGP I knew how to decode it, if someone sent me a encrypted email today, I would have no clue how to even identify it, nevermind decode it.
Is this depth of knowlege really required for a layman to take advantage of reasonable encryption security?
I believe that rampant technology has created a new 'slave class' of workers. The janitors in my building often get better consideration than us cube rats do. It is only the truly elite geek that has any pull these days. I'm trying to move up into management, so I can get at least some control over my daily schedule and workload.
The more our numbers grow, the more we become dispensible. Perhaps it's time we unionize.
...Maybe where you are from, but here in Japan, we spell it SAKE (when spelled in Roman Characters, that is)....and all you GAIJIN should start calling it by its real name; pronounced like this: SOCK-EH....as in a 'sock' and 'eh' put together...NOT SOCK-EE.....
Err... try:
sa-ke(): sa (as in SAw) ke (as in 'oKAY')
The 'ki' version came from a different system of romajinzation that is forunately becoming more rare to find.
-f}fCfPf
Maybe there is something you can look for in the black bar - isn't there normally SMTP time codes and other ID info (besides Close Captioning) in there?
I have a US-locale Palm V with the J-OS 1.9 extentions for Palm OS2.0 on it. Much nicer that these native plastic models.
The hack itself is only 18K, but the japanese fonts/dictionaries take about 200K. Do yourself a favor and make sure you get a 4MB model or higher if want to do serious multiligual stuff on it, as you will need to 'replace' most of the built-in english-only apps.
From a developer POV, I believe Windows still has a strong win in many areas. If one negates the windows registry (I still prefer using.INIs) and everything a year or less old (Kerberos support, AD, Message Queues, etc.) Then you still have one pervasive platform:
DirectX - Love it or hate it, it does the job. While some areas (like DirectInput and DirectMusic) are still queezy at best, you can't beat DirectDraw's flexibility.
UI - The 2D GUI is pretty hot. Font smoothing and color management. Solid control designs and IMEs. Try and write a multilingual application and see how far you get. Ever try and copy and paste multibyte characters in X? Oops.
COM - I've tried working with CORBA, and so far it can't cut it. COM is an incredible piece of engineering, and it shows. If I had one wish for Unix, it would be a COM implementation that could rival Windows. COM+ looks good too. Too bad it uses the registry - most of the time. We shall see what happens with SOAP.
MS Office - Sorry, but it's got to be said. Nothing beats Office - yet. Why does office work so well? COM. It will take many a manhours to raise Koffice/Openparts to that level. Well, if we had COM for Unix, and a lightweight VM, then maybe we could 'borrow' some of the more interesting pieces...
Yeah, the rest of Windows is crap, but you get what you pay for - DirectX, the UI, COM and Office. Everthing else is just one of those four things. Oh yeah, and IE thrown in just for fun.
The PCI bus is a non-switched fabric bus. All PCI devices have to share the bandwith of the bus and a graphics card can consume almost the entire bus bandwidth. By moving graphics data to the [AGP?] bus, you can significantly improve total system performance. In that sense, it roughly is the equivalent of segmenting a network.
If this is the case, my why does my Nivida Geforce 2 GTS (AGP) and my SB Live Platinum [PCI] have contentions with each other? Separate Buses, IRQs, DMAs, and Memory Addresses, but sometimes under Direct X they momentarily "hang" each other.
Is my PIII 900mhz processor/142mhz bus not task switching fast enought between them?
(Individually, everything works fine...just thought I'd ask, since this problem has been bugging me for some time...)
...and C# relies heavily on Microsoft's Component Object Model...
Which is probably how most of this functionality (encapulation, events and call-backs) will be implemented. I'm getting the sense this is going to turn out to be something of a quazi-language, which was in the end what Microsoft's Java implementation became (Just try and do something meaningful in it without invoking a COM object.)
In the end, C# really does not seem to offer anything meaningful that VB does (or will) not, and for the same reasons will not be any less portable.
Actually, that is an excellent <a href="http://phrack.infonexus.com/search.phtml?vi<nobr>e<wbr></wbr></nobr> w&article=p49-14">link</a>. I understood the technique in principal, but never seen an actually example of how it works. Pretty hairy stuff - the people who play with this must like to crash their own machines often.
I recently bought a Maxor 60 GB to replace my 17.2 GB drive. I was strangely confused when I had to jumper on the cylinder translation feature to make it work. I figured since my BIOS supported the 17.5 GB drive just fine, 60 GB would be okay too.
In the past I've run across the 80MB limit, the ~2GB limit, and the ~16 GB limit, but you would think after all that they would have figured out how to overcome the BIOS translation issue permamently now. Is'nt that what LBA addressing mode is all about?
This book has been around for awhile now, and I've long since gone through it. Actually I'm expecting my copy of OOP Perl to arrive tomarrow and am looking forward to reading something new.
My biggest gripe with the book is it gears up too slowly and ends too soon. If you already know what a database is, and how SQL works, skip the first half of the book. If you are looking to learn about the nuts and bolts of how use/setup a specific DBD, you will need to look somewhere else (the man pages are a better source here.)
Now that Windows 2000 can use a basterized version of LDAP vs. the undecriptable SAM, does it become any more feasible to have Access Control Lists (ACL) work from Unix? What are your feelings on the "extenstions" that Microsoft made to the LDAP spec - are they insurmountable to decode?
Slashdot Mirror
More of Irulan - She really got cut out of the movie. I liked the interplay between her and Paul, even if it is completely fabricated.
:)
Then again, maybe I've been watching too much A&E
I'm watching it now - Very different from the first version. Plot order is different, charactization are different, even basic pronucisation is very different.
So - is it better? It's surely different from both the book and the movie....
Other than implanting a homing beacon in your skull, I can't think of a way to "prove" anything. Anything else is subject to tampering or transmission.
I heard a rumor that satelite phone occationally wake up and broadcast their position the the satellites, even when they are not in use. Any truth to that?
I hate to say it, but Myst III looks cooler than realMYST to me, and I'm a graphics nut.
Will realtime engines ever reach the quality of raytracing at the consumer level?
My thinking is that their next game should be an interactive DVD movie.
Actually I liked the BASIC cartridge. You should of tried to pull the cartridge and using the built-in PCjr BASIC. It was much worse. With 256 colors and multiple graphic buffers, (SCREEN 5) It was quite bleeding edge. (The AT and XT could only do 16 colors)
I don't knock BASIC - It serves a good purpose even today.
Zip is alot more reliable than floppy. I've bought about 40 disks, and only two have bit it over the years. I actually used to install/use MS Office 95 (using drvspace) so that might have hasten it's death, as it was constantly thrashed. I love my zip plus drive, and have not had any issues with it.
Of the 4 1GB jaz and 2 2GB jaz, only 1 1GB disk has died on me so far. Not too sure if this common, but that one disk never seemed right from the start. It spins at a very high speed, so maybe any misalignment could be blamed.
Smartmedia is pretty flimsy, and limited in capacity (64MB). Flash is a lot stronger better, and can go larger (I have a 96 MB flash which is very useful) My biggest fear is losing them - they are so small. On the flip side, it's the only media types that can be stored easily in a pants pocket.
I have not used my CDRW media recently, I currently only have one, and it was expensive at the time. If it's anything like CD-R, then I worry about scratches. I'm constantly re-burning the same images over and over due to wear from foreign CD-ROM drives.
I'm pretty hard on my media, so hopefully this useful info. I'm for Flash first, but it is expensive. Transferring info to them can be slow if your "flash drives" are cheap too.
I'm getting a brain overload from all the different encryption tools/stories/specs. It was not too long ago that I remember that all that was out there was PGP and DES. Now there are so many that I only remember the ones with funny names. (twofish? blowfish?)
At least with PGP I knew how to decode it, if someone sent me a encrypted email today, I would have no clue how to even identify it, nevermind decode it.
Is this depth of knowlege really required for a layman to take advantage of reasonable encryption security?
Software upgradeable, and _a_lot_ easier to setup than a dedicated linux box with ipchains.
I believe that rampant technology has created a new 'slave class' of workers. The janitors in my building often get better consideration than us cube rats do. It is only the truly elite geek that has any pull these days. I'm trying to move up into management, so I can get at least some control over my daily schedule and workload.
The more our numbers grow, the more we become dispensible. Perhaps it's time we unionize.
Err... try: sa-ke(): sa (as in SAw) ke (as in 'oKAY') The 'ki' version came from a different system of romajinzation that is forunately becoming more rare to find. -f}fCfPf
Maybe there is something you can look for in the black bar - isn't there normally SMTP time codes and other ID info (besides Close Captioning) in there?
I have a US-locale Palm V with the J-OS 1.9 extentions for Palm OS2.0 on it. Much nicer that these native plastic models.
The hack itself is only 18K, but the japanese fonts/dictionaries take about 200K. Do yourself a favor and make sure you get a 4MB model or higher if want to do serious multiligual stuff on it, as you will need to 'replace' most of the built-in english-only apps.
- Maikeru
Japanese is a SOV language (Subject-Object-Verb) language. That it why word for word translations are pretty useless.
Maikeru
DirectX - Love it or hate it, it does the job. While some areas (like DirectInput and DirectMusic) are still queezy at best, you can't beat DirectDraw's flexibility.
UI - The 2D GUI is pretty hot. Font smoothing and color management. Solid control designs and IMEs. Try and write a multilingual application and see how far you get. Ever try and copy and paste multibyte characters in X? Oops.
COM - I've tried working with CORBA, and so far it can't cut it. COM is an incredible piece of engineering, and it shows. If I had one wish for Unix, it would be a COM implementation that could rival Windows. COM+ looks good too. Too bad it uses the registry - most of the time. We shall see what happens with SOAP.
MS Office - Sorry, but it's got to be said. Nothing beats Office - yet. Why does office work so well? COM. It will take many a manhours to raise Koffice/Openparts to that level. Well, if we had COM for Unix, and a lightweight VM, then maybe we could 'borrow' some of the more interesting pieces...
Yeah, the rest of Windows is crap, but you get what you pay for - DirectX, the UI, COM and Office. Everthing else is just one of those four things. Oh yeah, and IE thrown in just for fun.
If this is the case, my why does my Nivida Geforce 2 GTS (AGP) and my SB Live Platinum [PCI] have contentions with each other? Separate Buses, IRQs, DMAs, and Memory Addresses, but sometimes under Direct X they momentarily "hang" each other. Is my PIII 900mhz processor/142mhz bus not task switching fast enought between them?
(Individually, everything works fine...just thought I'd ask, since this problem has been bugging me for some time...)
SuSE rules - this American ain't going back to dorkyhat.
OT: I'm on 6.3 - any reason to go 6.4?
...and C# relies heavily on Microsoft's Component Object Model...
Which is probably how most of this functionality (encapulation, events and call-backs) will be implemented. I'm getting the sense this is going to turn out to be something of a quazi-language, which was in the end what Microsoft's Java implementation became (Just try and do something meaningful in it without invoking a COM object.)
In the end, C# really does not seem to offer anything meaningful that VB does (or will) not, and for the same reasons will not be any less portable.
The latest automated build of this breaks Mozilla on my machine.
(The plain old nightly build is not much better, but at least it runs...)
Actually, that is an excellent <a href="http://phrack.infonexus.com/search.phtml?vi<nobr>e<wbr></wbr></nobr> w&article=p49-14">link</a>. I understood the technique in principal, but never seen an actually example of how it works. Pretty hairy stuff - the people who play with this must like to crash their own machines often.
I recently bought a Maxor 60 GB to replace my 17.2 GB drive. I was strangely confused when I had to jumper on the cylinder translation feature to make it work. I figured since my BIOS supported the 17.5 GB drive just fine, 60 GB would be okay too.
In the past I've run across the 80MB limit, the ~2GB limit, and the ~16 GB limit, but you would think after all that they would have figured out how to overcome the BIOS translation issue permamently now. Is'nt that what LBA addressing mode is all about?
This book has been around for awhile now, and I've long since gone through it. Actually I'm expecting my copy of OOP Perl to arrive tomarrow and am looking forward to reading something new.
My biggest gripe with the book is it gears up too slowly and ends too soon. If you already know what a database is, and how SQL works, skip the first half of the book. If you are looking to learn about the nuts and bolts of how use/setup a specific DBD, you will need to look somewhere else (the man pages are a better source here.)
...you never want to go back.
Quake III may look better on linux, but until I get EAX linux support for my Soundblaster live, I really don't see myself using it for gaming.
I guess they could not wait for KDE2.
Any ETA on a stable release yet?
...they are too dated... topics like Nanotech are most likely unavailible - unless it's a really good college library.
./ was a very smart idea.
I think asking
Now that Windows 2000 can use a basterized version of LDAP vs. the undecriptable SAM, does it become any more feasible to have Access Control Lists (ACL) work from Unix? What are your feelings on the "extenstions" that Microsoft made to the LDAP spec - are they insurmountable to decode?