checked build 2003 sp1 with vmware gsx

Hello,

I have a problem loading the checked Server 2003 SP1
kernel on VMWare GSX server.
I followed the instructions how to use a partial
checked build, and copied the kernel and HAL files
with .chk extensions into windows\system32.

Here is the line I added to boot.ini:
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Windows
Server 2003, Checked” /noexecute=optout /fastdetect
/kernel=ntoskrnl.chk /hal=halaacpi.chk

When I choose to boot the checked kernel, I get this
error:
“Windows could not start because the following file
was missing or corrupt:
\system32\ntoskrnl.exe
Please reinstall a copy of the above file.”

Anyone had any similar problem?

Thanks,
Seva

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Seva Tonkonoh wrote:

Hello,

I have a problem loading the checked Server 2003 SP1
kernel on VMWare GSX server.
I followed the instructions how to use a partial
checked build, and copied the kernel and HAL files
with .chk extensions into windows\system32.

Here is the line I added to boot.ini:
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Windows
Server 2003, Checked” /noexecute=optout /fastdetect
/kernel=ntoskrnl.chk /hal=halaacpi.chk

When I choose to boot the checked kernel, I get this
error:
“Windows could not start because the following file
was missing or corrupt:
\system32\ntoskrnl.exe
>Please reinstall a copy of the above file.”
>
>

I have assumed that VMware needs a custom HAL, not one of the stock
HALs. Is that not correct?


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

No, I believe it can use a stock kernel,
I used VMWare workstation with Windows 2000 Pro
partial checked build before without problems.

Thanks,
seva

— Tim Roberts wrote:

> Seva Tonkonoh wrote:
>
> >Hello,
> >
> >I have a problem loading the checked Server 2003
> SP1
> >kernel on VMWare GSX server.
> >I followed the instructions how to use a partial
> >checked build, and copied the kernel and HAL files
> >with .chk extensions into windows\system32.
> >
> >Here is the line I added to boot.ini:
> >
> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Windows
> >Server 2003, Checked” /noexecute=optout /fastdetect
> >/kernel=ntoskrnl.chk /hal=halaacpi.chk
> >
> >When I choose to boot the checked kernel, I get
> this
> >error:
> >“Windows could not start because the following file
> >was missing or corrupt:
> >\system32\ntoskrnl.exe
> >Please reinstall a copy of the above file.”
> >
> >
>
> I have assumed that VMware needs a custom HAL, not
> one of the stock
> HALs. Is that not correct?
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
>
> —
> You are currently subscribed to windbg as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

I found the problem.
When I extracted the kernel files from the SP1,
they were still compressed.
I had to uncompress each of them
individually.

Sorry for the hassle,
seva

— Seva Tonkonoh wrote:

> No, I believe it can use a stock kernel,
> I used VMWare workstation with Windows 2000 Pro
> partial checked build before without problems.
>
> Thanks,
> seva
>
> — Tim Roberts wrote:
>
> > Seva Tonkonoh wrote:
> >
> > >Hello,
> > >
> > >I have a problem loading the checked Server 2003
> > SP1
> > >kernel on VMWare GSX server.
> > >I followed the instructions how to use a partial
> > >checked build, and copied the kernel and HAL
> files
> > >with .chk extensions into windows\system32.
> > >
> > >Here is the line I added to boot.ini:
> > >
> >
> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Windows
> > >Server 2003, Checked” /noexecute=optout
> /fastdetect
> > >/kernel=ntoskrnl.chk /hal=halaacpi.chk
> > >
> > >When I choose to boot the checked kernel, I get
> > this
> > >error:
> > >“Windows could not start because the following
> file
> > >was missing or corrupt:
> > >\system32\ntoskrnl.exe
> > >Please reinstall a copy of the above file.”
> > >
> > >
> >
> > I have assumed that VMware needs a custom HAL, not
> > one of the stock
> > HALs. Is that not correct?
> >
> > –
> > Tim Roberts, xxxxx@probo.com
> > Providenza & Boekelheide, Inc.
> >
> >
> >
> > —
> > You are currently subscribed to windbg as:
> > xxxxx@yahoo.com
> > To unsubscribe send a blank email to
> > xxxxx@lists.osr.com
> >
>
>
>
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam
> protection around
> http://mail.yahoo.com
>
>
> —
> You are currently subscribed to windbg as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>


Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Hi, I am having trouble installing 2003 SP1 checked build with Vmware Workstation 5. Setup copies files ok, I reboot, the splash screen comes up then it bug checks:

0x0000007E (0x80000003, 0x81158CC1, 0xF78E9D68, 0xF78E9A64)

No device driver information listed. I have looked on the Vmware forums and tried a few things (using an IDE disk, setting uhci.forceHaltBit = TRUE etc) without success.

Anyone managed to achieve this, or have any suggestions?

Cheers

J

Seva Tonkonoh wrote:
I found the problem.
When I extracted the kernel files from the SP1,
they were still compressed.
I had to uncompress each of them
individually.

Sorry for the hassle,
seva

— Seva Tonkonoh wrote:

> No, I believe it can use a stock kernel,
> I used VMWare workstation with Windows 2000 Pro
> partial checked build before without problems.
>
> Thanks,
> seva
>
> — Tim Roberts wrote:
>
> > Seva Tonkonoh wrote:
> >
> > >Hello,
> > >
> > >I have a problem loading the checked Server 2003
> > SP1
> > >kernel on VMWare GSX server.
> > >I followed the instructions how to use a partial
> > >checked build, and copied the kernel and HAL
> files
> > >with .chk extensions into windows\system32.
> > >
> > >Here is the line I added to boot.ini:
> > >
> >
> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Windows
> > >Server 2003, Checked” /noexecute=optout
> /fastdetect
> > >/kernel=ntoskrnl.chk /hal=halaacpi.chk
> > >
> > >When I choose to boot the checked kernel, I get
> > this
> > >error:
> > >“Windows could not start because the following
> file
> > >was missing or corrupt:
> > >\system32\ntoskrnl.exe
> > >Please reinstall a copy of the above file.”
> > >
> > >
> >
> > I have assumed that VMware needs a custom HAL, not
> > one of the stock
> > HALs. Is that not correct?
> >
> > –
> > Tim Roberts, xxxxx@probo.com
> > Providenza & Boekelheide, Inc.
> >
> >
> >
> > —
> > You are currently subscribed to windbg as:
> > xxxxx@yahoo.com
> > To unsubscribe send a blank email to
> > xxxxx@lists.osr.com
> >
>
>
>
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam
> protection around
> http://mail.yahoo.com
>
>
> —
> You are currently subscribed to windbg as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>


Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com


You are currently subscribed to windbg as: xxxxx@yahoo.co.uk
To unsubscribe send a blank email to xxxxx@lists.osr.com

---------------------------------
To help you stay safe and secure online, we’ve developed the all new Yahoo! Security Centre.

J wrote:

*Hi, I am having trouble installing 2003 SP1 checked build with Vmware
Workstation 5. Setup copies files ok, I reboot, the splash screen
comes up then it bug checks:*
**
*0x0000007E (0x80000003, 0x81158CC1, 0xF78E9D68, 0xF78E9A64)*
**
*No device driver information listed. I have looked on the Vmware
forums and tried a few things (using an IDE disk, setting
uhci.forceHaltBit = TRUE etc) without success.*
**
*Anyone managed to achieve this, or have any suggestions?*
**
*Cheers*
**
*J*
**
**
Hi,

It means a breakpoint has not been handled. Unfortunately if this
happens right after the setup you cannot install the debugger that would
help you. I think the checked build has detected an error and asserts.
Again, an access to the debug print would help. What I would suggest is
to remove all virtual devices except the ones required to run the VM.

I don’t know if this helps but I had a similar problem with 2000 SP4
Checked running in VMWare 5. Right after the installation of the VMWare
tools the system would assert, become sentient and kill people randomly.
Since I upgraded to 5.5 I don’t have this problem anymore.

Edouard