No it doesn't. You're confusing IMAP and MAPI. IMAP is an open protocol for mail access. MAPI is Microsoft's proprietary mail and calendaring protocol.
Indeed, the IBM microdrive works in several digital cameras. You can find a list at the IBM compatibility matrix online. The Canon Powershot S20 is in the list and looks like a nice camera. It seems like a far better solution (performance and robustness) than the Sony approach.
I seem to recall reading somewhere that a 1GB version of the drive is expected in the near future.
One thing to be careful of is that if you got an earlier board and you want to run PC133 memory at 133MHz, download and upgrade to the latest BIOS. I would imagine it's some kind of timing issue. I recently built a server on a K7V, 650MHz K7, and 128MB PC133 memory (+7200rpm drives). It's seriously fast and has been totally stable so far.
I suspect that the whole thing has been blown out of proportion. There were a couple of issues with MTRR support and AGP support, but nothing major. It's somewhat likely that some people have had the usual issues with faulty hardware and have blamed it on the new K7 processor and motherboard support. There have certainly been enough "problems with the kernel" reported on linux-kernel that have turned out to be bad hardware.
To be able to advertize your OS and "Unix", you do indeed have to certify your OS with the current trademark holder, namely The Open Group. You have to at least pass the Unix95 specification testing. I believe that if you pass Unix98, that's fine too.
As to the assertion that portability is difficult in the Unix world, I would disagree strongly. It is easy to write bad code that is highly non-portable (I find a lot of people who pretty much only use Solaris fall into this trap). It is however possible to write code which will run on most if not all Unices with little or no modification. However, that puts the onus on the developer to familiarize themselves with the relevant standards, and also use as many systems as are available to them. Sadly whether it's laziness or unreasonable deadlines, this doesn't appear to be happen that often.
Quite correct. Pity they are such abject morons. You can buy TV's in the UK that can display NTSC as well as PAL, you can order a player from the US for a couple of hundred bucks, and you can get a transformer for peanuts. The 60/50HZ frequency difference is not an issue. You can now view region 1 DVDs in the UK without any hackery-pokery whatsoever.
Remind me again how the region code protected them ?????
"It would have cost us, the consumer, more money if they had decided to release 128 bit encrypted titles in the US and 40-bit encrypted titles to the rest of the world. That's two smaller runs rather than one larger run. Sure you can yell about the export laws but they're a different subject."
Umm, hello ! Can you say region codes ?
They already do have to do multiple different runs because the morons don't want your to view a US film in e.g. the UK due to the different release schedules in the cinemas. It doesn't seem to have occurred to them that it's not hard to run an NTSC TV and a US DVD player in the UK. Of course most people don't do that since lots of places sell "region free" players with modified firmware allowing people to view region 1 DVDs elsewhere anyway.
Check out the stories at The Register which has been commenting on memory prices recently.
From an article yesterday: The announcement came as world 64Mb DRAM prices today reached their highest ever levels. According to Asiabiztech.com, these chips were today selling at $12.75 per unit.
This compares to prices around the $5 mark in July.
Joe D'Elia, senior microprocessor analyst at Dataquest, said: "We are now seeing the difference between a buyer's and a seller's market.
"Everyone has kept stocks to an absolute minimum."
He also pointed out the huge difference between contract pricing -- which stands at around $7 -- and spot pricing for 64Mb DRAM.
To explain the sudden memory price rises, D'Elia added: "There is a lot of uncertainty in the market at the moment - surrounding technology such as Rambus. The manufacturers are capitalising on that."
You are confusing the virtual and physical address spaces. The Intel P6 line has a 36bit physical address bus allowing the chip to address up to 64GB of physical memory. However, since it is a 32-bit processor, you can only see 4GB of this memory at any time. You can change what you can see by playing games with PTEs (page table entries), and/or segment registers. To address >4GB of memory requires use of either wide (64-bit) PTEs, or the strange mode Intel added to the PII, that allows large pages with narrow PTEs. The Sequent Dynix/ptx OS supports up to 64GB of physical memory. The hard part is conserving enough kernel virtual address space.
No, not even the "Unix-on-32-bit-processor" world. Most commercial Unices running on 32-bit processors have large file support. I know that DYNIX/ptx does. Max filesystem/file size is 1TB or something like that. glibc2.1 (RH6.0) seems to have the relevant library-level support. We just need filesystem support in Linux.
The cost argument is fine up the point that you buy the games. PC games don't tend to cost $65 per game ! Still I can see your point. I'm waiting for the PSX2, this thing looks incredible.
Nope, not even close I'm afraid. The MX300 is hard-wired silicon. The SB-Live uses the EMU-10K chip which is a DSP making it quite a lot more flexible i.e. Creative can change (improve) the functionality by changing the programming of the DSP. You'd need programming specs to support the MX-300.
You'll be just fine. You are correct in that support is available in kernel 2.0.34+ and 2.1.60+ and hence 2.2. I personally mount a couple of >4GB fat32 partitions from my 13GB EIDE drive under Linux (2.2.5) which is running on a 3GB SCSI disk.
Long filenames work, but you will still be at the mercy of the usual VFAT semantics, so all files are owned by one user (cf mount -o uid=XXX), long filenames are supported, but are case-insensitive, etc.
It appears that there are number of versions of fdisk out there that don't grok the FAT32X partition type. This is the >2GB partition size support for which M$ went and created yet another partition type. Don't worry about it, you can still mount these partitions just fine.
Um, the URL you gave doesn't seem to work (at least for me). Doing a web search, I found a bunch of stuff at Dementia including three releases of the pam_krb4 code.
Looks like pam_krb4-981201.tar.gz would be a likely contender... t
Slashdot Mirror
No it doesn't.
You're confusing IMAP and MAPI.
IMAP is an open protocol for mail access.
MAPI is Microsoft's proprietary mail and calendaring protocol.
Tim
Indeed, the IBM microdrive works in several digital cameras. You can find a list at the IBM compatibility matrix online. The Canon Powershot S20 is in the list and looks like a nice camera. It seems like a far better solution (performance and robustness) than the Sony approach.
I seem to recall reading somewhere that a 1GB version of the drive is expected in the near future.
Tim
One thing to be careful of is that if you got an earlier board and you want to run PC133 memory at 133MHz, download and upgrade to the latest BIOS. I would imagine it's some kind of timing issue.
I recently built a server on a K7V, 650MHz K7, and 128MB PC133 memory (+7200rpm drives). It's seriously fast and has been totally stable so far.
I suspect that the whole thing has been blown out of proportion. There were a couple of issues with MTRR support and AGP support, but nothing major. It's somewhat likely that some people have had the usual issues with faulty hardware and have blamed it on the new K7 processor and motherboard support. There have certainly been enough "problems with the kernel" reported on linux-kernel that have turned out to be bad hardware.
Tim
You are quite correct.
To be able to advertize your OS and "Unix", you do indeed have to certify your OS with the current trademark holder, namely The Open Group.
You have to at least pass the Unix95 specification testing. I believe that if you pass Unix98, that's fine too.
As to the assertion that portability is difficult in the Unix world, I would disagree strongly. It is easy to write bad code that is highly non-portable (I find a lot of people who pretty much only use Solaris fall into this trap). It is however possible to write code which will run on most if not all Unices with little or no modification. However, that puts the onus on the developer to familiarize themselves with the relevant standards, and also use as many systems as are available to them. Sadly whether it's laziness or unreasonable deadlines, this doesn't appear to be happen that often.
Tim
Quite correct.
Pity they are such abject morons.
You can buy TV's in the UK that can display NTSC
as well as PAL, you can order a player from the US
for a couple of hundred bucks, and you can get a
transformer for peanuts. The 60/50HZ frequency
difference is not an issue. You can now view
region 1 DVDs in the UK without any hackery-pokery
whatsoever.
Remind me again how the region code protected them ?????
Tim
"It would have cost us, the consumer, more money if they had decided to release 128 bit encrypted titles in the US and 40-bit encrypted titles to the rest of the world. That's two smaller runs rather than one larger run. Sure you can yell about the export laws but they're a different subject."
Umm, hello !
Can you say region codes ?
They already do have to do multiple different runs because the morons don't want your to view a US film in e.g. the UK due to the different release schedules in the cinemas. It doesn't seem to have occurred to them that it's not hard to run an NTSC TV and a US DVD player in the UK. Of course most people don't do that since lots of places sell "region free" players with modified firmware allowing people to view region 1 DVDs elsewhere anyway.
From an article yesterday:
The announcement came as world 64Mb DRAM prices today reached their highest ever levels. According to Asiabiztech.com, these chips were today selling at $12.75 per unit.
This compares to prices around the $5 mark in July.
Joe D'Elia, senior microprocessor analyst at Dataquest, said: "We are now seeing the difference between a buyer's and a seller's market.
"Everyone has kept stocks to an absolute minimum."
He also pointed out the huge difference between contract pricing -- which stands at around $7 -- and spot pricing for 64Mb DRAM.
To explain the sudden memory price rises, D'Elia added: "There is a lot of uncertainty in the market at the moment - surrounding technology such as Rambus. The manufacturers are capitalising on that."
Tim
You are confusing the virtual and physical address spaces.
The Intel P6 line has a 36bit physical address bus allowing the chip to address up to 64GB of physical memory. However, since it is a 32-bit processor, you can only see 4GB of this memory at any time. You can change what you can see by playing games with PTEs (page table entries), and/or segment registers.
To address >4GB of memory requires use of either wide (64-bit) PTEs, or the strange mode Intel added to the PII, that allows large pages with narrow PTEs.
The Sequent Dynix/ptx OS supports up to 64GB of physical memory. The hard part is conserving enough kernel virtual address space.
No, not even the "Unix-on-32-bit-processor" world.
Most commercial Unices running on 32-bit processors have large file support. I know that DYNIX/ptx does. Max filesystem/file size is 1TB or something like that.
glibc2.1 (RH6.0) seems to have the relevant library-level support. We just need filesystem support in Linux.
The cost argument is fine up the point that you buy the games. PC games don't tend to cost $65 per game !
Still I can see your point. I'm waiting for the PSX2, this thing looks incredible.
Tim
Nope, not even close I'm afraid.
The MX300 is hard-wired silicon. The SB-Live uses the EMU-10K chip which is a DSP making it quite a lot more flexible i.e. Creative can change (improve) the functionality by changing the programming of the DSP. You'd need programming specs to support the MX-300.
Tim
You'll be just fine. You are correct in that support is available in kernel 2.0.34+ and 2.1.60+ and hence 2.2. I personally mount a couple of >4GB fat32 partitions from my 13GB EIDE drive under Linux (2.2.5) which is running on a 3GB SCSI disk.
Long filenames work, but you will still be at the mercy of the usual VFAT semantics, so all files are owned by one user (cf mount -o uid=XXX), long filenames are supported, but are case-insensitive, etc.
It appears that there are number of versions of fdisk out there that don't grok the FAT32X partition type. This is the >2GB partition size support for which M$ went and created yet another partition type. Don't worry about it, you can still mount these partitions just fine.
Tim
Looks like pam_krb4-981201.tar.gz would be a likely contender... t