Maker Pro
Maker Pro

Skybuck's Universal Code 5 (The Native Version)

J

JosephKK

Skybuck said:
The days of the bios and complicated hd reading/writing are long gone !

You learned more from me in this thread then you will ever learn in any
college out there ! ;) :)

Bye,
Skybuck.

And exactly what do you claim to have to have elucidated here?
 
J

JosephKK

Skybuck said:
Whatever dipshit.

All I know is I don't have to write complex code.

The bios chip or the harddisk chip or whatever does that :)

I only specify the sector number.

I don't have to specify the head, cylinder or whatever.

Bye,
Skybuck.

What kind of freaking idiot tries to access the disk without either
using or understanding the file system?
 
M

Michael A. Terrell

JosephKK said:
And exactly what do you claim to have to have elucidated here?


Isn't it obvious? Skyduck has proved that you can have an IQ of ice
water, and still post crap to USENET.


--
Service to my country? Been there, Done that, and I've got my DD214 to
prove it.
Member of DAV #85.

Michael A. Terrell
Central Florida
 
M

Michael A. Terrell

JosephKK said:
Just the facts jackass.


If that aioe.org forger forged 'dimbulb' posts, he would look more
intelligent.


--
Service to my country? Been there, Done that, and I've got my DD214 to
prove it.
Member of DAV #85.

Michael A. Terrell
Central Florida
 
M

MooseFET

If that aioe.org forger forged 'dimbulb' posts, he would look more
intelligent.

He did forge at least one and you are right.

Currently, the forger is doing a bunch with my name on them. I really
wonder why he doesn't just use his own name. He obviously knows a
fair bit about electronics.
 
S

StickThatInYourPipeAndSmokeIt

He did forge at least one and you are right.

Currently, the forger is doing a bunch with my name on them. I really
wonder why he doesn't just use his own name. He obviously knows a
fair bit about electronics.


Don't shit yourself, he is a fucking retard, and Usenet abuser that
should be charged with crimes, as I am quite sure he commits malicious
acts online, like hacking at your machine, Usenet post bombs, etc. etc.

The little retarded bastard should be in a prison cell.
 
J

JosephKK

Skybuck said:
Somebody that tries to access the disk you retard.

Bye,
Skybuck.

As in file open(), seek(), read(), write(), close(), create(), or
delete() calls through the file system? Or do you not have an OS or
file system at all?
 
J

JosephKK

Michael said:
If that aioe.org forger forged 'dimbulb' posts, he would look more
intelligent.

That would improve dimbulb's credibility for a short while.
 
M

Michael A. Terrell

JosephKK said:
That would improve dimbulb's credibility for a short while.


We can't have THAT happen!!! What WOULD his neighbors think? ;-)


--
Service to my country? Been there, Done that, and I've got my DD214 to
prove it.
Member of DAV #85.

Michael A. Terrell
Central Florida
 
M

Michael A. Terrell

StickThatInYourPipeAndSmokeIt said:
Don't shit yourself, he is a fucking retard, and Usenet abuser that
should be charged with crimes, as I am quite sure he commits malicious
acts online, like hacking at your machine, Usenet post bombs, etc. etc.

The little retarded bastard should be in a prison cell.


In the cell next to yours, of course. After all, retards of a
feather should be incarcerated together!


--
Service to my country? Been there, Done that, and I've got my DD214 to
prove it.
Member of DAV #85.

Michael A. Terrell
Central Florida
 
M

Michael A. Terrell

MooseFET said:
He did forge at least one and you are right.


It must have been one of his sock puppets that's filtered.

Currently, the forger is doing a bunch with my name on them. I really
wonder why he doesn't just use his own name. He obviously knows a
fair bit about electronics.


He feels slighted over something, but people like him are too high
strung. He might be Phil's brother, down under?


--
Service to my country? Been there, Done that, and I've got my DD214 to
prove it.
Member of DAV #85.

Michael A. Terrell
Central Florida
 
M

MooseFET

It must have been one of his sock puppets that's filtered.


He feels slighted over something, but people like him are too high
strung. He might be Phil's brother, down under?

Perhaps he does feel slighted. It would be better if he was using his
own name and told us what the heck he's so spun up about. He
obviously knows some electronics but I can't match him up with and of
the regulars.
 
C

ChairmanOfTheBored

In the cell next to yours, of course. After all, retards of a
feather should be incarcerated together!


"of a feather"? What laws have I broken, you retarded bastard? When
did I ever post in someone else's name?

STFU, you retarded twit.
 
K

Keith Latham

StickThatInYourPipeAndSmokeIt said:
On "brand new installs"? You're an idiot.

Yes. On brand new installs.

The installation process uses the file system the same as anything else.
Since the allocation process is FIRST AVAILABLE as soon as two files are
written and the first one is deleted there is a hole and fragmentation
gets started. And there are a lot of files loaded and deleted during the
installation process. The only way that the disk would not be fragmented
after an install is if the installation process specifically ran a
defrag at the end. I have never noticed this happening.

A possible allocation algorithm to minimise defragmentation is to always
allocate into the largest contiguous unused space. This minimizes the
possibility of fragmenting a new file and gives the greatest chance that
a delete will open up a larger space. This is very effective in an
environment where there is a lot of temporary files created and dropped.
Unfortunately, this is not the way Windose works.
 
K

Keith Latham

StickThatInYourPipeAndSmokeIt said:
It is "cluster" and no, generally not. It writes to the next
"available" write space, and newly "released", just previously written to
areas get put at the end of the list of available space as they get
marked "free", so the first cluster to get written to is the first one
that was originally available in the "newly formatted" original "list".
This insures that all areas on a drive's platter gets "used", instead of
keeping all your drive activity to a confined area on the drive, inviting
an early failure mode.

And GUARANTEES fragmentation.
 
M

MooseFET

StickThatInYourPipeAndSmokeIt wrote: [... disk fragmentation ....]
A possible allocation algorithm to minimise defragmentation is to always
allocate into the largest contiguous unused space.

This is less than perfect. It tends to spread the files uniformly
over the surface of the disk. This makes for many small gaps and
longer seeks on the average between files.

These days, it is likely that allocating into the first /last gap
bigger than a few gig would work better.

Pushing the allocation towards at least one end would tend to keep the
free space together.
 
Top