The video I saw of the music player looked exactly like his hardrive design. It was a big revolving cylinder made out of pistons and different blocks allowed redstone to travel to the note blocks. This is copying because he stated 'I have made' right in his first sentence. He didn't make it, somebody else made it.
The video I saw of the music player looked exactly like his hardrive design. It was a big revolving cylinder made out of pistons and different blocks allowed redstone to travel to the note blocks. This is copying because he stated 'I have made' right in his first sentence. He didn't make it, somebody else made it.
The music cylinder had to be written manually, by breaking and setting blocks. This thing does that by itself through redstone commands.
The music player was like a CD, this is a hard drive disk.
The video I saw of the music player looked exactly like his hardrive design. It was a big revolving cylinder made out of pistons and different blocks allowed redstone to travel to the note blocks. This is copying because he stated 'I have made' right in his first sentence. He didn't make it, somebody else made it.
Did you even watch the video I linked?
OP said he didn't design the punch card system (that the music player uses)
and if that is STILL copying, then every CPU or anything made with logic gates would be copying.
Are you kidding? Those exist. Unless you mean because of its compactness, this is in no way revolutionary.
And yea, this is extremely compact, but I would imagine also very slow.
This fills in the non-volatile storage gap.
there are tons of ram, but they're HUGE (and hopefully fast)
then there have been roms, hardcoded by torches or whatnot.
but a 0.7kb of fast read/slow write storage would allow true storage for alot of CPUs
this is just the next step from the PBM Array.
The video I saw of the music player looked exactly like his hardrive design. It was a big revolving cylinder made out of pistons and different blocks allowed redstone to travel to the note blocks. This is copying because he stated 'I have made' right in his first sentence. He didn't make it, somebody else made it.
So every vehicle on the road is a copy of the Model A? Get real. He MADE this design using elements of other circuits just as car companies MADE cars using already designed parts (the tire, for one). This is an original design. If you still have a problem with it, build a bridge and get over it. Just don't use any technology or items ever conceived or designed in the history of man kind to make your bridge.
Rollback Post to RevisionRollBack
If you think the title and OP tells you everything you want to know about a thread, don't reply. If you want to actually read the thread and post an intelligent reply, you're welcome to it.
err looking at the writing head (i could be wrong) it looks like your punching in an entire row of 15 at a time....so each row is acting as a single bit resulting in like 49 bits....also how easily can i rig this to my adder/subtractor array and hook it to a 7 seg display? i only need like to store 10 bits
Rollback Post to RevisionRollBack
When life gives you melons, you're probably dyslexic.
What do you mean by automatic? without connecting it to an ALU or something there is no way to make it truly automatic. As it is the write op can be performed by pulling levers to run the write heads. It could be easily connected to an ALU or even just an adder without much work though.
What I mean is, do you command the write head to "set bit to 1" and it somehow figures out or decides where to pull the 1 from, or do you tell it to "move bit 3 from row 6 to bit 6 row 3" (the numbers don't matter).
Basically, how much information do you need to tell it to write a specific line of data.
I don't really understand the one OP posted, not sure I understand how it writes.
I made a working 46 byte writable punchcard memory array already:
Making it writable is not a trivial task :smile.gif:
Mine has to move a bit from one half of the disc into the write head before it can use it to write to the blank half of the disc. This means that I can only use half of the total memory that it contains.
What I mean is, do you command the write head to "set bit to 1" and it somehow figures out or decides where to pull the 1 from, or do you tell it to "move bit 3 from row 6 to bit 6 row 3" (the numbers don't matter).
Basically, how much information do you need to tell it to write a specific line of data.
At the moment I need to tell it where to move the bit from but in later versions I will have it fully automated
I don't really understand the one OP posted, not sure I understand how it writes.
I made a working 46 byte writable punchcard memory array already:
Making it writable is not a trivial task :smile.gif:
Wow. This removes the 1/2 memory limit. But it seems to have complicated wiring. You should make a tutorial or something.
I understand the concepts now, but I would love a Tut so I can build one.
The music cylinder had to be written manually, by breaking and setting blocks. This thing does that by itself through redstone commands.
The music player was like a CD, this is a hard drive disk.
Did you even watch the video I linked?
OP said he didn't design the punch card system (that the music player uses)
and if that is STILL copying, then every CPU or anything made with logic gates would be copying.
This thread is now [Diamond]
It is sill a nice idea anyways
This fills in the non-volatile storage gap.
there are tons of ram, but they're HUGE (and hopefully fast)
then there have been roms, hardcoded by torches or whatnot.
but a 0.7kb of fast read/slow write storage would allow true storage for alot of CPUs
this is just the next step from the PBM Array.
This thread is now [Diamond]
So every vehicle on the road is a copy of the Model A? Get real. He MADE this design using elements of other circuits just as car companies MADE cars using already designed parts (the tire, for one). This is an original design. If you still have a problem with it, build a bridge and get over it. Just don't use any technology or items ever conceived or designed in the history of man kind to make your bridge.
What I mean is, do you command the write head to "set bit to 1" and it somehow figures out or decides where to pull the 1 from, or do you tell it to "move bit 3 from row 6 to bit 6 row 3" (the numbers don't matter).
Basically, how much information do you need to tell it to write a specific line of data.
Mine has to move a bit from one half of the disc into the write head before it can use it to write to the blank half of the disc. This means that I can only use half of the total memory that it contains.
At the moment I need to tell it where to move the bit from but in later versions I will have it fully automated
Wow. This removes the 1/2 memory limit. But it seems to have complicated wiring. You should make a tutorial or something.
I understand the concepts now, but I would love a Tut so I can build one.
CornerStone Castle
Minecraft Free Build Map
Paininabox's Thread O' Links