1 MB hard drive (both a and b)

[johntim-winlinuxfan]

Version: ccb5e1c (Sep 20, 2025 11:09)
Browser/OS Chrome Version 126.0.6478.222 (Official Build) (64-bit), ChromeOS

i have no words whats happening so basically i tried doing a 200 megabyte hard drive (note : this bug happened on this update before it was fine) and it keeps saying its 1 megabyte now it had only 1 directory and it was dos 7.10

[johntim-winlinuxfan]

(note 2 : poweriso was taking ages so i just made an smaller partition also i need more than 220 mb so i made an img file with 256mb only because storage problem so thats why i use the built in empty disk (BEFORE the bug))

[FunnyCorgi]

I'm having the same problem: setting any size for any drive makes any guest read it as 1mb and the image export also reads at 1mb.
I think the culprit is how the hard disk size is set: if you look in the url the byte size of the disk is incorrect:
100 MB is 104857600 bytes
V86 writes into the url 1048576 bytes(1mb) which is less than the target no matter what you put in(unless you put in less than one megabyte).
FIRST EDIT:
I think something in the following where it sets the size doesn't work correctly:

const hda_empty_size = +$("hda_empty_size")?.value;
        if(hda_empty_size)
        {
            const size = Math.min(1, Math.max(MAX_ARRAY_BUFFER_SIZE_MB, hda_empty_size)) * 1024 * 1024;
            settings.hda = { buffer: new ArrayBuffer(size) };
            new_query_args.set("hda.empty", String(size));
        }

Though this code seems like it should work just fine. Since it is able to correctly access the size value as far as I can tell, the only reason I would see this failing is if:

Math.max(MAX_ARRAY_BUFFER_SIZE_MB, hda_empty_size)

returned a value greater than one(which it will for user provided sizes) and then math.min would take the value of the 1mb minimum then multiply to get the result size in bytes.

EDIT: I realized that it's a little hard to understand what I wrote here: basically the math.min and math.max appear to be evaluated in the wrong order and the evaluation currently goes as follows:

1. v86 decides which is greater: MAX_ARRAY_BUFFER_SIZE_MB or the hda_empty_size in MB provided by the user - that is then passed to math.min for the second parameter.
2. math.min looks at the values and chooses 1 because it is less than what math.max returned(regardless of user input - if they inputted 2048 MB that would be chosen as it is greater but if less than 2000 it will still return a value of 2000) and then that final value of 1 is multiplied and then passed to the url argument hda.empty
3. the value of hda.empty is then used to create the hard disk - which is now set to 1MB.

END EDIT
I think a fix for this would be to instead use:

            const size = Math.max(1, Math.min(MAX_ARRAY_BUFFER_SIZE_MB, hda_empty_size)) * 1024 * 1024;

I'll go ahead and begin drafting a PR to resolve this issue.