Hard Drive (Default Events) *New* [Anatomy Video]

[lcyGamma]

Wow :o

[Ad Bot]

[SeventhSandwich]

I have just completed a working prototype keyboard system for the harddrive. Currently it can only lock/unlock memory, and write to it. Plans are in work for reading/output.

-snip-

Why did you attach it to the harddrive?

[Mr.Noßody]

Id like to see a massive computer build that can fully function with a much higher resolution.
These small ones are neat, but dont impress me too much..

[Remousamavi]

Why did you attach it to the harddrive?

Because it's a component of said hard drive. The upper picture is the same keyboard detached. It has its own HIO port, and the casing is designed to look as if it's a part of the drive.

[SeventhSandwich]

What does the lock/rewrite part do?

I understand that it signals to the harddrive to begin rewriting itself, but how does it 'lock' it?

Also, should you begin writing to the first block right after it finishes beeping 5 times, or should you wait 33ms like on the table you put in the pdf?

EDIT: I sent a relay through the lock/rewrite part, but it did not reset all the memory blocks to 1, even though I didn't send anything else through the 'write transfer' part.

[lcyGamma]

EDIT: I sent a relay through the lock/rewrite part, but it did not reset all the memory blocks to 1, even though I didn't send anything else through the 'write transfer' part.

Write / relock allows you to set memory bricks to be writable, or to have them be unwritable. It does not restore a value to 1. A writing device will never need to "clear" the drive because there is always a value. It would unlock the drive, and continue writing the next value (if it had previously written 1 then to get to three it would know it needs 2).

[SeventhSandwich]

Write / relock allows you to set memory bricks to be writable, or to have them be unwritable. It does not restore a value to 1. A writing device will never need to "clear" the drive because there is always a value. It would unlock the drive, and continue writing the next value (if it had previously written 1 then to get to three it would know it needs 2).

How do you make it switch a memory brick to writable or un-writable? What's the difference?

Does it depend on the timing?

[Remousamavi]

The topmost layer of the HIO sets memory to be writable or unwritable, taking 5 seconds to complete.

Writable, and you can alter the contents of the memory with the writing part of the HIO.

Unwritable, and the writer doesn't do a thing, the memory chips stay the same whatever you do.

[lcyGamma]

How do you make it switch a memory brick to writable or un-writable? What's the difference?

The drive sequentially locks, but can only be totally locked or unlocked with the erase chip. You can't pick and choose what to erase or write to in..

... well actually that is another bug. I've just realized that means if you have half a drive written and try to unlock it, then other half will become locked. forget lol.

[Crêpe]

Can we have it when it is completed?

[lcyGamma]

Hey I just want some feedback.

The reading system seems to well well on single player but on the Internet, because of how tiny the timing is, its prone to giving out unstable reads.

Wouldn't be messing around with anyone if I delayed the read speed and adjusted the read timing in the guide would I? Nobody minds?

I don't want it to be unstable at all you see.

[Remousamavi]

I'm cool with the changes.

I've noticed a similar issue regarding input packets, where every so often a memory packet will end up one value off from what I intended, though that may be flaws in my input system.

[lcyGamma]

I've noticed a similar issue regarding input packets, where every so often a memory packet will end up one value off from what I intended, though that may be flaws in my input system.

How long are you waiting when writing?

I recommend 100MS per value and waiting until 1800MS has passed before writing to the next block for safety.

[nixton]

very cool.

[lcyGamma]

Thanks c: