630 replies to this topic

[steve6375]

also try adding this line

map --e820cycles=0

 

or try

.isowinvHe0 file extension

 

If you use .isoask in E2B, then it has many alternatives.  .isowinve0 and .isowinvHe0 specifically say 'that gives blank screen on a bad system'.

Edited by steve6375, 01 March 2016 - 10:51 AM.

[imnothing]

Did you try just using one map fd - e.g. fd0 or fd1?

what about setting the number of floppies too?

 

map --floppies=1

or map --floppies=2

 

I tried with just only one map fd but still not work.

about your question, i'm sorry i do not fully understand
 

what about setting the number of floppies too?

 

map --floppies=1

or map --floppies=2

 

can you give me a full menu.lst for testing. tks

 

again, i repost my menu.lst

title MiniXP Wimboot method (Winvblock)
set isoname=/ISO/XP.iso
map %isoname% (0xff)
map --mem /winvblock.gz (fd0)
map --mem /winvblock.gz (fd1)
map --hook
root (0xff)
chainloader (0xff)

title MiniXP WimBoot method with Firadisk
set isoname=/ISO/XP.iso
map --mem (md)0x800+4 (99)
map %isoname% (0xff)
map --mem /firadisk.gz (fd0)
map --mem /firadisk.gz (fd1)
map --hook
write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:%isoname%;\n\0
root (0xff)
chainloader (0xff)

[steve6375]

title MiniXP Wimboot method (Winvblock)
map --e820cycles=0
set isoname=/ISO/XP.iso
map %isoname% (0xff)
map --mem /winvblock.gz (fd0)
map --mem /winvblock.gz (fd1)
map --hook
map --floppies=2
root (0xff)
chainloader (0xff)

experiment with changing number of e820cycles (0,1,2,3) and number of floppies (0,1,2)

Also try using just one winvblock fd (either fd0 or fd1)

[imnothing]

also try adding this line

map --e820cycles=0

 

or try

.isowinvHe0 file extension

 

If you use .isoask in E2B, then it has many alternatives.  .isowinve0 and .isowinvHe0 specifically say 'that gives blank screen on a bad system'.

about map --e820cycles=0

how can i add this line with my menu.lst??

I will try with E2B then report result. tks

[imnothing]

Opps, i'm sorry because you and I post at same time.

Will try your code now.

Tks

[imnothing]

Now ISO was mount (test on HP probook 4420s)

tomorrow i will test on laptop toshiba, it's my friend's computer then fully report.

But i got another problem, after ISO mount to virtual disk, all of .exe file cannot run, seem them corrupt. Sorry i cannot take a screenshot.

[steve6375]

try e820cycles=1 ???

[imnothing]

try e820cycles=1 ???

I tried this but MiniXP hang at "F6 progress bar".

I will try with e820cycles=2 now

[imnothing]

Try with e820cycles=2, ISO mount OK but still data corrupt. .exe, .cmd file not run after click. Some .exe return error 16bit MS-DOS subsystem, the NTVDM CPU has ....

 

Also, you can explain what e820cycles=2 means? tks

[steve6375]

e820cycles

http://reboot.pro/to...les#entry143589

[imnothing]

@Steve, Now ISO was mount successful. Tks

 

Problem come from ISO file. I do not know why ISO not defrag, run wincontig then it say that my USB was defrag. But still my data in ISO file corrupt after ISO mounted. With the same ISO, try to mount with imdisk then run some .exe, .exe run fine.

 

After recreate ISO file by Winbuilder, format USB, copy new XP.ISO file then boot again with your code. Now ISO was mount and can run .exe without error.

 

So how winvblock mount ISO? Why with a same ISO, winvblock mount but data corrupt and imdisk mount OK. Can u explain it? Tks

Edited by congnt92, 01 March 2016 - 03:42 PM.

[steve6375]

Can you clarify please?

What ISO are you testing with?

What menu are you using (what worked and what did not)?

Does the same menu work with ALL systems?

Are both XP and Win7/8/10 ISOs working?

Did you test old 'bad' ISO on all systems and VBox and did it work on all except bad system?

Edited by steve6375, 01 March 2016 - 04:08 PM.

[Wonko the Sane]

Hey peeps, with all due respect , this is becoming (as often happens BTW) a "help me with all problems I have in booting"  kind of thread and is not really-really Firadisk connected (anymore if ever it was).

It would be IMHO a good idea if  congnt92 starts a new thread in 

http://reboot.pro/fo...-boot-anywhere/

or in

http://reboot.pro/forum/66-grub4dos/

 

in order to not make the present Firadisk thread longer and/or hijacking it with unrelated posts.

 

congnt92, really you don't pay a fee to start a new thread, a thread should be related to a given issue/problem/tool, as soon as that particular issue is solved other problems not directly related to the thread title should go in a new, dedicated thread, you have just been explained this general concept on MSFN, 

 

Wonko

 

P.S.: I see that it is of no use whatsoever.

Edited by Wonko the Sane, 01 March 2016 - 04:46 PM.

[imnothing]

Can you clarify please?

What ISO are you testing with?

What menu are you using (what worked and what did not)?

Does the same menu work with ALL systems?

Are both XP and Win7/8/10 ISOs working?

Did you test old 'bad' ISO on all systems and VBox and did it work on all except bad system?

- I test with MiniXP made by Winbuilder, wimboot method.

- Try your hint and it work fine, just add e820cycles=0. All the others lines keep original from my menu.lst

- Oh, with almost computer which i tested, i no need to add e820cycles=0, winvblock work fine. But with my hp probook 4420s, MiniXP hang with blank screen.

- No, i not try with Win7/8/10 ISO, i just test with MiniXP. normally, MiniXP.ISO boot very well. Since I need to mount ISO before boot to desktop to my autorun.cmd create some shortcut from virtual drive then i try with firadisk and winvblock but not work.

- My friend has a toshiba laptop with same problem when using winvblock. I will tell him try your code and report here.

 

---

May you no need to know about my autorun.cmd but i think i need to say about my goal.

 

autorun.cmd will search XP.ISO from ISO folder on root of any partition then mount it by imdisk to virtual drive. then nircmd create some shortcut.

But i found that, with this hardcode on autorun.cmd, my ISO must name with XP.ISO and must be in ISO folder. So i want to use winvblock or firadisk to mount XP.ISO instead of autorun.cmd and i can change name ISO to another name, that say MiniXP.ISO or put on another folder such as WINPE folder ...

But try with winvblock or firadisk MiniXP hang with blank screen as I say above.

After try your code, ISO was mount but data corrupt.

Finally i recreate new ISO and ISO was mount with "perfect" data.

Tks

[steve6375]

My question was  - If you use the new e820cycles=0 menu - does it work on all systems (both good and bad). i.e. can e820cycles=0 safely be added in to all menus without it causing any harm? According to old posts, it may cause harm on some 'good' systems...

[imnothing]

Hey peeps, with all due respect , this is becoming (as often happens BTW) a "help me with all problems I have in booting"  kind of thread and is not really-really Firadisk connected (anymore if ever it was).

It would be IMHO a good idea if  congnt92 starts a new thread in 

http://reboot.pro/fo...-boot-anywhere/

or in

http://reboot.pro/forum/66-grub4dos/

 

in order to not make the present Firadisk thread longer and/or hijacking it with unrelated posts.

 

congnt92, really you don't pay a fee to start a new thread, a thread should be related to a given issue/problem/tool, as soon as that particular issue is solved other problems not directly related to the thread title should go in a new, dedicated thread, you have just been explained this general concept on MSFN, 

 

Wonko

Oh, i'm sorry.

Let me say something.

I boot Minixp.iso fine with this code

 

title MiniXP

set isoname=/ISO/XP.iso
map %isoname% (0xff)
map --hook
root (0xff)
chainloader (0xff)

 

But i need to mount ISO after boot to desktop then try with this code

 

title XP with Firadisk
set isoname=/ISO/XP.iso
map --mem (md)0x800+4 (99)
map --mem /firadisk.img (fd0)
map %isoname% (0xff)
map --hook
write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:%isoname%;\n\0
map --floppies=1
root (0xff) || rootnoverify (0xff)
chainloader (0xff)

 

But after try with this code, miniXP hang with blank screen. So i think just firadisk is the reason and come here to get some advices from you.

 

If it's not right way then I'm sorry. I'll inbox you before post something that I'm not sure.

I'm sorry again.

[imnothing]

My question was  - If you use the new e820cycles=0 menu - does it work on all systems (both good and bad). i.e. can e820cycles=0 safely be added in to all menus without it causing any harm? According to old posts, it may cause harm on some 'good' systems...

 

I'm sorry for my confusing about your question.

With almost computer which i tested, i no need to add e820cycles=0 when boot with winvblock. So i was not try to see what happen if i try this code to boot on these computer. I'll try it now then report.

[imnothing]

Hi Steve, I report my result to your inbox. My problems solved. It's not come from firadisk. I'm sorry Firadisk's author, sorry all member with my unrelated posts.

Please forgive me. Tks

[ramdisk]

ok everything is clear now.

If there is no new driver there is no improvement.

I have been booting all versions off windows in RAM for the last three years.

When will be there a better driver?

every other discussion  is pointless.

https://www.youtube....a4j-mVRQ/videos

[ramdisk]

better driver new driver maybe edit the existing one in c# otherwise no hope.

[ramdisk]

complicated menu.lst that don't help.

[ramdisk]

complicated menu.lst that don't help.

[ramdisk]

complicated menu.lst that don't help.

[steve6375]

The command starts a RAM drive at approx 1MB in RAM:

map --mem (md)0x800+4 (99)

However, it may not work if a large boot.wim + Windows kernel is loaded into memory which uses more than 1MB of memory.

For instance, if you boot to Strelec x86 32-bit WinPE, then the FiraDisk driver loads the ISO and the Desktop icons can be seen.

 

However, if you load the 64-bit WinPE Strelec version, the ISO is not mounted by FiraDisk and no Desktop icons appear - presumably because the memory where the string is written to, is destroyed when the OS is loaded.

 

To fix this, I used

map --mem (md)+4 (99)

This seems to work for both 32-bit and 64-bit WinPE Strelec versions.

 

 

map --mem (md)+4 (99)  on a 5GB Virtual system maps drive (99) at about 3.7GB.

 

If I use --mem --top  then drive (99) starts at 5.78GB (end of memory is at 0x158900000 due to gap in memory map and relocated RAM).

 

--mem --top seems to  work on a 5GB system even when booting a 32-bit WinPE.

 

 

I used grub4dos 0.4.6a 2019-12-30 for testing.

 

[Edit] Note: If testing in Virtual Box 5, I have found that firadisk and winpe x64 does not work if the OS in the VM is set to Windows 64-bit! If you set Linux 64-bit or BSD 64-bit or Other 64-bit, then booting to Strelec 64-bit WinPE + firadisk works - but not if set to 'Windows 64-bit' !!!

Edited by steve6375, 07 January 2020 - 05:13 PM.

[steve6375]

Is there anyway that the scanning of the grub4dos drive to look for [FiraDisk] commands can be made to work when booting from grub2 to a WinPE for both BIOS and UEFI? e.g. scan all of physical memory for signature at certain intervals?

 

At the moment, the code in driver.c FiraDiskDriverStartDetectRAMDrive seems very specific to BIOS\Legacy and GRUB4DOS.

It would be nice to boot Strelec (for instance) using grub2 UEFI and get it to mount the Strelec in the same way that

 

write (99) [FiraDisk]\nStartOptions=disk,vmem=find:%~pnx1,boot;\n\0

 

is used for Grub4DOS?

 

a1ive may be willing to modify grub2 to support this if it is possible.

 

See https://github.com/a.../grub/issues/24