[multi Os Cd Problem] Getting No Emulation Error

[::TR::]

I'm getting:
No-Emualation type image (raw)
0000080000000001
Hit a key to start from CD-ROm [this line is translated by me as it doe not show up in english]

When I pick a option where a XXXXSECT.DAT file is used.

Does anyone know how to take care of this error ?

[::TR::]

Am I the only one who have run into this error ?

If anyone got any info about this error, please let me know about it.


Thanks in advance

[::TR::]

If you don't get this error, please let me know of it as well then.

thanks

[koszopal]

hi
 try search in software :Emulation type image
 koszopal

[Space Between]

Your image is not a valid bootable image. Whatever your using is not going to work. However it could be your bios to. Some bios's dont like diskemu...but if diskemu did load..then its your boot image that is wacked.

Describe what you are doing in creating the .dat and all the rest of the stuff...diskemu is booting right?

[::TR::]

[quote name=\'koszopal\' date=\'Apr 23 2003, 03:28 AM\']hi
 try search in software :Emulation type image
 koszopal[/quote]
 Doh, I forgot about that.
This is what Twinkie say:
When you see:
Running xxxxSECT.DAT
No Emulation Type Image (Raw)
00000800000000001
Press Enter to ...

That is not an error. That is the boot file from the Microsoft CD. If you press a key you will start setup like normal, otherwise it boots to the HD. If no OS is on the machine it will error out. No way around that so far. The No Emulation Type Image (Raw) is the type of image we are all using. The serial number.... got me. I got the file from Bart.

To be honest, I don't believe that. I do think that s some sort of error. But it does start loading the set up after hitting a key.

[::TR::]

[quote name=\'Space Between\' date=\'Apr 24 2003, 09:23 PM\']Your image is not a valid bootable image. Whatever your using is not going to work. However it could be your bios to. Some bios's dont like diskemu...but if diskemu did load..then its your boot image that is wacked.

Describe what you are doing in creating the .dat and all the rest of the stuff...diskemu is booting right?[/quote]
 Well I useing http://tech-hints.com/ as my guide here.

Yeas, diskemu do load ( the boot menu appears ).
What do you mean by \"boot image that is wacked\" ?
I seem to me that it is diskem1x.bin that is reporting this error. Can the code line that report about this error be deleted (I only want to do that if this not a error, as Twinkie say it isn't).
I have seen somewhere in a guide that someone used a bin-file and not a XXXXSECT.DAT file, would that be a way around this problem (if else doesn't work) ?
I have also thought about that this can be a diskemu problem only. How do I do this stuff with bootscriptor ?

[Space Between]

Slow down...diskemu or the other bootscriptor thing???

First of all that IS NOT a error. Emulation means floppy imulation. As if you were emulating as in the
means of a image...you are not doing that.

It is your .dat file that is wacked. Dont belive me because you dont have to right...however i got that
same error before. In fact if you search all the threads on this board like 2 years old you will see me
posting about this very same thing...if you search.

File extension dont matter. Aslong as it is alphanumeric it should work. Not a single operating system
depends on file extensions...it is just there for a convience. 95% of all files on a computer are plain text
files. So something like Diskemu just interprets the text into values. If you have ever tried to open a
PURE binary file you would know this (grrr shssshhssh grrr sssshhhh gr bleeeennnn shhhh...modem failed to
connect http://images.thetechguide.com/forum/public/style_emoticons/<#EMO_DIR#>/smile.gif\' class=\'bbc_emoticon\' alt=\'\' />...j/k'n if you know what i mean http://images.thetechguide.com/forum/public/style_emoticons/<#EMO_DIR#>/smile.gif\' class=\'bbc_emoticon\' alt=\'\' />.

Anyways, if you followed the guide...then open the .dat file in a hex editor, copy the code from their and
paste it to here. BTW i have already done this in a couple threads. You could track down one of these threads and copy that code into the hex editor and save it...and it should work :-)

Im thinking your either A. somehow using a compressed image...or B. Using a image that is NOT formatted
correctly...(these are sort of obvious...sorry :-)

Remember you can name it anything you want alphanumberically...in example  trs.boot.123
I think you might want to stick with the 8.3 convention though...like above.

btw...i like twinkies sight...so dont get me wrong here. But i really think you should refer to that thread
about all this. It gives more insight to other things that can go wrong. Twinkies sight really doesnt tell
you what the output of something might be if you got something wrong...the thread does....and ALOT
of it .-)

[Space Between]

wait...props to Twinkie because if you follow it EXACTLY it WILL work...so it's a user problem.

one more thought...could your .DAT file be corrupted?? like during transfer, extraction, burn.

More insight is needed either way....either way read that thread...and you will be a master
at it http://images.thetechguide.com/forum/public/style_emoticons/<#EMO_DIR#>/smile.gif\' class=\'bbc_emoticon\' alt=\'\' /> (what little there is too it...diskemu does all the real work :-)...thanks Bart)

[::TR::]

I can extract the file, which holds the dat-files, without any problem. So the dat-files are not corrupt as if they are not packed as corrupt.
I have search for the thread with the hex code you mention, but I can't seem to find it. Could you maybe post that again or help me find that thread in question ?

[Twinkie]

Where did you get your .DAT file from TR.  My site or did you make your own?  The DAT file is just a renamed bootsect.bin file from the oringinal CD's.   I have had people report problems but everyone tracked it down to a corrupt file or error in the diskemu.cmd file.

Anyway open your DAT file in a HexEditor.  Do not use Notepad!  Near the end, find the line:
SETUPLDR.BINBOOTFIX.BINI386

and change the I386 at the end to the folder name you are using.  So if using W2KP for 2000 Pro change the line to:
SETUPLDR.BINBOOTFIX.BINW2KP

In this example I put my boot (setup) files in the W2KP folder at the ROOT of my CD.

As to the error you mention.  No it is not an error.  That is just how the program passes along its info to you.  Everyone gets that message.

Running xxxxSECT.DAT                               -- What file you selected
No Emulation Type Image (Raw)                --  Type of emulation
00000800000000001                                --  String count (if I remember right, part of the report from diskemu)
Press Enter to ...                                       --  This is the part from M$.  Just like their CD's.

[::TR::]

Ok. But how do one do to make that message not show up. As Space Between wrote, \"i got that
same error before\". So I would guess that you can make the message in qestion not show up on the screem.

[::TR::]

I would like to check if bootscriptor gives the same message (which is not a error http://images.thetechguide.com/forum/public/style_emoticons/<#EMO_DIR#>/smile.gif\' class=\'bbc_emoticon\' alt=\'\' /> ). If you know how I would do to replace diskemu with bootsriptor, please give me a helping hand. If you do know how to modify diskemu so I wont get the message meantion above, please help me than as well.

[Space Between]

i didnt make that clear...i did get that message before...but it was
me who was doing something wrong to get that message.

you should see a message of some sort to press a key with similar
looking text above it

it is your boot.dat/bin/sec whatever.  your doing something wrong

i cant prove it is you that is doing something wrong...but since you
seem to be the only one with this problem currently after reading the
faq at twinkies and the thread on this (assuming you read the thread) im
going to play the numbers and say it is you.

only thing i could think of, but have no knowledge in, is your bios...which
makes no sense being diskemu is controlling it at this point.

Im betting on the possibility of your .dat/.bin or whatever is wrong.
Im thinking you extracted this WRONGLY in cdrwin or whatever.

About that thread i pasted it in..i couldnt find it either http://images.thetechguide.com/forum/public/style_emoticons/<#EMO_DIR#>/sad.gif\' class=\'bbc_emoticon\' alt=\'\' />..
will look now for you though and post back if i find it