I like to put as little strain as possible on the floppy disks that I have, especially when installing operating systems. I thus like to prepare disk images on my modern Linux box in QEMU (where I can use floppy images instead of actual disks) and then transfer them over to my real retro box.
Older operating systems like OS/2 make extensive use of CHS addressing and even store some of this information in the HPFS filesystem header. CHS info spreads all over the place. So, simply creating a QEMU disk image, installing something and then copying to another drive *probably* won't work, because QEMU guesses *some* CHS geometry that won’t necessarily match that of the target drive.
The solution is to a) create a QEMU disk image of the exact same size (in bytes) as the intended target drive, b) configure a matching CHS geometry in QEMU. The latter can be done like so:
-drive file=warp3.raw,if=none,id=disk1,format=raw
-device ide-hd,drive=disk1,cyls=495,heads=16,secs=32,bios-chs-trans=none
How do you know the correct CHS geometry? Ask the BIOS of the target machine.
And then be very thankful that we don’t have to deal with this anymore today. 😂
I like to put as little strain as possible on the floppy disks that I have, especially when installing operating systems. I thus like to prepare disk images on my modern Linux box in QEMU (where I can use floppy images instead of actual disks) and then transfer them over to my real retro box.
Older operating systems like OS/2 make extensive use of CHS addressing and even store some of this information in the HPFS filesystem header. CHS info spreads all over the place. So, simply creating a QEMU disk image, installing something and then copying to another drive *probably* won't work, because QEMU guesses *some* CHS geometry that won’t necessarily match that of the target drive.
The solution is to a) create a QEMU disk image of the exact same size (in bytes) as the intended target drive, b) configure a matching CHS geometry in QEMU. The latter can be done like so:
-drive file=warp3.raw,if=none,id=disk1,format=raw
-device ide-hd,drive=disk1,cyls=495,heads=16,secs=32,bios-chs-trans=none
How do you know the correct CHS geometry? Ask the BIOS of the target machine.
And then be very thankful that we don’t have to deal with this anymore today. 😂
I like to put as little strain as possible on the floppy disks that I have, especially when installing operating systems. I thus like to prepare disk images on my modern Linux box in QEMU (where I can use floppy images instead of actual disks) and then transfer them over to my real retro box.
Older operating systems like OS/2 make extensive use of CHS addressing and even store some of this information in the HPFS filesystem header. CHS info spreads all over the place. So, simply creating a QEMU disk image, installing something and then copying to another drive *probably* won't work, because QEMU guesses *some* CHS geometry that won’t necessarily match that of the target drive.
The solution is to a) create a QEMU disk image of the exact same size (in bytes) as the intended target drive, b) configure a matching CHS geometry in QEMU. The latter can be done like so:
-drive file=warp3.raw,if=none,id=disk1,format=raw
-device ide-hd,drive=disk1,cyls=495,heads=16,secs=32,bios-chs-trans=none
How do you know the correct CHS geometry? Ask the BIOS of the target machine.
And then be very thankful that we don’t have to deal with this anymore today. 😂
I like to put as little strain as possible on the floppy disks that I have, especially when installing operating systems. I thus like to prepare disk images on my modern Linux box in QEMU (where I can use floppy images instead of actual disks) and then transfer them over to my real retro box.
Older operating systems like OS/2 make extensive use of CHS addressing and even store some of this information in the HPFS filesystem header. CHS info spreads all over the place. So, simply creating a QEMU disk image, installing something and then copying to another drive *probably* won't work, because QEMU guesses *some* CHS geometry that won’t necessarily match that of the target drive.
The solution is to a) create a QEMU disk image of the exact same size (in bytes) as the intended target drive, b) configure a matching CHS geometry in QEMU. The latter can be done like so:
-drive file=warp3.raw,if=none,id=disk1,format=raw
-device ide-hd,drive=disk1,cyls=495,heads=16,secs=32,bios-chs-trans=none
How do you know the correct CHS geometry? Ask the BIOS of the target machine.
And then be very thankful that we don’t have to deal with this anymore today. 😂
> Error error parsing created field: parsing time "1713565714000000000" as "2006-01-02T15:04:05Z07:00": cannot parse "565714000000000" as "-"
And now it's even offline according to Clownflare…
I played around with my torch's green light and the camera for the first time. I have to practise and learn quite a bit. The tripod was definitely needed. With full zoom, the tripod was not rigid enough, though. Pressing the trigger button moved the cam quite a lot.
You might be able to make out Ursa Major in 06 in between the pixel errors. The clear night sky was very beautiful, I enjoyed it a lot. I also saw a bunch of satellites flying around. No shooting star, though.
https://lyse.isobeef.org/nachtwanderung-2024-07-07/
/https://baldo.cat/media/photos/photo_19107-07-2024_13-19-37.jpg) #catsoftwtxt
#catsoftwtxt
#catsoftwtxt
#catsoftwtxt
#catsoftwtxt
/https://duque-terron.cat/media/photos/photo_19007-07-2024_10-17-11.jpg) #catsoftwtxt
#catsoftwtxt
#catsoftwtxt
/https://baldo.cat/media/photos/photo_18907-07-2024_10-14-58.jpg) #catsoftwtxt
ugh so miserable. went the opposite direction than normal and did not realize the long bu gradual incline on 102nd ave. plus worn out from independence day, zoo, and now lennox's party today.
#running
ugh so miserable. went the opposite direction than normal and did not realize the long bu gradual incline on 102nd ave. plus worn out from independence day, zoo, and now lennox's party today.
#running
ugh so miserable. went the opposite direction than normal and did not realize the long bu gradual incline on 102nd ave. plus worn out from independence day, zoo, and now lennox's party today.
#running
> ChatGPT has an extremely broad range of success when it comes to producing functional code — with a success rate ranging from anywhere as poor as 0.66 percent and as good as 89 percent
> ChatGPT has an extremely broad range of success when it comes to producing functional code — with a success rate ranging from anywhere as poor as 0.66 percent and as good as 89 percent
> ChatGPT was fairly good at solving problems in the different coding languages — but especially when attempting to solve coding problems that existed on LeetCode before 2021. For instance
https://en.wikipedia.org/wiki/Tories_(British_political_party)
and
https://en.wikipedia.org/wiki/Tories_(British_political_party
https://en.wikipedia.org/wiki/Tories_(British_political_party)
and
https://en.wikipedia.org/wiki/Tories_(British_political_party
[here](https://en.wikipedia.org/wiki/Tories_(British_political_party))
[here](https://en.wikipedia.org/wiki/Tories_(British_political_party))
The rain finally got me, it was forecast to arrive later. Oh well.
Loud music from town blasted uphill into the forest. And fireworks reverbed with loud bangs over the hills in the middle of nature, holy crap!
URIs include components and subcomponents that are delimited by
characters in the "reserved" set. These characters are called
"reserved" because they may (or may not) be defined as delimiters by
the generic syntax, by each scheme-specific syntax, or by the
implementation-specific syntax of a URI's dereferencing algorithm.
If data for a URI component would conflict with a reserved
character's purpose as a delimiter, then the conflicting data must be
percent-encoded before the URI is formed.
reserved = gen-delims / sub-delims
gen-delims = ":" / "/" / "?" / "#" / "[" / "]" / "@"
sub-delims = "!" / "$" / "&" / "'" / "(" / ")"
/ "*" / "+" / "," / ";" / "="
URIs include components and subcomponents that are delimited by
characters in the "reserved" set. These characters are called
"reserved" because they may (or may not) be defined as delimiters by
the generic syntax, by each scheme-specific syntax, or by the
implementation-specific syntax of a URI's dereferencing algorithm.
If data for a URI component would conflict with a reserved
character's purpose as a delimiter, then the conflicting data must be
percent-encoded before the URI is formed.
reserved = gen-delims / sub-delims
gen-delims = ":" / "/" / "?" / "#" / "[" / "]" / "@"
sub-delims = "!" / "$" / "&" / "'" / "(" / ")"
/ "*" / "+" / "," / ";" / "="
I have mixed feelings about this show. On the one hand, it’s rather mediocre, to be honest. I can’t stand some of the characters/actors. Then again, the soundtrack is absolutely brilliant and the overall atmosphere is pretty great.
https://www.youtube.com/watch?v=e2xxizpHuoo
https://www.youtube.com/watch?v=9f_gfOrhV2k
I have mixed feelings about this show. On the one hand, it’s rather mediocre, to be honest. I can’t stand some of the characters/actors. Then again, the soundtrack is absolutely brilliant and the overall atmosphere is pretty great.
https://www.youtube.com/watch?v=e2xxizpHuoo
https://www.youtube.com/watch?v=9f_gfOrhV2k
I have mixed feelings about this show. On the one hand, it’s rather mediocre, to be honest. I can’t stand some of the characters/actors. Then again, the soundtrack is absolutely brilliant and the overall atmosphere is pretty great.
https://www.youtube.com/watch?v=e2xxizpHuoo
https://www.youtube.com/watch?v=9f_gfOrhV2k
I have mixed feelings about this show. On the one hand, it’s rather mediocre, to be honest. I can’t stand some of the characters/actors. Then again, the soundtrack is absolutely brilliant and the overall atmosphere is pretty great.
https://www.youtube.com/watch?v=e2xxizpHuoo
https://www.youtube.com/watch?v=9f_gfOrhV2k
Block them all! 😂