Author Topic: ? on No-emulation  (Read 1335 times)

jeanie2600

  • Guest
? on No-emulation
« on: June 02, 2002, 11:02:36 PM »
I am trying to make a multi OS boot CD with XP Home & Pro. I\'ve read some threads about the
\"no-emulation image type RAW\" error and that it is normal.

However, when I press enter at this point, the setup of the OS does not continue, all I get is the same screen again with the option to choose either 1 for XP Pro or 2 for Home if the hard drive is blank. If there is an OS on the drive already, it just boots the installed OS as normal rather than loading \"setup.exe\"

What am I doing wrong? I am using the xphmsect & xpprsect.dat files from Twinkie\'s site.
Here is the diskemu.cmd file I am using:

:start
cls
print
print Setup Menu
print ==========
print 1. Windows XP Professional
print 2. Windows XP Home
print 3. Windows Advance Server (Not Used)
print Esc) Boot from hard disk...
print
print Enter a choice:

:mainkey
; timeout is 30 seconds, default key is escape
getkey 30 esc
onkey 1 goto pro
onkey 2 goto srv
onkey 3 goto advsrv
onkey esc boot 80
; When no key found...
goto mainkey
;

:pro
run XPPRSECT.DAT
;

:srv
run XPHMSECT.DAT
;

:advsrv
run ASRVSECT.DAT
;


Thank you!
Jeanie

jeanie2600

  • Guest
? on No-emulation
« Reply #1 on: June 04, 2002, 09:13:42 AM »
Thanks to Twinkie, I got this bug figured out!

jeanie2600

Anonymous

  • Guest
? on No-emulation
« Reply #2 on: June 04, 2002, 09:42:35 AM »
well, from highlighting the text you wrote, it seems there are a lot of space.  there are to be no spaces after the end of a line

ie.
run arvsect.dat
instead of
run arvsect.dat_

this may be your problem, if you have spaces at the end of any lines, it is def. your problem, but if you dont then it could be something else.  Ill look more closely at your .cmd file

Offline Twinkie

  • member
  • Full Member
  • ***
  • Posts: 168
  • Karma: +0/-0
    • View Profile
? on No-emulation
« Reply #3 on: June 04, 2002, 02:47:50 PM »
First, add an error message after the sections for troubleshooting.  That will let you know if the command itself or the dat files are the problem.

I use ---
:pro
run WPROSECT.DAT
; when run has failed
print
print Failed to run \"WPROSECT.DAT\", hit any key.
getkey
goto start
;

If it says Failed... then something is wrong with the dat files.  If nothing happens it is most likely the diskemu file.

Second, check your motherboard settings at Bart\'s site.  There is some notes about multiboot not working on certain typs of motherboards but few have reported any problems.  At least few told me about it.
Hope this Helps,

Twinkie