Reading Maximum Address Of The HD In LBA48

Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
Post Reply
Lprogster
Member
Member
Posts: 174
Joined: Tue Nov 14, 2006 11:59 am

Reading Maximum Address Of The HD In LBA48

Post by Lprogster »

...False alert!...
Last edited by Lprogster on Sat Sep 08, 2007 6:07 am, edited 1 time in total.
Lprogster
Member
Member
Posts: 174
Joined: Tue Nov 14, 2006 11:59 am

Post by Lprogster »

I think I have it working - I found a new ATA specification which told me what I needed.

Lster
pcmattman
Member
Member
Posts: 2566
Joined: Sun Jan 14, 2007 9:15 pm
Libera.chat IRC: miselin
Location: Sydney, Australia (I come from a land down under!)
Contact:

Post by pcmattman »

Lprogster wrote:I think I have it working - I found a new ATA specification which told me what I needed.

Lster
Care to share what you have to do to get the size in LBA48?
Lprogster
Member
Member
Posts: 174
Joined: Tue Nov 14, 2006 11:59 am

Post by Lprogster »

[EDIT]

Good luck,
Lster
Last edited by Lprogster on Fri Sep 14, 2007 12:23 pm, edited 1 time in total.
pcmattman
Member
Member
Posts: 2566
Joined: Sun Jan 14, 2007 9:15 pm
Libera.chat IRC: miselin
Location: Sydney, Australia (I come from a land down under!)
Contact:

Post by pcmattman »

My port mistake was worse - in my inport[size] function I forgot to return the data read from the port...
Lprogster
Member
Member
Posts: 174
Joined: Tue Nov 14, 2006 11:59 am

Post by Lprogster »

I tend to find, the more complex a task, the simpler the mistakes... LOL
User avatar
AndrewAPrice
Member
Member
Posts: 2309
Joined: Mon Jun 05, 2006 11:00 pm
Location: USA (and Australia)

Post by AndrewAPrice »

I remember reading a comment in early Linux source about a function that said something like "I hope this works. I'd hate to have to debug this".

The my complex the code is, the more you want to write it once and never touch it again and assume your the perfect coder who does have bugs.

It'll appear to work, until 2 months later when you've built a whole lot of code dependent on that code and after a day of debugging you've uncovered around 20 bugs in your original code.

It's even scarier when you find major bugs in your code (especially errors in pointer arithmetic) yet it runs perfectly and produces no seen side effects.
My OS is Perception.
User avatar
Candy
Member
Member
Posts: 3882
Joined: Tue Oct 17, 2006 11:33 pm
Location: Eindhoven

Post by Candy »

MessiahAndrw wrote:It's even scarier when you find major bugs in your code (especially errors in pointer arithmetic) yet it runs perfectly and produces no seen side effects.
Seen that a lot, sadly. Usually it's a function that makes a hash of everything but barely compiles, which is then never used.
Post Reply