[kDn]

Maybe this can be usefull:

Quote

timeout 30
default /default

# After execute this commands -> usb-drive always (hd0)
# Nested calls like configfile /menu.lst is ignored
errorcheck off
# Try to supress unneeded messages
debug off
serial --unit=0 --speed=115200
terminal --silent serial
# Clearing mappings...
checkrange 0x00,0x01 read 0x8280 && map --unmap=0:0xff
checkrange 0x00,0x01 read 0x8280 && map --floppies=2
# Shifts (hd) devices (4 hdd by default)
checkrange 0x00,0x01 read 0x8280 && map (hd3) (hd4)
checkrange 0x00,0x01 read 0x8280 && map (hd2) (hd3)
checkrange 0x00,0x01 read 0x8280 && map (hd1) (hd2)
checkrange 0x00,0x01 read 0x8280 && map (hd0) (hd1)
# Maybe USB-ZIP like (fd1) or (fd0) ?
checkrange 0x01 read 0x8280 && map (fd1) (hd0)
checkrange 0x00 read 0x8280 && map (fd0) (hd0)
checkrange 0x00 read 0x8280 && map (fd0) (fd1)
checkrange 0x00 read 0x8280 && map (fd1) (fd0)
# Mapping changes
checkrange 0x00,0x01 read 0x8280 && map --hook
checkrange 0x00,0x01 read 0x8280 && rootnoverify (hd0,0)
# Try to hide unnecessary floppies
ls (fd1)/menu.lst && map --floppies=1
geometry (fd0) || map --floppies=0
# Enable messages output
terminal console
terminal graphics
debug normal
errorcheck on

gfxmenu /boot/_splash/message.gz
configfile /boot/_lst/2menu_en.lst

title
...

cdob, on Oct 6 2009, 09:07 PM, said:

@kDn
Another idea:
Imagine there exist a file \I386\RAMBOOT.TXT

123456\nsome text

123456 refers to RAM load sectors count.
Grub4dos menu.lst dosn't contain sector numbers by default.
Do you have a idea to boot grub4dos, read RAMBOOT.TXT at grub4dos and call

map --mem (0xFE)+123456 (0xFF)

cdob
I dont know good solution, or universal way...
But I try thinking about it

This post has been edited by kDn: 06 October 2009 - 04:03 PM

[Siginet]

You know what... I feel so dumb. The unattended answer files I was using were blank. LOL! So I guess this just hasn't been my week. I've been troubleshooting creating a USB Bootable RAM ISO all week and most of my issues were my own fault. If someone wants to remove my useless posts in this thread it's fine by me. I feel so embarressed that I'd even let the simplest things like this slide by me. LOL! This is what I get for being out of the loop for so long. Guess it's time for me to start coding something again.

[Siginet]

Here's a few questions I have:

1. If I loaded an iso to ram... and then loaded a second iso to RAM again... would existing files be overwritten?

The reason I ask is this.

We know that all different editions of XP Pro use the same exact files... except a small amount of files are different.
If we could load an ISO of XP Pro Corp to RAM... and then load another small ISO on top of it which only contained the different files for XP Pro OEM... would it actually change the ram install into XP Pro OEM?

2. Also... can I mount an ISO onto a HD instead of into RAM?

for instance if we could... then we could create a normal USB XP install stick with XP Pro Corp...
and then mount a small iso with the different files for XP Pro OEM conversion. Which would overwrite the ones on the hd.

3. And my last question...

Is there any way possible to use a cd/dvd... and somehow mount that small iso into RAM in a way that would map those files to trick windows setup into thinking the files in ram where the files on the disk. Since CD/DVD ROM's are not writeable... this would be really cool if we could utalize the memory to make it look like the drive is writeable. I doubt this is possible right now. But it would be something cool to think about for those who have created drivers like this which allows us to do things we normally couldn't do in the past.

[jaclaz]

Siginet, on Oct 7 2009, 01:23 AM, said:

I feel so embarressed that I'd even let the simplest things like this slide by me. LOL!

Well, NO, it doesn't work this way.
What would we have (when old and retired, and forgetful ) to point you to, which reference would we have for "You remember that time you completely messed up...."

Siginet, on Oct 7 2009, 02:27 AM, said:

1. If I loaded an iso to ram... and then loaded a second iso to RAM again... would existing files be overwritten?

NO. separate addresses are used.

Siginet, on Oct 7 2009, 02:27 AM, said:

2. Also... can I mount an ISO onto a HD instead of into RAM?

NO.
You cannot mount an ISO to a HD.
BUT, hopefully, in the future we may be able to load directly (NOT in ram) a HD image (.ima/.img) as HD.
This is a requsted feature that will probably be added to Firadisk or to WinVblock:
http://www.boot-land...?showtopic=8168
http://www.boot-land.net/forums/index.php?...=8168&st=11
http://www.boot-land.net/forums/index.php?...=8804&st=77

For the record there is a "filedisk" driver that should be able to do that as it has no size limits and is a real miniport one:
http://www.boot-land...?showtopic=8468
(it seems like there are no takers for experimenting with this one)

Siginet, on Oct 7 2009, 02:27 AM, said:

for instance if we could... then we could create a normal USB XP install stick with XP Pro Corp...
and then mount a small iso with the different files for XP Pro OEM conversion. Which would overwrite the ones on the hd.

There could be a way through using graft-points (sort of hardlinks) in the making of the .iso.

Siginet, on Oct 7 2009, 02:27 AM, said:

3. And my last question...

Is there any way possible to use a cd/dvd... and somehow mount that small iso into RAM in a way that would map those files to trick windows setup into thinking the files in ram where the files on the disk. Since CD/DVD ROM's are not writeable... this would be really cool if we could utalize the memory to make it look like the drive is writeable. I doubt this is possible right now. But it would be something cool to think about for those who have created drivers like this which allows us to do things we normally couldn't do in the past.

Sure, Firadisk (and grub4dos) can load HD images allright (actually it is what it is intended and used for) but you will have to deal to same "queer" behaviour theat were found (and solved) for the "normal" Install XPfrom USB.

jaclaz

[kDn]

cdob
What you think about that?

title Test generating menu
#(fd1) optional, required at some BIOS
#map --mem /Boot/XP_INST.gz (fd1)
map --mem /Boot/XP_INST.gz (fd0)
ls /Boot/XP_RAM.ISO || find --set-root /Boot/XP_RAM.ISO
map /Boot/XP_RAM.ISO (0xFE)
map (hd0) (hd1)
map (hd1) (hd0)
map --hook
# EMPTY512.LST content 512 spaces
write --offset=0x00 (fd0)/EMPTY512.LST default 0\n######
write --offset=0x10 (fd0)/EMPTY512.LST \ntimeout 0\n\n##
write --offset=0x20 (fd0)/EMPTY512.LST \ntitle TOFF\n###
write --offset=0x30 (fd0)/EMPTY512.LST \nmap --mem (0xFE)					  (0xFF)\n#
write --offset=0x60 (fd0)/EMPTY512.LST \nmap --hook\n###
write --offset=0x70 (fd0)/EMPTY512.LST \nmap --unmap=0xFE\n#####
write --offset=0x88 (fd0)/EMPTY512.LST \nchainloader (0xFF)/I386/SETUPLDR.BIN\n#
# RAMBOOT.TXT content like "+12345667" without quotes
dd if=(0xfe)/RAMBOOT.TXT of=(fd0)/EMPTY512.LST seek=0x44 count=0x0A
configfile (fd0)/EMPTY512.LST

[maanu]

reply to post#70

can you please explain the grub4dos entries in code box plz ?

[kDn]

maanu, on Oct 7 2009, 09:50 PM, said:

reply to post#70

can you please explain the grub4dos entries in code box plz ?

This an idea to construct menu entry on-the-fly... Look to the post #59 or #66

This post has been edited by kDn: 07 October 2009 - 01:21 PM

[cdob]

@kDn
Thanks, I like the idea.
The (fd0)/EMPTY512.LST offers a universal solution.
EMPTY512.LST settings can be adjusted to special needs.
Have to do some tests. There are different approaches to create RAMBOOT.TXT.
Maybe I add a ramload.lst to ISO image too. ramload.lst offer a basic setting with swap hd0 hd1 and without map.
Haven't made a final decision so far.

@Siginet
I don't know a reliable solution with two single ISO files.
Remember grub4dos dd is more a hex editor. You can copy sectors, but file system is not adjusted.
You may mount a second ISO file, and dd oembios.cat to RAM ISO.
Given different oembios.cat file sizes results are interesting. Try and report.

A multi session CD (or fake multi session as growisofs) may get a approach too.
dd file system parts to RAM. However this is rather difficult at two single ISO images.

A multi boot ISO file gives reliable results.

To 3: It should be possible to load a small iso into RAM (textmode boot files, about 10mb), mount the big ISO file to a virtual CD drive and continue installation.
Setup search all CD drives for source files, does work at U3 fake CD drive. No need to add a special search.
I don't know a setupldr.bin textmode driver to mount the big ISO file.

[cdob]

kDn, on Oct 7 2009, 03:08 AM, said:

What you think about that?

I created two approaches finally:
mkISO_RAMload_sort.cmd creates a grub4dos menu RAMboot.lst.
Example:

Quote

#183934 #

timeout 1

title Install Windows - no map
map --mem (0xFE)+183934 (0xFF)
map --hook
chainloader (0xFF)/I386/SETUPLDR.BIN

Recognice the first line, this contain the sector numbers.

The RAMboot.lst is called from main menu.lst.

First approach: configfile, use preconfigured RAMboot.lst.

 
title Loading XP RAM install - swap hd0 hd1 \n loading N sectors configfile RAMBOOT.LST
ls /Inst/XP_RAM.ISO || find --set-root /Inst/XP_RAM.ISO
map --mem /Inst/XP_INST.IMA (fd0)
map /Inst/XP_RAM.ISO (0xFE)
map (hd0) (hd1)
map (hd1) (hd0)
map --hook
map --unmap=0xFE
configfile (0xFE)/I386/RAMBOOT.LST

title Loading XP RAM install - no map hdN \n loading N sectors configfile RAMBOOT.LST
ls /Inst/XP_RAM.ISO || find --set-root /Inst/XP_RAM.ISO
map --mem /Inst/XP_INST.IMA (fd0)
map /Inst/XP_RAM.ISO (0xFE)
map --hook
map --unmap=0xFE
configfile (0xFE)/I386/RAMBOOT.LST 

Second approach: universal solution, read sectors from RAMboot.lst

 
title Loading XP RAM install - no map hdN \n loading N sectors from RAMBOOT.LST
ls /Inst/XP_RAM.ISO || find --set-root /Inst/XP_RAM.ISO
map --mem /Inst/XP_INST.IMA (fd0)
#optional, (fd1) required at some BIOS
#map --mem /Inst/XP_INST.IMA (fd1)
map /Inst/XP_RAM.ISO (0xFE)
map (hd0) (hd1)
map (hd1) (hd0)
map --hook
#kDn [url="http://www.msfn.org/board/index.php?s=&showtopic=137714&view=findpost&p=886626"]http://www.msfn.org/board/index.php?s=&...st&p=886626[/url]
# EMPTY512.LST content 512 spaces
write --offset=0x00 (fd0)/setup/EMPTY512.LST default 0\n
write --offset=0x10 (fd0)/setup/EMPTY512.LST \ntimeout 0\n\n
write --offset=0x20 (fd0)/setup/EMPTY512.LST \ntitle RAM load\n
write --offset=0x30 (fd0)/setup/EMPTY512.LST \nmap --mem (0xFE)+        (0xFF)\n
write --offset=0x52 (fd0)/setup/EMPTY512.LST \nmap --hook\n
write --offset=0x60 (fd0)/setup/EMPTY512.LST \nmap --unmap=0xFE\n
write --offset=0x72 (fd0)/setup/EMPTY512.LST \nchainloader (0xFF)/I386/SETUPLDR.BIN\n
# RAMBOOT.* content like "#123456" without quotes
dd if=(0xfe)/I386/RAMBOOT.LST of=(fd0)/setup/EMPTY512.LST skip=1 seek=0x42 bs=1 count=0x07
#cat (fd0)/setup/EMPTY512.LST
configfile (fd0)/setup/EMPTY512.LST 

EMPTY512.LST is included in XP_INST_v04.7z, attached to first post.

[kDn]

cdob
All works pretty good. Thanks a lot for yours work.

[kDn]

cdob
Another some little changes maded in setup script (SETUP.CMD) for more correct work, compare and confirm its please.

Attached File(s)

•  SETUP.7z (3.11K)
  Number of downloads: 77

[kDn]

On some systems USB do not initialized properly, this can be fixed like that:

Quote

title Testing Install Windows XP from ISO on USB-HDD
ls /boot/XP_RAM.ISO || find --set-root /boot/XP_RAM.ISO
map --mem /boot/XP_INST.gz (fd0)
#(fd1) optional, required at some BIOS
map /boot/XP_RAM.ISO (0xFE)
# if start from HDD-device, than remaping hd0<->hd1
checkrange 0x80 read 0x8280 && map (hd0) (hd1)
checkrange 0x80 read 0x8280 && map (hd1) (hd0)
map --hook
write --offset=0 (fd0)/setup/ISOimage.ini \\boot\\XP_RAM.ISO\n;\n;\n;
map --unmap=0xFE
# uncomment line ;setup, fixBoot.USB
write --offset=1782 (fd0)/TXTSETUP.OEM dll = setup, fixBoot.USB\r\n;
configfile (0xFE)/I386/RAMBOOT.LST

[kDn]

If you want to use multiple unattended-mode installation, you may do some simple steps:
1. Create file WINNT.SIF with 65536 space chars (0x20), and put it in the root of floppy image (XP_INST.IMA)
2. Use menu item like that:

Quote

title Testing WINNT.SIF
ls /Inst/XP_RAM.ISO || find --set-root /Inst/XP_RAM.ISO
map --mem /boot/XP_INST.IMA (fd0)
#(fd1) optional, required at some BIOS
#map --mem /boot/XP_INSTF.IMA (fd1)
map /Inst/XP_RAM.ISO (0xFE)
map --hook
# Uncomment if not work while installing from USB
#write --offset=1782 (fd0)/TXTSETUP.OEM dll = setup, fixBoot.USB\r\n;
# Use WINNT.SIF from ISO
#dd if=(0xFE)/I386/WINNT.SIF of=(fd0)/WINNT.SIF
# Use WINNT.SIF from /boot/TEST.SIF
dd if=()/boot/TEST.SIF of=(fd0)/WINNT.SIF
# or comment all lines whis dd command for install in manual (non unattended) mode
checkrange 0x80 read 0x8280 && map (hd0) (hd1)
checkrange 0x80 read 0x8280 && map (hd1) (hd0)
map --hook
map --unmap=0xFE
configfile (0xFE)/I386/RAMBOOT.LST

[robekia]

Excellent work, i appreciate that effort so much.

I used ISO file for windows XPSP3 tweaked with NLite.

i tested this using Memory stick 8GB/1GB/4GB on AsusEee --> worked fine.
i tested this using Memory stick 8GB/1GB/4GB on HP530 --> worked fine.
i tested this using Memory stick 8GB/1GB/4GB on HP500 --> worked fine.
i tested this using Memory stick 8GB/1GB/4GB on Acer1640 --> worked fine.

but when i tested this using the builtin/internal Card Reader with 4GB on ACER5738 with the following steps:
1- Format 4GB SD memory with HPTools.
2- install Grub 0.4.4
3- Booted from Grub
4- Start the text mode windows setup till i reach the step for choosing the partition to install windows --> actually this step never reached and blank screen appear instead.
5- i tried another ISO that worked for all other Laptobs and the same result
6- i tried with an ISO for pure windows (Not tweaked) with the same results.
7- i got maaaaaaaaaaaaaaaaaaaaaaaaaad with this.


any solution gents?

[cdob]

kDn, on Oct 13 2009, 01:36 AM, said:

Another some little changes maded in setup script (SETUP.CMD) for more correct work, compare and confirm its please.

Sorry late answer, got distracted. Some vacation preparations: I'm offline next december.

Diff are spaces in most cases

 
$ diff setup.cmd setup.cmd.edited

44c44
< echo presetup log %date% %time% > presetup.log
---
> for %%a in (presetup.log) do if not exist %%a echo presetup log %date% %time% > presetup.log
49c49
< for %%a in (reg.exe) do if not exist %%a echo Error: missing file: %%a >>presetup.log
---
> for %%a in (reg.exe) do if not exist %%a echo Error: missing file: %%a >> presetup.log
53c53
<   echo presetup fixDrive.USB > presetup.log
---
>   echo presetup fixDrive.USB >> presetup.log
58c58
<   if /I not %SystemDrive%.==C: echo setup SystemDrive %SystemDrive% >>presetup.log
---
>   if /I not %SystemDrive%.==C: echo setup SystemDrive %SystemDrive% >> presetup.log
62,63c62,65
<   if exist c:\Inst\XP_*.ISO set reassign=true
<   if exist c:\Inst\2003*.ISO set reassign=true
---
>   
>   set ISO_file_search=\Inst\XP_RAM.ISO
>   if exist ISOimage.ini for /f "eol=;" %%a in (ISOimage.ini) do if not %%a.==. set ISO_file_search=%%a
>   if exist c:%ISO_file_search% set reassign=true
68c70
<     echo reg delete MountedDevices \DosDevices\C: and \DosDevices\%SystemDrive%>> presetup.log
---
>     echo reg delete MountedDevices \DosDevices\C: and \DosDevices\%SystemDrive% >> presetup.log
85c87
<   echo presetup fixBoot.USB > presetup.log
---
>   echo presetup fixBoot.USB >> presetup.log
106c108
<  if not exist %%a echo Error: missing file: %%a >>presetup.log)
---
>  if not exist %%a echo Error: missing file: %%a >> presetup.log)
129c131
< if defined sourcepath (echo sourcepath %sourcepath%)>>presetup.log
---
> if defined sourcepath (echo sourcepath %sourcepath%) >> presetup.log
143c145
<     echo search ISO file "%%i:%%j">>presetup.log
---
>     echo search ISO file "%%i:%%j" >> presetup.log
149c151
< (echo Error: no ISO file found &echo.)>>presetup.log
---
> (echo Error: no ISO file found &echo.) >> presetup.log
153c155
<   echo found ISOfile %ISOfile%>>presetup.log
---
>   echo found ISOfile %ISOfile% >> presetup.log
156c158
<   echo mount ISOfile %ISOfile% >>presetup.log
---
>   echo mount ISOfile %ISOfile% >> presetup.log
165c167
<   echo.>>presetup.log
---
>   echo. >> presetup.log
167c169
<   echo.>>presetup.log
---
>   echo. >> presetup.log
171c173
<     (echo. &echo mount ISOfile V:\XP_RAM.ISO) >>presetup.log
---
>     (echo. &echo mount ISOfile V:\XP_RAM.ISO) >> presetup.log
174c176
<     echo.>>presetup.log
---
>     echo. >> presetup.log
176c178
<     echo.>>presetup.log
---
>     echo. >> presetup.log
205c207
<   echo call presetup.cmd >>presetup.log
---
>   echo call presetup.cmd >> presetup.log
208c210
<   echo end presetup.cmd >>presetup.log
---
>   echo end presetup.cmd >> presetup.log
222c224
< (echo. &echo run setup CmdLine: %CmdLine% - %date% %time%)>>presetup.log
---
> (echo. &echo run setup CmdLine: %CmdLine% - %date% %time%) >> presetup.log
233c235
< (echo. &echo prepare USB boot configuration %date% %time% )>>presetup.log
---
> (echo. &echo prepare USB boot configuration %date% %time% ) >> presetup.log 

I like to keep this lines: if exist c:\Inst\XP_*.ISO set reassign=true
Idea, USB drive got letter c:, let windows reassing drive letters. Internal hard disk may get c: or windows assign c: for USB again.
Do you have different results? Can you describe the conditions?

Thanks, I missed a > at 'echo presetup fixBoot.USB > presetup.log'.
Yes, use 'echo presetup fixBoot.USB >> presetup.log'

kDn, on Oct 19 2009, 10:36 AM, said:

On some systems USB do not initialized properly, this can be fixed like that:

I'm glad to keep the fixBoot.USB section, actually I might have deleted this part.
Now this is usefull at some conditions.
Do you have some examples? Which systems dosn't initialize USB properly.

Another idea for multiple installation:
add several floppy images XP_INST.IMA to multi boot ISO image.
Load the ISO image to RAM first, and load a appropiate floppy image from ISO image next.

robekia, on Oct 27 2009, 08:54 AM, said:

Start the text mode windows setup till i reach the step for choosing the partition to install windows --> actually this step never reached and blank screen appear instead.

Windows setup hang at partition detection/mounting.
Does internal hard disk contain partitions already?
Does a Memory stick 8GB/1GB/4GB work at the ACER5738 ?

[robekia]

cdob, on Oct 27 2009, 08:13 PM, said:

Windows setup hang at partition detection/mounting.
Does internal hard disk contain partitions already?
Does a Memory stick 8GB/1GB/4GB work at the ACER5738 ?

That's what i thought about, partition detection hang.

yes the HDD already contain partitions on which the XP already installed and some are free.
the HD is 320GB and currently working fine and i devided it to (C: 20, D: 20, E: 20, F: 20, G: the rest)
i want to install windows on C: or D:
I tried also with some other HD with the same results

yes, the Memory Sticks working fine on this ACER and all other mentioned Laptops in case reading and writing
yes, the Memory Sticks working fine on all other mentioned Laptops in case installing windows
NO, the Memory Sticks didn't work on this ACER5738 in case installing windows

This post has been edited by robekia: 27 October 2009 - 12:08 PM

[cdob]

robekia, on Oct 27 2009, 12:59 PM, said:

the HD is 320GB and currently working fine

Windows setup is more picky than windows. Installation may reject the hard disk anyway, partition detection hang at more reasons.

Can you try a installation CD?

robekia, on Oct 27 2009, 12:59 PM, said:

I tried also with some other HD with the same results

Did you zero the hard disk first? e.g. WinDlg http://support.wdc.c...ndlg/WinDLG.zip

Or a ACPI issue. Try press F7 at F6 message.

Disconnect as much hardware as possible.

Or try different map (hdN) (hdN). Actually no idea, I don't use a ACER5738.

[kDn]

cdob

Quote

Diff are spaces in most cases

Yes, you may ignore this strings

Quote

I like to keep this lines: if exist c:\Inst\XP_*.ISO set reassign=true
Idea, USB drive got letter c:, let windows reassing drive letters. Internal hard disk may get c: or windows assign c: for USB again.
Do you have different results? Can you describe the conditions?

I don't use ...\Inst\... path, as you can see earlier I use write --offset=0 (fd0)/setup/ISOimage.ini \\boot\\XP_RAM.ISO\n;\n;\n;. If follow script logic then can see:

  set ISO_file_search=\Inst\XP_RAM.ISO
  if exist ISOimage.ini for /f "eol=;" %%a in (ISOimage.ini) do if not %%a.==. set ISO_file_search=%%a
  if exist c:%ISO_file_search% set reassign=true
  if defined reassign if /I %SystemDrive%.==C:. set reassign=

1. Set default path
2. Read new path from ISOimage.ini
3. If exist c:\boot\XP_RAM.ISO then reassign=true (in my case)
4. If defined reassign and %SystemDrive%.==C: then reassign not needed

Quote

I'm glad to keep the fixBoot.USB section, actually I might have deleted this part.
Now this is usefull at some conditions.
Do you have some examples? Which systems dosn't initialize USB properly.

When people testing yours method they feedback error in some cases when installing XP from USB-HDD or USB-Flash as HDD... First stage (txt-mode-setup) running absolutly correct, but after reboot they give error like: Needed file 'asms' on Windows XP Professional Service Pack 3 CD and after Shift+F10 and looking presetup.log we can see that USB device where placed XP_RAM.ISO not found...
Error feedback:
http://forum.ru-board.com/topic.cgi?forum=...p;start=1560#20
http://greenflash.su...7-16-1256148181

Quote

Another idea for multiple installation:
add several floppy images XP_INST.IMA to multi boot ISO image.
Load the ISO image to RAM first, and load a appropiate floppy image from ISO image next.

That's about unattended install? I not sure... As I think - correct some values outside ISO and IMA winnt.sif more simplest way. This solution founded when I tested wrong winnt.sif placed inside ISO and which give error like that: setup cannot copy the file: firadisk.sys ... and other from IMA

Problem description:
http://forum.ru-board.com/topic.cgi?forum=...mp;start=1640#7
http://forum.ru-board.com/topic.cgi?forum=...p;start=1700#15
http://forum.ru-board.com/topic.cgi?forum=...p;start=1720#16

[robekia]

Sorry for late reply because i was out for some reasons.

today, i did some tests and hereunder the findings:

cdob, on Oct 27 2009, 09:34 PM, said:

Can you try a installation CD?

YES for sure i tried to install the same nLite iso using CD and it works perfectly.

cdob, on Oct 27 2009, 09:34 PM, said:

Did you zero the hard disk first? e.g. WinDlg http://support.wdc.c...ndlg/WinDLG.zip

i did ZERO to another hard disk which is 80GB used for testing but still the same results (Blank Black screen) as my current HD which means that either something wrong with MYSELF or with the bios of the Laptob

cdob, on Oct 27 2009, 09:34 PM, said:

Or a ACPI issue. Try press F7 at F6 message.
Disconnect as much hardware as possible.

of course No ACPI issue as i believe no issues with the hardware of my computer.

Also, pressing F7 at F6 message doing nothing, the Laptob continue without giving me any choices, it seems it didn't recognize F7 at all.

cdob, on Oct 27 2009, 09:34 PM, said:

Or try different map (hdN) (hdN). Actually no idea, I don't use a ACER5738.

Grub is giving error for any tries to map different Hard disk than (hd0, hd1) because the SD is hd0 and the physical hard disk is hd1

i still insist that there is always a solution

[cdob]

@kDn
It's fun to read http://forum.ru-board.com/ with google translation.
I don't understand some translation parts.
I understand: a Asus A6Q00VM, Pentimum M call, I915 chipset does require fixBoot.USB.
I expect a USB boot nightmare (Dell Dimension 5150) would require this too.
fixBoot.USB. does require a addional reboot and is disabled by default therefore.

I may change fixBoot.USB settings at setup.cmd: detect missing USB drive
Understood finally, I'll add too: if exist c:%ISO_file_search% set reassign=true
Need some time. This includes mkISO_RAMload_sort.cmd, read below.

Yes, winnt.sif [MassStorageDrivers] and floppy txtsetup.oem fails. Driver not found.
Another idea: write to winnt.sif inside RAM ISO, disable [MassStorageDrivers].


Recovery Console:

Sort some files at mkISO_RAMload_sort.cmd

rem sort some recovery console files
FOR %%a in (autochk.ex? autofmt.ex? kbd*.dl?) do (
 call :sort_boot ./%boot_directory% %%a)

if exist ASMS echo ./%boot_directory%/ASMS/* -7000>>%sort_lst%

And load first 20mb: map --mem (0xFE)+10000 (0xFF)

Does mentioned recovery console start by default?
Do you have to press F10 at F6 message?

Compare: Adding Windows Recovery Console, Without having to press F10 or R in setup
http://www.msfn.org/board/adding-windows-r...le-t139069.html


There was a question about mkisofs -input-charset utf-8 and -duplicates-once.
http://forum.ru-board.com/topic.cgi?forum=...mp;start=1680#3
http://forum.ru-board.com/topic.cgi?forum=...p;start=1720#19
I don't understand clearly: does this refer to windows or another operating system?

Alex Kopylov (former bootcd.ru) added -duplicates-once and -force-uppercase in 2004.
This mingw32 version isn't supported since 2004. There is no charset utf-8.

Mkisofs uses iconv nowadays http://en.wikipedia.org/wiki/Iconv.
And cygwin file cygiconv-2.dll does offer charset utf-8.

Integrate -duplicates-once source code to current cdrtools version and compiled at cygwin:
Source code cdrtools-2.01.01a66-bootcd.ru-mkisofs.tar.gz
Win32 binaries cdrtools-2.01.01a66-bootcd.ru-mkisofs.7z
This version support -input-charset utf-8 and -duplicates-once, however russian characters are not tested.



@robekia
Sorry, no more idea. There is a strange BIOS.