found a bug in FDISK in MS-DOS 5.0, where do I report this
Discussion
Loading...
Discussion
@thomasfuchs Ooh, memory just bubbled to the surface! You had to low level format based on the MFM/RLL drive controller before you ran fdisk.
debug<enter>
g=c800:5<enter>
Then fdisk, create a new partition.
Then format c: /s/v and give it a name.
The horrors....
@thomasfuchs
Maybe @shanselman could find it funny?
@alf149 @thomasfuchs Lemme open source it first and then we can take a PR 😉 https://github.com/microsoft/MS-DOS
@shanselman @alf149 @thomasfuchs
:)
"To whoever winds up maintaining this, I will apoligize in advance. I had just learned 'C' when writing this, so out of ignorance of the finer points of the langauge I did a lot of things by brute force. Hope this doesn't mess you up too much - MT 5/20/86"
https://github.com/microsoft/MS-DOS/blob/main/v4.0/src/CMD/FDISK/FDISK.C
@jpsays @shanselman @alf149 @thomasfuchs
```
#define BEGIN {
#define END }
```
I don't know whether to find this adorable or be horrified.
@mr_daemon @jpsays @shanselman @alf149 @thomasfuchs
The Bourne shell code, as I recall, had an entire header to make C look like Pascal and then was written in almost-Pascal.
@david_chisnall @mr_daemon @jpsays @shanselman @alf149 @thomasfuchs I know friends of ADA, who did this as well when they had to use C. The outcome is … special.
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled