Jump to content

galaxstar

Member
  • Posts

    6
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Guadeloupe

About galaxstar

galaxstar's Achievements

0

Reputation

  1. @ Mr Snrub : Vista : no this netbook came with XP preinstalled. This behavior started with the first installation of win7 (beta). It's an atom-based netbook that originally came with 1gb of ram (2 now) so i didn't feel like putting vista on it. It's a medion akoya e1210 which is more or less a rebranded msi wind. Sleep and resume : works great. Bios : i've updated it once and that was before installing windows 7. Not much in terms of parameters. sata disk (no raid of coursel) and ahci enabled. @cluberti 7 seconds timeout : following forum advice i've tried changing the value to 0 and since it didn't work i've set it again to 7 in case i would find a way to trigger the timer later. usefirmwarepcisettings : i don't have this on my other win7 machine. I wonder if i should (and how) change this value.
  2. Here goes : Windows Boot Manager -------------------- identifier {bootmgr} device partition=C: description Windows Boot Manager locale en-US inherit {globalsettings} default {current} resumeobject {453fa0e2-545a-11de-9f35-b853fce87737} displayorder {current} toolsdisplayorder {memdiag} timeout 7 Windows Boot Loader ------------------- identifier {current} device partition=C: path \Windows\system32\winload.exe description Windows 7 locale en-US inherit {bootloadersettings} recoverysequence {453fa0e4-545a-11de-9f35-b853fce87737} recoveryenabled Yes osdevice partition=C: systemroot \Windows resumeobject {453fa0e2-545a-11de-9f35-b853fce87737} nx OptIn usefirmwarepcisettings No
  3. I typed the bcdedit command but it didn't change anything. The Windows Boot Manager already had {current} as default.
  4. bcdedit at command prompt gives me 2 "entries" a Windows Boot Manager category with identifier : {bootmgr} and timeout 7 (i've changed it from 30 to see what would happen) a Windows Boot Loader category with identifier : {current} But i guess it counts as one entry . Btw my win7 x64 system has almost exactly thesame bcdedit entry (except timeout 30) and minus the usefirmwarepcisettings option (=no on the netbook).
  5. Sadly no, eyeball. I forgot to mention that the boot manager menu does not display a timer. I've tried changing the default timeout using BCDedit but again since this menu doesn't seem to use timemouts it made no difference. Moreover on my other pc the option you mention is at 30 seconds and yet i don't get a boot menu at startup. Really puzzling Thanks for your suggestion anyway
  6. I've been having this problem this problem since the beta : I just installed windows 7 RC x86 on my netbook (medion akoya e1210 2gb ram 80gb hd). I only have one partition (i did the manual procedure to avoid the extra system partition) taking up the whole HD (ie fresh install on a newly and completely formatted hd). Yet at startup, windows 7 insists on showing a boot manager with only one choice of course. I had the same problem with the beta (only i had the 200 mb system partition as well but no other os installed). Why am i getting this boot manager menu at startup and most importantly how to get rid of it ? Thanks Note : I've also installed windows 7 (x64) on my main pc with several partitions present but no other os and i don't have this issue.
×
×
  • Create New...