Live data from Hacker News

Debug Project

debug.com

121–127 of 127 posts

Re: Debug Project

#121
post #67

My understanding (very informal armchair) is that someone could relatively easily wipe out aedes aegypti using a gene drive with a sort of sex-selective infertility: Release a few thousand females carrying a gene drive that produces all infertile males, and all fertile females (who all also have the same gene due to it being a gene drive). Every generation, there are more and more infertile males, and more and more f…

You'd want fertile males and infertile females (it's different from the idea on the article), so you could contaminate the population faster.

But any claim of completely wiping out a thriving species with a single action is doubtful. I'm all for trying this one, but I'm not bullish on its long-term success.

Re: Debug Project

#122
post #91

Earlier quoted context omitted.

The DEBUG utility was originally named DEBUG.COM in early versions of MS-DOS, but it was renamed to DEBUG.EXE starting with MS-DOS 3.2 Shoutout to the 12 of us who remember debug> g=c800:5

Sure I remember, but since I purchased Spinrite doing lowlevel was needed just once while changing ST-506 controller to a different type or for a new disk, former was quite much rarer needed. Then even after std lowlevel it was worth using Spinrite to check if interleave value was proper. And if it wasn't it was worth letting it first before anything else. Same when changing a faster CPU as it could speed up IO so mu…

I had Spinrite III; Gibson made good stuff. But I was often in situations where all I had was a WD, etc MFM controller.

Re: Debug Project

#123
post #91

Earlier quoted context omitted.

Sure I remember, but since I purchased Spinrite doing lowlevel was needed just once while changing ST-506 controller to a different type or for a new disk, former was quite much rarer needed. Then even after std lowlevel it was worth using Spinrite to check if interleave value was proper. And if it wasn't it was worth letting it first before anything else. Same when changing a faster CPU as it could speed up IO so mu…

Sigh. How the times change. Right now I'm looking at 2 days to rebuild my NAS array after adding another 10TB disk.

True, that's some things have changed.

But it's when you consider taking first full drive backup times. It still takes 'forever' when you'd rather like to get on with fixing single disk issues. Or like when you wait RAID rebuilds too.

We did plan our maintenance tasks so, that there was something else useful we could do while obligatory backup and Spinrite was running. Upgraded another devices EPROM's, PC BIOS or dot matrix printer EPROM, cleaned printer heads, chaff and dust from chassis, changed colour ribbon to it. Ran updates to software we had sold etc. And went lunch with the customer:)

Re: Debug Project

#124

Earlier quoted context omitted.

A more apt analogy: I don't consider North Sentinel Island to be part of the modern world, since there is no relevant innovation going on there, it has no influence on the rest of the world, and there is nothing to be learned there.

You miss debug.com, wish there was an equivalent for the modern era, find out that windbg does almost all these things today, and say there's nothing of value there. I say this as something who does all the things you described debug.com as doing, in this modern era.

You are missing the point.

Windows is not a platform for serious people.

Re: Debug Project

#125
post #123

Earlier quoted context omitted.

Sigh. How the times change. Right now I'm looking at 2 days to rebuild my NAS array after adding another 10TB disk.

True, that's some things have changed. But it's when you consider taking first full drive backup times. It still takes 'forever' when you'd rather like to get on with fixing single disk issues. Or like when you wait RAID rebuilds too. We did plan our maintenance tasks so, that there was something else useful we could do while obligatory backup and Spinrite was running. Upgraded another devices EPROM's, PC BIOS or dot…

It turned into 5 days. After realising I'd forgotten to change the block size to 4096 and it was horribly slow, I yanked the drive out, tried with my utility to set it to 4096 bytes and failed, found another utility that did the job, put the drive back in, wait 3 days for it to rebuild the array without the new disk, and then another two days to add the disk back in. Sigh.

Still, with 4k block sizes, it goes like shit off a shovel.

Re: Debug Project

#126

Earlier quoted context omitted.

You miss debug.com, wish there was an equivalent for the modern era, find out that windbg does almost all these things today, and say there's nothing of value there. I say this as something who does all the things you described debug.com as doing, in this modern era.

You are missing the point. Windows is not a platform for serious people.

Maybe so, but that's not what you claimed. You claimed that WinDbg "does not assemble or disassemble", when of course it does. Try to be more accurate with your claims if you want serious people to take you seriously.

Re: Debug Project

#127

Earlier quoted context omitted.

You are missing the point. Windows is not a platform for serious people.

Maybe so, but that's not what you claimed. You claimed that WinDbg "does not assemble or disassemble", when of course it does. Try to be more accurate with your claims if you want serious people to take you seriously.

What I said, in part, is:

> Moreover, I don't consider Windows to be part of the modern era,

Why are you lying about what I said when everyone can see it?

Post reply on HN