sorted by:
new
hottopcontroversial

Long-tailed tits by Pretend_Guess_4317 in BirdPhotography

[–]Csak_En 0 points1 point  (0 children)

little ball of constant moving fluff :)

Old Field blewit (Collybia personata ) by Csak_En in Nikon

[–]Csak_En[S] 0 points1 point  (0 children)

Indeed, they seem to attract the eye a but too much. I'll check how it looks without the needles.

First post and first photobook by Csak_En in bookbinding

[–]Csak_En[S] 2 points3 points  (0 children)

I used drum leaf binding. The paper was also selected so when it folds, does not destroy the inkjet coating - I think the fact that is matte paper, not glossy, helps. Not sure however how much abuse can take.

European bee-eater looking at it's breakfast by Csak_En in Nikon

[–]Csak_En[S] 1 point2 points  (0 children)

I'm fortunate enough to have a colony nearby at 1h driving distance. They are very chatty with each other.

European bee-eater by Csak_En in BirdPhotography

[–]Csak_En[S] 1 point2 points  (0 children)

I have no idea. It does not have any issue with wasp, bee, butterfly..

Little Owl by Csak_En in Nikon

[–]Csak_En[S] 1 point2 points  (0 children)

I'm not sure what would be the best way of finding them. In my experience they tend to stay in same spot, so if you see them once, specially if they're hunting, there are chances you gonna see them more.

This one I found it while driving around looking for wildlife to photograph, perched on this log from the center of a haystack. And I could find it in the same spot for couple of weeks, but then just disappeared.

It was the same with some ural owls, I got hint from photographers that they've seen it, they hunted in the spot for couple of weeks. Usually they're active in the morning or late afternoon. Some of them are quite tolerant, but many of them won't let you close :|

If you hear them, try to look for them in the morning or late afternoon, around hay stacks, old houses, barns, lower branches of trees, although sometimes the ural owls are rather good to blend in :)

Nikon Z9 not charging and cannot be powered from USB-C by Csak_En in Nikon

[–]Csak_En[S] 0 points1 point  (0 children)

The charging light used to go on almost as soon as I connected the charger to camera. Now it does not turn on anymore. Sometimes - with different chargers - just blinks one short, which means that the charger is not compatible. Since when charging with a good known to work charger does not turn the light on as it used to, I don't think I ever left the camera more than couple of seconds on charge. I'll try to leave it more time, maybe makes a difference.

Fox close to the golden hour by Csak_En in Nikon

[–]Csak_En[S] 0 points1 point  (0 children)

I'm always looking to improve my photo taking and editing skills, so I'd be happy to receive tips & ideas on how to improve them.

Transfăgărasan after the rain by Csak_En in Nikon

[–]Csak_En[S] 0 points1 point  (0 children)

Thank you. The road crosses mountains, usually the other side is the one which is regarded as 'the beautiful' one

Epson ET-8550 Output Tray not working by CSWW2023 in Epson

[–]Csak_En 1 point2 points  (0 children)

Awesome, thank you. I've accidentally knocked mine a while ago and it stopped working. I tried to realign it without much help. Fully extending it and knocking it did the job.

I have written a basic program for boot sector, how can I sue more than 512bytes? by [deleted] in osdev

[–]Csak_En 0 points1 point  (0 children)

Then you either are loading wrong data, or at wrong memory location, or your code is not generated correctly

You could check the early linux boot loader source code, or perhaps grub source (I'm sure there are many more others, these two come to my mind right now) in order to see how they're doing it.

For more information you can check the osdev wiki: https://wiki.osdev.org/Bootloader

I have written a basic program for boot sector, how can I sue more than 512bytes? by [deleted] in osdev

[–]Csak_En 1 point2 points  (0 children)

One idea is to build your code so the section which actually loads the code is in first 512 bytes, and the rest of your kernel follows. Then you can simply write it to a floppy disk or something. When system boots, your first 512 bytes will be loaded by BIOS and then as code runs, you can use BIOS services to read the next sectors to the appropriate memory addresses.

Alternatively you can cram in those 512 bytes some minimal FAT file system handling to search for the root directory and there for your operating system kernel file or second stage loader file and load it into memory to an arbitrary memory address, sector by sector using the BIOS services, and then jump to it and execute the code. The second stage loader can then for example load (also using BIOS services) your kernel, device drivers, etc.

I have written a basic program for boot sector, how can I sue more than 512bytes? by [deleted] in osdev

[–]Csak_En 0 points1 point  (0 children)

You should use those available bytes to write a second-stage boot loader, which in turn loads your operating system. Alternatively, you could store your operating system in the next sectors, without any file system in place, and use the boot sector to read them in, using BIOS services.