Jump to content











Photo
- - - - -

troubles with booting


  • Please log in to reply
14 replies to this topic

#1 sixcentgeorge

sixcentgeorge

    Frequent Member

  • Advanced user
  • 191 posts
  •  
    France

Posted 22 October 2015 - 06:27 PM

i made a 7 Go vhd for a mainboard asus sabertooth x79 that has 32 Go of ram and three nvidia gtx570 .

 

when i boot using :

 
find --set-root --ignore-floppies /win7x79r.vhd
map --mem /win7x79r.vhd (hd0)
map --hook
root (hd0,0)
chainloader  /bootmgr
boot
 
the display turns black immediately and the computer goes off
 
after reading few pages about memdisk , i found a setting : uppermem 
[that i am not sure how it behaves ]
 
using it like this create a change :
 
find --set-root --ignore-floppies /win7x79r.vhd
uppermem 7340032
map --mem /win7x79r.vhd (hd0)
map --hook
root (hd0,0)
chainloader  /bootmgr
boot

 

grub4dos load file until it reaches 512 Mo then pc screen goes black

 

is it the setting to edit and the parameter ?

 

i would like to use memdisk for testing and see if that works but i am not sure about parameters , any one knows how to launch a win 7 vhd made like in winram topic : http://reboot.pro/to...sk/#entry151868

thanks for help



#2 steve6375

steve6375

    Platinum Member

  • Developer
  • 7078 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 22 October 2015 - 07:06 PM

The 512MB limit makes me think that maybe it is something to do with the memory gap in modern chipsets

http://www.rmprepusb...als/biostestmem


  • sixcentgeorge likes this

#3 tinybit

tinybit

    Gold Member

  • Developer
  • 1158 posts
  •  
    China

Posted 22 October 2015 - 11:33 PM

No, it is not related to the memory fragments. The 32G total RAM should contain a block larger than 7G.

If there were no block large enough, the map would fail with an error message.

Since the map command began to copy image to memory, there must be enough memory for the image.


At grub prompt, enter
 

displaymem

It will report the system memory layout.

 

Also please run each of your menu commands one by one at the grub prompt, and report the output messages.

 

 

If the map command works normally, then the problem has nothing to do with grub4dos. Check your OS boot manager,  drivers for your hardware, and drivers for grub4dos virtual disk(i.e., firadisk or winvblock) and see if they all work fine.

 

Check your map with

map   --status

And, after

map   --hook

check if the files in your virtual drive (hd0) could be accessed normally.

 

If all work fine, then there is nothing wrong with grub4dos.

 

 



#4 sixcentgeorge

sixcentgeorge

    Frequent Member

  • Advanced user
  • 191 posts
  •  
    France

Posted 23 October 2015 - 11:52 AM

i did it and made photos :

 

p1130780.jpg

 

p1130783.jpg

 

 

 

at this prompt i typed the mem copy and computer went off...



#5 steve6375

steve6375

    Platinum Member

  • Developer
  • 7078 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 23 October 2015 - 11:54 AM

Did you try latest version at http://dl.grub4dos.c...a-2015-10-21.7z

Copy \grldr to root of drive to test?



#6 sixcentgeorge

sixcentgeorge

    Frequent Member

  • Advanced user
  • 191 posts
  •  
    France

Posted 23 October 2015 - 12:26 PM

i tested the latest files and have same error

i tested syslinux but had error , may be because its a vhd ?
so i used syslinux+grub.exe and it makes same poweroff after reaching 512 Mo
 
 
i used rammap from sysinternals to show ram:
rammap.jpg


#7 tinybit

tinybit

    Gold Member

  • Developer
  • 1158 posts
  •  
    China

Posted 23 October 2015 - 01:14 PM

Your displaymem shows the memory is enough. You have 28G starting at address of 4G.

Your map --status reported the drive map table is empty. This means you did not create any virtual drives.

So you should firstly
 

map  --mem  /win7x79r.vhd  (hd0)

and then

map  --status
map  --hook
find  --set-root  /bootmgr
root
ls  /
geometry  (hd0)
ls  (hd0,0)/
ls  (hd0,1)/
ls  (hd0,2)/
ls  (hd0,3)/

at last, you load the bootmgr and boot it up:
 

chainloader /bootmgr
boot


#8 sixcentgeorge

sixcentgeorge

    Frequent Member

  • Advanced user
  • 191 posts
  •  
    France

Posted 23 October 2015 - 02:00 PM

when i boot , grub4dos shows free memory as 2751/29952
when i use : map --mem /win7x79r.vhd (hd0)
at 512 Mo the monitor turns black...
 
so i can not enter any other command , i would like to test a setting that would decide where in the ram is copied the file . so i could try at every Go until that crashes


#9 tinybit

tinybit

    Gold Member

  • Developer
  • 1158 posts
  •  
    China

Posted 23 October 2015 - 04:37 PM

I suspect the bios might be broken in an unknown manner. I suppose the bios worked normally at first, but suddenly it crashed and stopped working, even halted or hung up the machine.

Sorry I cannot offer any further help. End my post on this topic.

#10 sixcentgeorge

sixcentgeorge

    Frequent Member

  • Advanced user
  • 191 posts
  •  
    France

Posted 23 October 2015 - 05:55 PM

windows has no troubles , bios is uefi and cpu is lga 2011 1st gen

i suppose you do not care :dubbio: ...if that works or not... :chair: , if you want to progress : you should first admit your product is not good with all pcs instead of saying my old board does not work ...



#11 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 23 October 2015 - 08:40 PM

i suppose you do not care :dubbio: ...if that works or not... :chair: , if you want to progress : you should first admit your product is not good with all pcs instead of saying my old board does not work ...

Noticeably grateful and respectful attitude towards the guy who not only developed large, relevant, vital parts of what grub4dos is now, but also introduced it to us westerners and since some 10 years or so - whenever he can  - tries and helps/assists people having troubles with it, also additionally often acting as "communication officer" between us and our good Chinese friends that bring on the development of grub4dos.
 
If you read ATTENTIVELY the README_GRUB4DOS.txt you might find in it the sentence:

Buggy BIOSes are not supported!!

and

Buggy BIOSes will encounter more and more problems with grub4dos in the future.

and a number of examples of BIOSes that are simply not compatible with grub4dos, to which you have to add the tens of posts and/or bug reports about similar "queer" BIOS behaviours (actually when possible very often fixed in a later release of grub4dos).

It is very possible that you overlooked this hints about the possibly not universal nature of grub4dos, but they were there since day one and they are not to be believed somehow *unexpected* as essentially what grub4dos allows is to make strange, non-standard things to a BIOS (which in itself is a non-standard).

Anyway you can ask your money back, total refund policy has been effective since day one of grub4dos.

Just in case, and I have no alternatives, I can tell you that your old board does not work ADDITIONALLY to telling you that grub4dos is not good for all PC's.
 
:duff:
Wonko
  • tinybit likes this

#12 tinybit

tinybit

    Gold Member

  • Developer
  • 1158 posts
  •  
    China

Posted 23 October 2015 - 11:56 PM

windows has no troubles , bios is uefi and cpu is lga 2011 1st gen
i suppose you do not care :dubbio: ...if that works or not... :chair: , if you want to progress : you should first admit your product is not good with all pcs instead of saying my old board does not work ...

Yes. You care it more than I, certainly. But I also care it, although not as much as you. I am really sorry that I indeed have no capability in helping you to gain a thorough success. I am not skillful enough. I am inept, impuissant, shiftless and talentless. Therefore, I feel that I am guilty, sinful or culpable.

No. It is not my product. It is a product of the community. Many people contributed code to it, or helped the development in some way. And it is possible someday in the future you might contribute to the project. And if anyone use this product or like it, then I think this product thus become the product of his own. So to a certain extent, it is your product. You care the product more than I. I am sorry I do not care it as much as you.

I am sorry I have ended my maintenance of this project. It is now maintained by Chenall and others. Thanks to their hard work.

By posting and reporting and discussion on this board, in fact you already are contributing to this project. Maybe someone could be enlightened from your report and could improve the software in some way. Don't stop. Keep on.

I admit I have almost completely lost interest in the x86 PCs, both in development and in using them. I use ARM android product for now. I am so sorry to say so. But it is true.

#13 sixcentgeorge

sixcentgeorge

    Frequent Member

  • Advanced user
  • 191 posts
  •  
    France

Posted 24 October 2015 - 11:42 AM

The 512MB limit makes me think that maybe it is something to do with the memory gap in modern chipsets

http://www.rmprepusb...als/biostestmem

i tested your tool and result is :

 

 
REM GET AND CHECK MEMORY MAP (INT 15h E820 and E801)  v1.5 2011-08-16 [SSi]
REM ========================================================================
REM BIOS call to Interrupt 15h AX=E801 returns amount of memory (max 4GB).
REM Interrupt 15h AX=E820 returns a map (base address and length of blocks)
REM DOS needs a contiguous block, it cannot cope with 'holes' in the memory
REM DOS typically uses AX=E801, Windows uses AX=E820
REM So the amount of contiguous memory reported by E801 should match or be
REM less than that reported by E820 - if not then DOS programs which use
REM extended memory may crash.
REM Notes: Columns 3 & 4 are rounded down to nearest 1MB only.
REM Ext Attrib=Extended Attributes (bit 0 set if valid value present)
REM T=Type   1=Free 2=Resvd 3=ACPI 4=NVS 5=Unusable 6=Hole else 'Other'
REM ERRORLEVEL=number of errors - 0 is OK, if not 0 then check output.
REM ========================================================================
REM E801 AX=Extended1 - contiguous KB between 1-16MB, max. 15 MB
SET E801_AX=0
REM E801 BX=Extended2 - contiguous 64KB between 16MB-4GB
SET E801_BX=0
REM E801 CX=Configured1 - contiguous KB between 1-16MB, max. 15 MB
SET E801_CX=0
REM E801 DX=Configured2 - contiguous 64KB between 16MB-4GB
SET E801_DX=0
REM ========================================================================
REM BASE ADDRESS (H)     LENGTH (BYTES)   BaseAd(MB) Length(MB) Ext Attrib T
REM ==================   ================ ========== ========== ========== =
REM B=0000000000000000 L=000000000009E800        0MB        0MB E=00000001 1
REM B=000000000009E800 L=0000000000001800        0MB        0MB E=00000001 2
REM B=00000000000E0000 L=0000000000020000        0MB        0MB E=00000001 2
REM B=0000000000100000 L=00000000ABF50000        1MB     2751MB E=00000001 1
REM B=00000000AC050000 L=000000000043E000     2752MB        4MB E=00000001 2
REM B=00000000AC48E000 L=000000000010E000     2756MB        1MB E=00000001 3
REM B=00000000AC59C000 L=000000000021F000     2757MB        2MB E=00000001 4
REM B=00000000AC7BB000 L=0000000000F60000     2759MB       15MB E=00000001 2
REM B=00000000AD71B000 L=0000000000001000     2775MB        0MB E=00000001 1
REM B=00000000AD71C000 L=0000000000086000     2775MB        0MB E=00000001 4
REM B=00000000AD7A2000 L=000000000043B000     2775MB        4MB E=00000001 1
REM B=00000000ADBDD000 L=0000000000417000     2779MB        4MB E=00000001 2
REM B=00000000ADFF4000 L=000000000000C000     2783MB        0MB E=00000001 1
REM B=0000000100000000 L=0000000750000000        0MB     1280MB E=00000001 1
REM B=00000000E0000000 L=0000000010000000     3584MB      256MB E=00000001 2
REM B=00000000FED1C000 L=0000000000004000     4077MB        0MB E=00000001 2
REM B=00000000FF000000 L=0000000001000000     4080MB       16MB E=00000001 2
 
SET E801=16
SET E820_TOTAL=32708
SET E820_CONTIG=2752
REM INT 15h E801 ideally should be same as INT 15h E820 =  ** POSSIBLE FAIL **
SET RMEMTEST_PARAM=1 15
SET E801_64K_COUNT=256
SET E820_64K_COUNT=44037
SET ERRORLEVEL=1
 
 
so it seems not very cool ...
beside that i think that these i7 have a sort of 2x [4x memory controller] , at the physical plan with 2x4 slots of memory , may be the ram is divided in two blocks so getmem/grub4dos should change the memory controller when a block is filled : 512 [or even 256 or 1024] Mo to get a large block of continuous memory . 


#14 sixcentgeorge

sixcentgeorge

    Frequent Member

  • Advanced user
  • 191 posts
  •  
    France

Posted 29 October 2015 - 12:35 AM

I suspect the bios might be broken in an unknown manner. I suppose the bios worked normally at first, but suddenly it crashed and stopped working, even halted or hung up the machine.

Sorry I cannot offer any further help. End my post on this topic.

just to add that the bios is one of the few that can install Mac osX...

http://www.tonymacx8...Pro_Socket_2011

 

so i wonder if anyone can consider it as "broken"...



#15 sixcentgeorge

sixcentgeorge

    Frequent Member

  • Advanced user
  • 191 posts
  •  
    France

Posted 31 October 2015 - 07:45 AM

still no reply for the question...

some says they are happy to have this board because of the BIOS... 

http://www.tonymacx8...tml#post1137911

 

beside that i think i found a bug in grub4dos with memdisk .

i edited my config boot files with this page : http://www.syslinux....dex.php/MEMDISK

 

i used the uppermem parameter , but it seems to be only for grub and its uses is may be not correct in that page 

13.3.37 uppermem
— Command: uppermem kbytes
Force GRUB to assume that only kbytes kilobytes of upper memory are installed. Any system address range maps are discarded. 
Caution: This should be used with great caution, and should only be necessary on some old machines. GRUB's BIOS probe can pick up all ram on all new machines the author has ever heard of. It can also be used for debugging purposes to lie to an OS. 
 
 
so here is the menu.lst i used :
 

 
title Boot  Windows 7 x64 from Image 7168/7168 MB memdisk
uppermem 7340032
find --set-root --ignore-floppies /win7x79r.vhd
kernel /memdisk harddisk=1 c=914 h=255 s=63
initrd /win7x79r.vhd
 
 
title Boot  Windows 7 x64 from Image 7168/7168 MB memdisk raw
uppermem 7340032
find --set-root --ignore-floppies /win7x79r.vhd
kernel /memdisk raw harddisk=1 c=914 h=255 s=63
initrd /memd.img
 
[i made the raw file using a dedicated tool of hddguru ]
here are the screen result :
 
p1130785.jpg

 

 

p1130786.jpg

 

 

so with both grub4dos answers it can not find enough memory...

 

if i use full syslinux boot with config :

 
LABEL m1
    kernel memdisk
    initrd memd.img
    append harddisk=1 c=914 h=255 s=63
 
LABEL v1
    kernel memdisk
    initrd win7x79r.vhd
    append harddisk=1 c=914 h=255 s=63

 

i get error : 

p1130787.jpg

 

meaning some memory troubles...that is weird because hpa has a job at intel...

 

so where is the solution except trying to install win7 in 511 Mo ?  :cold:






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users