Still hoping that design isn't final.
Pretty sure you need to submit the final design for these sorts of electrical/radio certification things?Still hoping that design isn't final.
how can they have a harddrive without a harddrive slot?
Is the 16GB PS3 going to be all that viable with all the mandatory installs?
thats gonna be like 12GB out of the box after format and bloatware
Whats the state of mandatory installs on recent PS3 software? Still common?
At 16GB, it is almost certainly not a traditional 2.5" HDD, and probably some sort of low cost flash memory.
The unanswered question is, will that hard drive be a standard 2.5" HDD or will they go the MS route of hard drive in proprietary shell.I know that but all of the models are the same besides the Hard drives so if the other models have harddrives the 16GB one will also have a place to put a hard drive.
The unanswered question is, will that hard drive be a standard 2.5" HDD or will they go the MS route of hard drive in proprietary shell.
No, hasn't been one in years.
You'll just have something like this in the HDD bay of the 16GB version:
Here's the link
Think of the an ultra cheap version of what's on the link and you'll get the idea.
So, when is the XTV model with HDMI pass-through coming?
Jeff - is this your PS 3.5:?
http://kotaku.com/5927310/unboxing-the-nasne-sonys-new-media-hub/gallery/1
Maybe this from the other thread?
Maybe this from the other thread?
Cause its only for Japan. They've had PS3 DVR hardware/software for a while now, Nasne is just an updated version of it.Seems cool. How come I haven't of this before?
Selling a PS3 model with clamps is smart because most of the products that are being sold right now use clamps so the price is just going to keep getting cheaper & cheaper & it's smaller & more can be made a lot faster than a screws & will save a lot of money on shipping & storage for the manufacturer.
or they can just stick a 16GB flash chip to the motherboard
Solder it on. Don't solder it on. Bam. Two products, same motherboard.That would result in a more complicated motherboard which will need to have the interface with the on board SSD as well as SATA, not to mention 2 different motherboards.
Why use SATA for an onboard flash chip? You realize there already is an onboard flash chip (for firmware only, so far) in every PS3. Doesn't use SATA either.Then there's the software where PS3 OS doesn't support 2 SATA devices.
Selling a PS3 model with flash is smart because most of the products that are being sold right now use flash memory so the price is just going to keep getting cheaper & cheaper & it's smaller & more can be made a lot faster than a harddrives & will save a lot of money on shipping & storage for the manufacturer.
That would result in a more complicated motherboard which will need to have the interface with the on board SSD as well as SATA, not to mention 2 different motherboards. Then there's the software where PS3 OS doesn't support 2 SATA devices.
Goes back to show what happened with the original Xbox. HDD's are an anchor when trying to lower the price of the system. Interesting to see what MS and Sony do next gen in regards to storage.
So the nasne(?) is like the PlayTV DVR thing I'm using right now?
You'd need to have the traces for the flash, in ADDITION to the traces that go to the HDD slot on the motherboard, even if you don't solder on the chip, adding cost to the motherboard. And you HAVE to use SATA, since the PS3 OS is set up to read/write from a SATA HDD and PS3 software counts on that SATA device being present. You can't install anything to the onboard flash chip besides the essential part of the system software that gets loaded first, as it's treated differently by the PS3 security system.Solder it on. Don't solder it on. Bam. Two products, same motherboard.Why use SATA for an onboard flash chip? You realize there already is an onboard flash chip (for firmware only, so far) in every PS3. Doesn't use SATA either.
You'd need to have the traces for the flash, in ADDITION to the traces that go to the HDD slot on the motherboard, even if you don't solder on the chip, adding cost to the motherboard. And you HAVE to use SATA, since the PS3 OS is set up to read/write from a SATA HDD and PS3 software counts on that SATA device being present. You can't install anything to the onboard flash chip besides the essential part of the system software that gets loaded first, as it's treated differently by the PS3 security system.
360 OS and software do not require a hard drive to be present, that's why they used USB for interfacing with the 4GB onboard flash, as it's no different than plugging in a 4GB USB stick to the 360 from a software/OS standpoint.You are significantly overstating the problem. The 360 didn't have any issue adding the same exact thing to that platform, although they just use what is basically an internal USB drive from what I remember, rather than flash soldered to the board.
There's no reason to believe even filesystem-specific code is hard-linked into any application, much less interface-layer code. In any sane system those are abstracted away into OS layers and none of the using code can tell the difference between writing to a network share across the globe or writing to /dev/shm.You'd need to have the traces for the flash, in ADDITION to the traces that go to the HDD slot on the motherboard, even if you don't solder on the chip, adding cost to the motherboard. And you HAVE to use SATA, since the PS3 OS is set up to read/write from a SATA HDD and PS3 software counts on that SATA device being present. You can't install anything to the onboard flash chip besides the essential part of the system software that gets loaded first, as it's treated differently by the PS3 security system.
Goes back to show what happened with the original Xbox. HDD's are an anchor when trying to lower the price of the system. Interesting to see what MS and Sony do next gen in regards to storage.
They obviously know enough to differentiate between a blu-ray, hdd, and usb. adding a hdd2 would complicate things.There's no reason to believe even filesystem-specific code is hard-linked into any application, much less interface-layer code. In any sane system those are abstracted away into OS layers and none of the using code can tell the difference between writing to a network share across the globe or writing to /dev/shm.
Is it really EASIER or CHEAPER to make a new interface, write the driver for it, and extensively test it compared to just sticking 16GB of flash in a SATA interface? Why would Sony go that route when all they're trying is to reduce costs with the PS3? It's a lot more effort.Adding a direct-to-chip interface, if it indeed does not exist yet, should not be hard. It's the easiest kind of interface you can abstract in software, because it doesn't need to be compatible with any outside device. It can use the same filesystem as the HDD. Those are independent blocks to mix and match.
Not the same thing as they did not increase the number of devices in the system. Less stuff was kept on the boot flash and more on the HDD. They did not make any part of the boot flash accessible to the user outside of applying firmware updates, so they can't just add 16GB to there and make it user accessible like a HDD.They even already changed the storage policy for the firmware itself. Launch models had a big chunk of flash (256MB? 512MB? don't remember) to store the whole thing. Revisions then switched to storing only a small bootstrap fragment in a 16MBish flash chip, with the rest spilled out to the HDD. So they actually did something like that before. Arguably harder than moving user storage back to flash.
Why spend all that money testing an update over all PS3's when you can get away with not having one for this purpose and work on adding other features? How would spending the money and resources this way benefit the consumer in any way? How would it benefit Sony?I'm sure there'll be a firmware update to establish a common code base between old and new models. But I really don't see a non-SATA interface as a technical challenge or cost problem.
Don't you think the PS3 board is already as small as it could be and has as few layers as it can get away with the components it has on board? What do you think adding an extra SATA interface will do to it? You can certainly design a board that's smaller if you don't have to worry about routing traces for extra chip(s) on the motherboard.Board traces also aren't produced individually. You start with a surface fully plated in copper. Then you litographically "harden" the parts you want to keep. All the rest is removed with acids, then the board is coated in an insulation layer (again masked out at contact points). It's a full-surface process at every step, and, as long as the number of layers and the outer dimensions of the board remain constant, it makes no difference if you have fewer traces or more traces.
That would result in a more complicated motherboard which will need to have the interface with the on board SSD as well as SATA, not to mention 2 different motherboards. Then there's the software where PS3 OS doesn't support 2 SATA devices.
You'd need to have the traces for the flash, in ADDITION to the traces that go to the HDD slot on the motherboard, even if you don't solder on the chip, adding cost to the motherboard. And you HAVE to use SATA, since the PS3 OS is set up to read/write from a SATA HDD and PS3 software counts on that SATA device being present. You can't install anything to the onboard flash chip besides the essential part of the system software that gets loaded first, as it's treated differently by the PS3 security system.
well they changed from Harddrive to System Storage so something has changed.
Without commenting on whether or not Sony will add the 16GB to the motherboard, I do feel like pointing out that the PS3's OS is based on FreeBSD. It already supports all the SATA devices the hardware can throw at it, and like virtually all Unix derivatives, it completely abstracts extra drives as folders that can be mounted anywhere. All Sony would have to do is simply add a line in the boot script so that if it found two SATA hard drives, mount the 16GB flash as OS storage space. Maybe throw in a script to copy the contents of the flash onto the hard drive after it formats the hdd.The only way it could be integrated on board is if they update the OS to handle 2 SATA devices AND run the traces for 2 SATA ports on the motherboard (1 to the slot, 1 to the soldered chip). I think this would be significantly more expensive than just sticking a tiny SATA board with 16GB's of flash in the HDD slot.
That realization came at an interesting point in time then.Maybe they realised it was confusing if somebody connected an external hard drive via USB and used that option. You know, they'd have wiped their entire PS3 unintentionally.
We already know what Sony are doing, Gaikai.
Full software PS2 BC isn't quite a reality even now. They have had a PS2 emulator in FW for a while now but hadn't actually used it because only a very small amount of games worked with it and even those needed to be optimised on a case by case basis. Re-introducing PS2 BC seems off the cards for now especially since they can milk that limited amount of games on PSN.Perfect opportunity to reintroduce PS2 BC now that they have full SW emulation for PS2 classics, and actual PS2 production is winding down. If $179 price point is true PS2 BC could be a real incentive for those still using PS2 to upgrade to PS3.
Huh? No it doesn't.That would result in a more complicated motherboard which will need to have the interface with the on board SSD as well as SATA, not to mention 2 different motherboards. Then there's the software where PS3 OS doesn't support 2 SATA devices.
Huh? No it doesn't.
//global list of all sata devices
SataDevice sataDevices[1]; //one should be enough for anybody.
//Also, hardcoding this, because we're idiots.
;pCode://global list of all sata devices SataDevice sataDevices[1]; //one should be enough for anybody. //Also, hardcoding this, because we're idiots.