Hi,
You are still vey confused.
, This is driving me crazy! Each time I paste something in codebox, it comes out jumbled.
When one map --mem +
?
![:dubbio:](http://reboot.pro/public/style_emoticons/default/dubbio.gif)
Should've been
map --mem (hd0) + (hd1) see next post.
and
[s]map --mem (hd0) + (hd1)[/s]
see next post. Is that possible?
(and is it going to come out as I typed?) no.
@Wonko, yeah, source-target, I know. Thanks for wanting to clear it though. The above I hope explains what I meant.
@Cdob,
Idea:
create a disk in RAM, format as FAT, copy files to this disk.
No, I don't have a working example myself.
Yeah, I was going to ask, at some point, if creating an empty ramdrive with grub4dos was possible -out of the box.
Thanks, & thanks for the links. I'd already seen the Fat copy tool,
Chenall's copy/Fat, I think can only copy to root of drive. I assume it can copy a file from its path.
Otherwise, I could have the folder zipped, copy the zip to a map --mem (offsetxxx) drive, and unzip to another ram-drive.
Zip being more 'common' than iso (in everyday use).
No, I don't have a working example myself.
![;)](http://reboot.pro/public/style_emoticons/default/wink.png)
Dpms
, always good to see an unknown Iso.
@wonko,
--in-situ
, mhm! interesting. Interesting name, mostly, for me. "Sounds cool!"
SO. Do you guys know if it's possible to create a blank formatted (or not) drive out of the box with Grub4dos?
By saying map this area of memory as say, floppy, CHS, FAT FS.
But the main idea being.For the test:
1 container drive image. (hd-like)
1 Dos boot floppy
1 bootsector and FAT(.bin, .file, .whatever) [edit: of a second floppy]
After that the files of a second floppy (whose bootsector is the latter) are on the main drive image. The files are in the same order, an Hex-copy.
The floppy images must be same FS as main drive, to, I assume, avoid overlapping FSs.
The FAT of the main drive would list the files of second floppy, as well as a Bootsector and fat. bin.
The files of the floppy are now accessible from windows.
Grub4dos would have to map the offsets from bootsectorfat.bin to end of last file (on main drive), and map thae length as a drive.
Therefore we have a bs, a FAT, and files. In RAM.
It looks more like a proof of concept. Might be useful.
Fun.
Ok, see yas.