teletype | team members and collaborate on code in real time | Code Editor library

One day, I too needed a delay routine capable of doing delays ranging from 0.5 sec to just a few msec. Read all about it in this CodeReview question, and especially the reason why I needed to take this approach.

My solution was to find out how many iterations a delay routine can do in the interval between 2 ticks of the standard 18.2Hz timer. Those ticks are 55 msec apart. Because sometimes measurements can be erratic I only accepted the results if 2 consecutive measurements varied by less than 1%%. Finally I divided the good measurement by 55 to obtain the number of iterations per msec aka SpeedFactor. Hereafter, whenever I wanted to pause the program I multiplied the desired delay expressed in msec by this SpeedFactor and then performed that number of iterations within the delay routine.

The full code:

You can use this which is more universal as the Control class contains the Text property. Also, using the best practice $"".

As commented by @DavidMaze

The original dockerfile used an older version of python which contains an old version of libc6.

And as the dockerfile is used to do a large-scale update of the OS, it may cause issues with an outdated very-low-level system component.

Change the header of the dockerfile from FROM python:3.7-slim-buster as base to FROM python:3.10.0rc2-slim-buster as base which will use the python version with a newer version of libc6

You are assembling your bootloader.asm with nasm -f elf which by default causes it to assemble 32-bit code. Thus you get machine code that doesn't do the right thing when run in 16-bit real mode.

You may be able to work around by putting bits 16 at the top of your bootloader.asm file. But the ELF object file format isn't designed for 16-bit code in the first place, and trying to use it for such a small piece of code is rather absurd. I would instead suggest just building the boot sector with

Following is tested with Python3.6 and with this test odt file;

The problem with this is that you are copying mydirectory into / while your script is located in /usr/src. By default, python only looks for packages in the site-packages directory and the directory where the script is located (the current working directory is used as a fallback in case location of script is not available). So, you should copy your mydirectory in the same directory as your script (which is /usr/src). So, you have two ways to move ahead:

1. Copy mydirectory into /usr/src (and you may make it the working directory).
2. Manipulate the sys.path in your script to include the absolute path to mydirectory.

To do this, simple put this snippet in your script before importing mydirectory

First, you are not suggested to use sudo in docker. You could well design your behavior using USER + gosu.

But, if you insist for some uncontrolled reason, just add next line after you setup normal user:

Originally int 0x15, eax=0xE820 returned a 20-byte structure. This was extended to 24 bytes by a version of ACPI (I think it was ACPI 3.0 but didn't check and could be wrong) that introduced a new "flags" field to the structure.

This code allocates space on the stack for the 20 byte structure (without the extra flags field):