The laptop vs. notebook thing doesn't really mean much of anything... everyone seems to use the terms interchangably depending on the connotation a marketing department wants for a particular model.
I think notebooks are not really the word you want; I agree with others that it appears to be a more worldwide, generic synonym for laptop. It think it just means a fold-up PC... to differentiate it from other portables (like "handhelds" or "tablet PCs")
But there _is_ an industry term that describes _your_ definition of notebook. It's DTR, or "desktop replacement". Meaning you use it as your desktop, but you can also carry it around.
But DTR isn't a marketing friendly acronym I guess...
I'll bet anyone a few lattes that it is none other than MediaFrame.
Why?
If you go to their website they claim that "MediaFrame for Mpeg-4 is set for a full release in the new year". They also dual license the product, with partners getting access to this as-yet-unreleased stuff.
XviD, which is detected in the encoder, creates an MPEG4-compatible video stream... MediaFrame has yet-unreleased support for MPEG4 decoding in pure java.... but isn't ready to release it yet... hmmmmmmmmm
It's feature set is also eerily similar to VX30: - Supports DRM - Supports client usage tracking. - Supports bandwidth detection and delivers media accordingly
DrunkenBatman paints a picture where Airlock (MediaFrame) is all gaa-gaa about this pure-java client solution, and just so happens to like MediaFrame and VX30, and PANS absolutely everything else.
I bet it was ALL AIRLOCK'S IDEA to market MediaFrames more advanced product line through the VX30 brand... they are the kings of viral marketing... MXS probably promised them the encoder/distribution side.
The same people who download music off the internet by the assload are precisely NOT the same people who care about the GPL and spend hours trying to prove MXS is a violator, etc.
Those people go to cdbaby.com, legally record live shows of local bands and search for "really-free" free music.
I know it's really easy to just cram every post you see on slashdot that isn't your from your friend or yourself into some representation of a geek living in his parent's basement with no morals and bad acne.
1) You may be behind a proxy server which doesn't like port 8090 2) Coral cache is sensitive to the lifetime of pages as reported by the original webserver and the also size of the page. If a page indicates it's non-cachable, coral cache will just forward the request. If a document is too small (1M IIRC?) it will also just forward the request
Forwarding the request to a slashdotted webserver doesn't do much, as you might expect!:-)
Well it's one of those tradeoff things. Either you make your pagetables have less entries per page with the additional address bits, or you aim for a reasonable maximum, with the knowledge that eventually you'll release a version 2 with more virtual address space and a new pagetable layout.
Wasting space in pagetables is bad for performance. Totally kills your cache and makes flushing TLBs more costly.
This was done to be somewhat compatible with 16-bit instructions in 16-bit modes. Later intel introduced PAEs which used parts of the segmentation mechanism to implement "weird ass vm mode", so you could have 36-bit of physical address with 32-bit pointers.
PAE was not nearly as bad as the 16->32 relationship
64-bit mode completely removes the segmentation step and has no need for PAEs.
It's even simpler than before, and it requires nothing new from an application developers' persepctive.
40 bits physical: The system can actually use 2^40 bytes (a terabyte) of RAM 48 bits virtual: The system may use 64-bit pointers, but the top 16-bits are ALWAYS zero.
(Virtual memory addresses are translated into physical addresses by page tables... swapping and memory mapped files and all sorts of fun stuff is done with these tricks that make you look like you have more "memory" than is actually there)
This is important because the page tables that translate virtual addresses into physical addresses are going to completely ignore that top 16-bits. This is done because 2^48 is an incredibly huge amount of space... you can't possibly have that many hard drives hooked up to one machine and swap into all of it or mmap that many files. You save space in memory if you have less wasted page tables since you can have less of them (by a factor of 60000!) At the same time you want two pointers to be equal when you compare them if they truely point to the same virtual memory, so we all agree that it's set to 0 rather than just keeping anything you want in that upper 16 bits.
64-bit mode on AMD abandons the idea of segments. You don't need them to get around the 4GB limit (no need for PAE), and no operating system was using segment protection of memory anyway; relying solely on page protection flags. Everything in 64-bit mode ends up in a known, fixed location of memory (like on old Macs)
Is that if you can do this in semi-realtime you can guesstimate the location of major directional lights in a real-world photograph and see if what comes out makes any sense. There might be some way to automate the process using some kind of simple model of what a "realistic" output image should look like.
Red screens of death will be what in the *nix world are called "panics". These are the kinds of errors that the system was not expecting and that there is no way of possbily recovering from. * Bad memory/parity/bus error in a kernel page * NULL pointer access in file system or security-related code * Hard disk/controller dies during paging * Double faults
Blue screens of death are the ones where the system is still "up" but it can't continue safely (either you decided with a setting, a driver made a choice, or the OS decided for you). These are more like "oops" in the linux kernel. * Audit logs / disks full * watchdog timers * Bad memory in user space * System/boot drive died * Other faults unhandled by drivers or an application
Blue errors are errors of circumstances that you could probably fix and reboot. Red errors are the ones you can't do much about. Red errors are probably microsoft's job to fix... or due to an unrecoverable hardware error. Maybe a reboot and it goes away...
Or it could be something simple like "Red" means it was an "unhandled exception" (interrupt context/unhandled exception from userspace) and "Blue" means it was called explictly by the kernel itself.
What you're thinking about is that option under system properties that makes the machine automatically reboot if it blue screens (they only way you can tell it happened is if you check the system log)
Restarting explorer is a seperate thing altogether. This has been possible in all the NTs.
It happens when explorer gets messed up for whatever reason (usually due to some kind of built-in behavior and removable media... unavailable network shares, etc.)
Since explorer drives most of the interface, it is designed to start if no existing copy is running. In Windows 95 and 98, it was also possible, BUT, generally speaking explorer dying was just a side-effect of a larger problem that would ultimately take down the whole system. In 95/98, a user-space issue could easily become a system issue.
But that is not the same thing as a BSOD. In Windows NT, a BSOD is strictly a system-level issue, explorer dying is a just a problem with explorer. They are almost always not connected.
That's because the low-level graphics libraries that display text blindly "slide" the contents of the framebuffer down to simulate text scrolling.
Probably use the same techniques Sun does... there is no "text mode" like on a PC. The BIOS just simulates a console on top of your framebuffer.
You'll get the same thing on a Sun if you do STOP+A or ctrl-break while X is running... you get the "console" text pushing up the GUI with a ok> prompt...
You're almost there. What you need first is a PROCEDURE, then you can evaluate the pros and cons of previously mentioned software for your needs. Or if these steps are simple enough, you could write a perl script to fill in the gaps.
1) Bring all the files together into one place (if you can). Resolve name collisions now, but don't worry too much about how. 2) Evaluate the existing metadata (is it consistent across all your file formats? how consistent is it?). Come up with a mapping. (OGG Comments of Artist and Composer map to IDV3 artist, etc.) 3) Decide on a common schema for your metadata. IE - I'm going to have Artist, Title, Album/Compilation, and Year for all my music. I'll have Title and Year for all my legally copied movies, etc. 4) UPDATE ALL YOUR METADATA. This is the painful part for which a lot of the tagging tools will be helpful. STICK TO THE SCHEMA. 5) Create a top level directory for each major media type (music, movies, pictures, text) I'm just going to focus on music... 6) Create a directory for each artist. You may be able to automate this with metadata extraction tools and a perl script. 7) Ensure you have no duplicates (The Cure vs Cure, The). If you do, you may need to FIX YOUR METADATA LOOP: 8) Make a subdirectory of an artist and call it "All Tracks". Move all the files matching the artist into the subdirectory. Every reference to this artist from any 9) For each album or compilation in which the tracks are featured, make a subdirectory under the artist (again, use a perl script and metadata extraction tools). Don't include any identifiable "Various/Sndtrk" compilations (usually the "track artist" and "artist" don't match in that case). Create seperate Compilation and Soundtracks directories at the artist level for this purpose. 10) Create a compilation-level subdirectory called "Incomplete", and one called "Other". Move any compilation-level subdirectories for albums you know are not complete into the Incomplete subdirectory. 11) For each compilation-level subdirectory for albums which you know are complete, make softlinks out of the directory into the "All Tracks" directory for that Artist. Use a scheme like TRACK# - ARTIST - TITLE.FMT. Note you don't have to rename any files in the "All Tracks" directory... you can keep those as is. 12) Repeat step 11 for all the incomplete albums in the subdirectory 13) Link any files not listed under a compilation in the Other directory 14) REPEAT
However, the lame-ass GUI is written in java. You can get rid of it by running MATLAB with the -nojava command line option. Besides most of the heavy lifting is done by LAPACK libraries that are bundled with it (those are written in a mix of C, Fortran and assembly... incidentally you can swap them out with a custom built one; that was popular for a quick speedup when opterons were out but they didn't support it directly) Sadly, MATLAB is just slow PERIOD on SPARCs. It can't be helped.
You wanted the PC itself to be act as a firewire drive?
Good luck. Macs have this built into the firmware, not PCs. I don't think it's even on anyone's radar. But I don't imagine it's too difficult to write something that could do the job using libraw1394 and the SBP2 documentation.
I disagree, it could accept the password as data from the host...
I smacked myself in the head after I posted realizing that you could easily use some OOB key exchange to do the same job.
Also, what does the physical protection offer you that the encryption doesn't? It doesn't make it any less difficult to get the encrypted data off the flash.
The only thing I could think is to prevent someone from installing something in the device that intercepts the plaintext travelling in/out of the device via the USB interface. But if they could do that unnoticed, they could also install logging into your end-user computer.
Why the hell did you link to a for-pay only article on Slashdot? Be honest, did you write it? The article from the german university is appreciated, but why even bother with that Forrester research BS.
Slashdot Mirror
The laptop vs. notebook thing doesn't really mean much of anything... everyone seems to use the terms interchangably depending on the connotation a marketing department wants for a particular model.
I think notebooks are not really the word you want; I agree with others that it appears to be a more worldwide, generic synonym for laptop.
It think it just means a fold-up PC... to differentiate it from other portables (like "handhelds" or "tablet PCs")
But there _is_ an industry term that describes _your_ definition of notebook.
It's DTR, or "desktop replacement".
Meaning you use it as your desktop, but you can also carry it around.
But DTR isn't a marketing friendly acronym I guess...
I'll bet anyone a few lattes that it is none other than MediaFrame.
... they are the kings of viral marketing ... MXS probably promised them the encoder/distribution side.
Why?
If you go to their website they claim that "MediaFrame for Mpeg-4 is set for a full release in the new year".
They also dual license the product, with partners getting access to this as-yet-unreleased stuff.
XviD, which is detected in the encoder, creates an MPEG4-compatible video stream... MediaFrame has yet-unreleased support for MPEG4 decoding in pure java.... but isn't ready to release it yet... hmmmmmmmmm
It's feature set is also eerily similar to VX30:
- Supports DRM
- Supports client usage tracking.
- Supports bandwidth detection and delivers media accordingly
DrunkenBatman paints a picture where Airlock (MediaFrame) is all gaa-gaa about this pure-java client solution, and just so happens to like MediaFrame and VX30, and PANS absolutely everything else.
I bet it was ALL AIRLOCK'S IDEA to market MediaFrames more advanced product line through the VX30 brand
Just a WILD THEORY...
You just happened to stumble on ryan's finding independantly.
The "drunkenblog guy" and eventhorizon (ryan) are collaborators.
The same people who download music off the internet by the assload are precisely NOT the same people who care about the GPL and spend hours trying to prove MXS is a violator, etc.
Those people go to cdbaby.com, legally record live shows of local bands and search for "really-free" free music.
I know it's really easy to just cram every post you see on slashdot that isn't your from your friend or yourself into some representation of a geek living in his parent's basement with no morals and bad acne.
But Scott, they're individuals... just like you.
Group hug!
Luxriousity Software
They offer Photoshop, Office, and Sound editor work-alikes for Windows and Mac.
Give you three guesses what you actually get for you $29.99...
You mean... slashdot?
Sourceforge?
I was just wondering what you meant by that.
1) You may be behind a proxy server which doesn't like port 8090
:-)
2) Coral cache is sensitive to the lifetime of pages as reported by the original webserver and the also size of the page.
If a page indicates it's non-cachable, coral cache will just forward the request. If a document is too small (1M IIRC?) it will also just forward the request
Forwarding the request to a slashdotted webserver doesn't do much, as you might expect!
Well it's one of those tradeoff things.
Either you make your pagetables have less entries per page with the additional address bits, or you aim for a reasonable maximum, with the knowledge that eventually you'll release a version 2 with more virtual address space and a new pagetable layout.
Wasting space in pagetables is bad for performance. Totally kills your cache and makes flushing TLBs more costly.
You still had segments.
The mapping was as follows:
Segment ID:Segment-relative address -> (segment descriptor) -> flat 32bit address
Flat address -> (page table) -> physical address
This was done to be somewhat compatible with 16-bit instructions in 16-bit modes. Later intel introduced PAEs which used parts of the segmentation mechanism to implement "weird ass vm mode", so you could have 36-bit of physical address with 32-bit pointers.
PAE was not nearly as bad as the 16->32 relationship
64-bit mode completely removes the segmentation step and has no need for PAEs.
It's even simpler than before, and it requires nothing new from an application developers' persepctive.
40 bits physical:
The system can actually use 2^40 bytes (a terabyte) of RAM
48 bits virtual:
The system may use 64-bit pointers, but the top 16-bits are ALWAYS zero.
(Virtual memory addresses are translated into physical addresses by page tables... swapping and memory mapped files and all sorts of fun stuff is done with these tricks that make you look like you have more "memory" than is actually there)
This is important because the page tables that translate virtual addresses into physical addresses are going to completely ignore that top 16-bits. This is done because 2^48 is an incredibly huge amount of space... you can't possibly have that many hard drives hooked up to one machine and swap into all of it or mmap that many files. You save space in memory if you have less wasted page tables since you can have less of them (by a factor of 60000!)
At the same time you want two pointers to be equal when you compare them if they truely point to the same virtual memory, so we all agree that it's set to 0 rather than just keeping anything you want in that upper 16 bits.
64-bit mode on AMD abandons the idea of segments.
You don't need them to get around the 4GB limit (no need for PAE), and no operating system was using segment protection of memory anyway; relying solely on page protection flags.
Everything in 64-bit mode ends up in a known, fixed location of memory (like on old Macs)
Is that if you can do this in semi-realtime you can guesstimate the location of major directional lights in a real-world photograph and see if what comes out makes any sense. There might be some way to automate the process using some kind of simple model of what a "realistic" output image should look like.
Red screens of death will be what in the *nix world are called "panics". These are the kinds of errors that the system was not expecting and that there is no way of possbily recovering from.
* Bad memory/parity/bus error in a kernel page
* NULL pointer access in file system or security-related code
* Hard disk/controller dies during paging
* Double faults
Blue screens of death are the ones where the system is still "up" but it can't continue safely (either you decided with a setting, a driver made a choice, or the OS decided for you). These are more like "oops" in the linux kernel.
* Audit logs / disks full
* watchdog timers
* Bad memory in user space
* System/boot drive died
* Other faults unhandled by drivers or an application
Blue errors are errors of circumstances that you could probably fix and reboot. Red errors are the ones you can't do much about. Red errors are probably microsoft's job to fix... or due to an unrecoverable hardware error. Maybe a reboot and it goes away...
Or it could be something simple like "Red" means it was an "unhandled exception" (interrupt context/unhandled exception from userspace) and "Blue" means it was called explictly by the kernel itself.
What you're thinking about is that option under system properties that makes the machine automatically reboot if it blue screens (they only way you can tell it happened is if you check the system log)
Restarting explorer is a seperate thing altogether. This has been possible in all the NTs.
It happens when explorer gets messed up for whatever reason (usually due to some kind of built-in behavior and removable media... unavailable network shares, etc.)
Since explorer drives most of the interface, it is designed to start if no existing copy is running. In Windows 95 and 98, it was also possible, BUT, generally speaking explorer dying was just a side-effect of a larger problem that would ultimately take down the whole system. In 95/98, a user-space issue could easily become a system issue.
But that is not the same thing as a BSOD. In Windows NT, a BSOD is strictly a system-level issue, explorer dying is a just a problem with explorer.
They are almost always not connected.
I was really not liking SLES. Lots of weird problems.
RHEL was much nicer...
(I'm bringing this up because I'm thinking of getting some V4xzs but I wanted to know about people's experiences with them)
That's because the low-level graphics libraries that display text blindly "slide" the contents of the framebuffer down to simulate text scrolling.
Probably use the same techniques Sun does... there is no "text mode" like on a PC. The BIOS just simulates a console on top of your framebuffer.
You'll get the same thing on a Sun if you do STOP+A or ctrl-break while X is running... you get the "console" text pushing up the GUI with a ok> prompt...
Bleh I'm babbling... sorry.
You're almost there.
What you need first is a PROCEDURE, then you can evaluate the pros and cons of previously mentioned software for your needs. Or if these steps are simple enough, you could write a perl script to fill in the gaps.
1) Bring all the files together into one place (if you can).
Resolve name collisions now, but don't worry too much about how.
2) Evaluate the existing metadata (is it consistent across all your file formats? how consistent is it?). Come up with a mapping. (OGG Comments of Artist and Composer map to IDV3 artist, etc.)
3) Decide on a common schema for your metadata.
IE - I'm going to have Artist, Title, Album/Compilation, and Year for all my music. I'll have Title and Year for all my legally copied movies, etc.
4) UPDATE ALL YOUR METADATA. This is the painful part for which a lot of the tagging tools will be helpful. STICK TO THE SCHEMA.
5) Create a top level directory for each major media type (music, movies, pictures, text)
I'm just going to focus on music...
6) Create a directory for each artist. You may be able to automate this with metadata extraction tools and a perl script.
7) Ensure you have no duplicates (The Cure vs Cure, The). If you do, you may need to FIX YOUR METADATA
LOOP:
8) Make a subdirectory of an artist and call it "All Tracks". Move all the files matching the artist into the subdirectory. Every reference to this artist from any
9) For each album or compilation in which the tracks are featured, make a subdirectory under the artist (again, use a perl script and metadata extraction tools). Don't include any identifiable "Various/Sndtrk" compilations (usually the "track artist" and "artist" don't match in that case). Create seperate Compilation and Soundtracks directories at the artist level for this purpose.
10) Create a compilation-level subdirectory called "Incomplete", and one called "Other". Move any compilation-level subdirectories for albums you know are not complete into the Incomplete subdirectory.
11) For each compilation-level subdirectory for albums which you know are complete, make softlinks out of the directory into the "All Tracks" directory for that Artist. Use a scheme like TRACK# - ARTIST - TITLE.FMT. Note you don't have to rename any files in the "All Tracks" directory... you can keep those as is.
12) Repeat step 11 for all the incomplete albums in the subdirectory
13) Link any files not listed under a compilation in the Other directory
14) REPEAT
This should get you organized.
I wish I could give you a hug.
However, the lame-ass GUI is written in java. You can get rid of it by running MATLAB with the -nojava command line option.
Besides most of the heavy lifting is done by LAPACK libraries that are bundled with it (those are written in a mix of C, Fortran and assembly... incidentally you can swap them out with a custom built one; that was popular for a quick speedup when opterons were out but they didn't support it directly)
Sadly, MATLAB is just slow PERIOD on SPARCs. It can't be helped.
You wanted the PC itself to be act as a firewire drive?
Good luck. Macs have this built into the firmware, not PCs. I don't think it's even on anyone's radar. But I don't imagine it's too difficult to write something that could do the job using libraw1394 and the SBP2 documentation.
Good luck!
This took me like 2 seconds to find.
I disagree, it could accept the password as data from the host
I smacked myself in the head after I posted realizing that you could easily use some OOB key exchange to do the same job.
Also, what does the physical protection offer you that the encryption doesn't? It doesn't make it any less difficult to get the encrypted data off the flash.
The only thing I could think is to prevent someone from installing something in the device that intercepts the plaintext travelling in/out of the device via the USB interface. But if they could do that unnoticed, they could also install logging into your end-user computer.
Why the hell did you link to a for-pay only article on Slashdot?
Be honest, did you write it?
The article from the german university is appreciated, but why even bother with that Forrester research BS.