Jump to content











Photo
- - - - -

grub4dos for UEFI map is loading vhd into memory without mem switch


  • Please log in to reply
5 replies to this topic

#1 favorinus

favorinus

    Member

  • Members
  • 38 posts
  •  
    Argentina

Posted 01 November 2022 - 12:38 AM

grub4dos for UEFI  map is loading vhd into memory without mem switch

 

Hi everyone,

 

again something strange. I managed my vhd to chainload and boot from memory,

but now it's imposible to boot from vhd normally.. it's loading always first into memory.

 

find --set-root /win10_4125.vhd

map /win10_4125.vhd (hd)

 

now it's starting to load the whole vhd file into memory .. like there is the --mem switch

 

why and how can I prevent that ?

 

 

 

 

 



#2 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 01 November 2022 - 08:38 AM

Try using Defraggler to make the vhd file contiguous



#3 favorinus

favorinus

    Member

  • Members
  • 38 posts
  •  
    Argentina

Posted 01 November 2022 - 04:01 PM

thanks, that solved it.



#4 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 16066 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 02 November 2022 - 01:07 PM

So, if I get it right, grub4dos (for UEFI) if it detects that the file is fragmented, autoloads it in memory? :w00t: :frusty:

 

Not to seem the usual grumpy, old, bastard (that I actually am, BTW), but it seems to me the perfect way to crash (after a looong delay) when there is not enough RAM available and with slow media.

 

Can the behaviour be disabled somehow?

 

:duff:

Wonko



#5 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 02 November 2022 - 01:41 PM

It may be that the file was too highly fragmented and map could not cope so it defaulted to load it into memory ???



#6 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 16066 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 03 November 2022 - 09:20 AM

It may be that the file was too highly fragmented and map could not cope so it defaulted to load it into memory ???

Maybe, but as said, if this behaviour is confirmed, it is likely to produce delays and crashes, and of course it is more likely that a file is fragmented if it is a large one.

 

With smaller ones (that fit in memory) the behaviour (if confirmed) would introduce the delay for loading into mem, and then the *whatever* might work, but not as intenteded (filedisk) but rather as the grub4dos arbitrarily decided (memdisk).

 

It doesn't seem to me like a desirable feature.

 

:duff:

Wonko






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users