19 replies to this topic

[betrand]

Can WinVBlock mount a Grub4dos-created (md)

and keep it existant in WinXP?

 

I know the WinVb Winvblock 'patch' to hook a named image to protected mode.

But will a (md) work?

 

I know the (md) is still existant in XP, but is there a way to patch during boot?

 

Cheers.

[Wonko the Sane]

Can WinVBlock mount a Grub4dos-created (md)

and keep it existant in WinXP?

 

I know the WinVb 'patch' to hook a named image to protected mode.

But will a (md) work?

 

I know the (md) is still existant in XP, but is there a way to patch during boot?

 

Cheers.

WHICH "patch"?

 

You can re-map a (md) drive to any "virtual drive", there is NO such thing as (md) drive existing in XP.

 

If you have an issue, DESCRIBE what you actually want to do (and the issue you are faced with), NOT the way you think you should do it and the way you think should be the issue solved/worked around.

 

Of course unless you want the usual bunch of (mostly unuseful) guesses (educated or not).

 

How many times will I need to give you links to these? :

http://homepage.ntlw...ard-litany.html

http://homepage.ntlw...red-banana.html

 

 

 

Wonko

[betrand]

Srry, can't 'quote', am using a slow machine where things are weird!

 

Quote:

You can re-map a (md) drive to any "virtual drive", there is NO such thing as (md) drive existant in XP. :woot:

 

I think I mapped said (md) to (hd31).

 

quote:

Which patch?

 

The patch I mean is the way WinVBlock enables an image file (XP.img) of an NT system to remain existant in

 protected mode.

 

I can't remember the code here, but it is the general code from Grub4dos to do that mapping.

x00xp.img is an extract (I may not remember correctly). The file is named. (hd31) is not a name. It doesn't fit how the patch works.

I thought, by the way, that this code was "historical".

 

 

The (md) mapped as (hd31) I know is existant in XP, as it appears in a disk tool.

 

I would like to know how it can be assigned a letter.

 

In any case, I have a possible workaround.

[Wonko the Sane]

In any case, I have a possible workaround.

That's good , as what you posted (even with the added info in your last post) is NOT understandable/ makes not any sense. (usual mumbo-jumbo without head or tail that only someone with ESP may hopefully understand).

 

Wonko

[betrand]

Am I right in thinking

 

map --mem /images/XP.img (hd0)
map --hook
map --rd-size=2048
map --mem (rd)+4 (0x55)
map --hook
write (0x55) #GRUB4DOS\x00v=1\x00XP.img\x00\x80\x00

 

gives info to the WinVBlock driver?

Am I right in thinking it gives the info to enable XP seeing the image?

 

This is based on an image (XP.img).

If I want to give a (md) (mapped as (hdxx))

a drive letter in the OS (XP), how do I do that?

[saddlejib]

42

[Wonko the Sane]

42

 

"Oh freddled gruntbuggly,
Thy micturations are to me
As plurdled gabbleblotchits on a lurgid bee.
Groop, I implore thee, my foonting turlingdromes,
And hooptiously drangle me with crinkly bindlewurdles,
Or I will rend thee in the gobberwarts
With my blurglecruncheon, see if I don't!"

 

 

Wonko

[betrand]

Guys, .

 

Really, a mix of and  .

 

Seriously, I must be tired and hungry, but I am sure it makes sense!

 

Or is there a simple 'thing' I don't know about mapping a (md) to (hd32) and having it letterd in XP?

 

Something, like, you guy know that  the post5 example makes everything in memory from grub4dos

stay in memory? That everything is mapped, even if not lettered?

I mean, my system drive, OK, is mapped as C:, from an image using the stratagem from post5.

 

[Wonko the Sane]

Seriously, I must be tired and hungry, but I am sure it makes sense!

 

Sure it does to you, most probably because you have a whole set of added information and details of what you are actually trying to achieve that you are completely failing to communicate (rest assured, this is the case, noone else but you can make actual sense of the blurbs that you post)

 

But since this is your "posting style" since a lot of time and nothing attempted till now has been successful in convincing you about the objective fact that noone else but you understands what you post and - at the very most - only random or semi-random guesses can be given to you as assistance, it's perfectly OK .

 

Only, since you fail to make sense to other members, you cannot expect that what other people posts should make sense to you.

 

Check "blurb":

http://en.wikipedia.org/wiki/Blurb

 

Wonko 

[betrand]

Yeah, sure, I agree with you.

[IT, systems] It's just something I do sometimes, pick up like that for fun,

and (sometimes) assume people know more / know enough to 'read between the lines'.

Not saying they can't, saying they have also a whole lot of info which doesn't necessarily

pertain to the asked subject.

Thus if I start something, I'll assume people will have bits of info regarding the topic at hand.

Possibly I do a good bit of searching before, so the amount of info can become

difficult to piece together. All the more to explain.

 

For instance, here I assumed someone would know what I mean by grub4dos Winvblock patch.

For me there aren't 42 codes that link Grub4dos and WinVBlock when mentioning mapping to memory.

 

Post5:

 

Am I right in thinking

 

map --mem /images/XP.img (hd0)
map --hook
map --rd-size=2048
map --mem (rd)+4 (0x55)
map --hook
write (0x55) #GRUB4DOS\x00v=1\x00XP.img\x00\x80\x00

 

gives info to the WinVBlock driver?

Am I right in thinking it gives the info to enable XP seeing the image?

 

This is based on an image (XP.img).

If I want to give a (md) (mapped as (hdxx))

a drive letter in the OS (XP), how do I do that?

[Wonko the Sane]

For instance, here I assumed someone would know what I mean by grub4dos Winvblock patch.
For me there aren't 42 codes that link Grub4dos and WinVBlock when mentioning mapping to memory.

Sure, most mind readers would know what you mean, as it is not a "patch", and you called it "WinVb", which may mean Visual Basic under Windows or WinVb.exe (or *whatever*).
 

Post5:
 
Am I right in thinking
 
map --mem /images/XP.img (hd0)
map --hook
map --rd-size=2048
map --mem (rd)+4 (0x55)
map --hook
write (0x55) #GRUB4DOS\x00v=1\x00XP.img\x00\x80\x00
 
gives info to the WinVBlock driver?
Am I right in thinking it gives the info to enable XP seeing the image?
 
This is based on an image (XP.img).
If I want to give a (md) (mapped as (hdxx))
a drive letter in the OS (XP), how do I do that?

Post 7:
"Oh freddled gruntbuggly,
Thy micturations are to me
As plurdled gabbleblotchits on a lurgid bee.
Groop, I implore thee, my foonting turlingdromes,
And hooptiously drangle me with crinkly bindlewurdles,
Or I will rend thee in the gobberwarts
With my blurglecruncheon, see if I don't!"

 

Let's see how long we can go on like this.

 

I will expand on it as follows:

 

"Oh freddled gruntbuggly,
Thy micturitions are to me,
As plurdled gabbleblotchits,
On a lurgid bee,
That mordiously hath bitled out,
Its earted jurtles,
Into a rancid festering confectious inner-sphincter. [drowned out by moaning and screaming]
Now the jurpling slayjid agrocrustles,
Are slurping hagrilly up the axlegrurts,
And living glupules frart and slipulate,
Like jowling meated liverslime,
Groop, I implore thee, my foonting turling dromes,
And hooptiously drangle me,
With crinkly bindlewurdles,
Or else I shall rend thee in the gobberwarts with my blurglecruncheon,
See if I don't."


Wonko

[betrand]

So you saying that a mapped (hd32),

ANY, is seen from within XP,

when 1 only (XP.img) is called by the code eg from post5.

All the other ramdisks stay existant in XP?

 

It is a question, as it something I never experienced.

Only C: (system drive) shown.

 

Mmm, sorry about WinVB, then.

I think, in fact, this was a bit of the big mislead.

[Wonko the Sane]

So you saying that a mapped (hd32),

ANY, is seen from within XP,

when 1 only (XP.img) is called by the code eg from post5.

All the other ramdisks stay existant in XP?

No, I meant that unless you frurtle the gingerbews, you cannot expect the gruntdies to cofwobble properly, let alone trigredumbling the weghnitudes, or - even worse - altroproggling those dewretors.

 

I will try to type the following as slowly as I can:

What you asked makes no sense whatsoever unless you provide the EXACT details of what you are trying to achieve (GOAL, NOT means) and a COMPLETE, EXHAUSTIVE description of the CONTEXT in which you are asking the question.

 

Wonko

[betrand]

map --mem /images/animg.img (hd32)

map --hook

map --mem /images/XP.img (hd0)
map --hook
map --rd-size=2048
map --mem (rd)+4 (0x55)
map --hook
write (0x55) #GRUB4DOS\x00v=1\x00XP.img\x00\x80\x00
root (hd0,0)

chainloader /ntldr

 

Boot to XP.

 

Is 'animg.img' supposed to appear as a drive in XP, by the use of the Winvblock code?

Maybe I always had supposed only the xp.img would.

 

Also, to go further, does a (md) mapped as (hd33)

and formatted with (the Chenall Fat tool) fat mkfs (hd33),

when added to the above code, does it appear as a drive

in XP?
 

[Wonko the Sane]

Let's try another approach.

Is 'animg.img' supposed to appear as a drive in XP, by the use of the Winvblock code?

No.

Maybe I always had supposed only the xp.img would.

Maybe then you always supposed correctly.

 

Also, to go further, does a (md) mapped as (hd33)
and formatted with (the Chenall Fat tool) fat mkfs (hd33),
when added to the above code, does it appear as a drive
in XP?

No.

"Magic" is not part of the way devices are mounted in any NT based system.
A device needs a driver.
The driver needs to know that the device - virtual or real - exists and - one way or the other - connect to it.
Each and every device accessed in "real mode" won't survive the switch to "protected mode" (very early in the booting process).
A grub4dos mapped device is mapped in "real mode".


Wonko

[betrand]

Re-reading this.

Never came back to it.

At the time I had wanted someone to confirm what I was implying was wrong.

To exclude the fact I might have missed some topic about that.

Wonko did that accordingly.

 

(The last two posts sum-up the discussion)(Previous posts are "fun")

A normal XP system won't do as I am trying to imply in the last two posts.

An Xpcli-MiniXP might do that if loaded to ram.

Try mapping a (fd0) @ boot. Have the right drivers in XP system (floppy driver).

You might even want to try with a disk viewer (Hxd for e.g.).

 

-Is it the fact Minlogon is used?

-Is it similar to XP install Phase 1 and Phase 2 (install from Ram-iso, using a random fd image to "hook" the driver)?

[Wonko the Sane]

RE-reading this, I see little fun in the posts, only a very sad evidence of communication problems that more one year later have not in any way changed, you insist on posting confusing, partial blurbs and I continue to completely fail to understand what (the heck) do you mean/want.

 

Maybe when you will stop attempting to imply anything and just plainly describe, possibly in detail and explicitrly what you are after, there will be a chance of having a more normal communication.

 

Anyway a relatively new example from https://www.reddit.c...onpoetrycircle/ :

 

"A lurgid bee" is plurdled gabbleblotchits narf

That bruntcuntnuples in liverslime

And belches the bindlewurdles from flopsokitus

And festers as putrid should.

 

 

Wonko

[betrand]

Post 14. I asked a question.

Post 15. I got the answer I was expecting.

Post 16. I say that I asked a question to get the answer.

 

Post 16 and 18. I explain that by observation the answer to post 14 is not necessarily NO.

Post 18.

I have observed that by using the .lst commands as in post 14 (or similar), I can see a drive listed.

All the more, if one maps a floppy image as HDx,x, becomes appended an MBR and Partition table  to the drive (device)

(as is the working of Grub4Dos, re-creating a MBR in certain circumstances), which can be useful even as a POC, or better a studying tool.

[Wonko the Sane]

Well you asked questions that I could not understand as much as you could not understand the replies provided.

 

And since you decided to already expect some answers, refusing - after having been asked to - to provide the meaningful missing info, the thread provided nothing really of use to you and some frustration for the one that attempted (vainly) to help you.

 

Too bad, I could have provided links to some possibly useful posts, like:

http://reboot.pro/to...block/?p=120942

or

http://reboot.pro/to...e-2#entry121456

http://reboot.pro/to...block/?p=101891

 

instead of providing Vogon's poetry...

 

Wonko

[betrand]

some frustration for the one that attempted (vainly) to help you.

Arh! Sorry man!

To be fair we settled the affair of mis-judged wording at the time when It was put forward Winvb could be misconstrued as VisualBasic.

And the use of "patch" instead of "code".

 

Thanks for the links provided, will read.