Hello,

  My company recently received a Dell computer that we had sent in for repair. After receiving the computer I attempted to start a scripted install on the computer, which failed (Windows 7 install). The install began, the blue screen at the very beginning of the Windows installation appeared and froze, then it failed in about a minute. It then reverted back to the K2000 scripted install page with the command prompt still open. Then about a second later the command prompt turned off and all the links on the page began displaying a “Script has failed” error message when clicked. After recording the screen with my phone’s camera I found out that the command prompt in the video frame before it disappeared showed the error “The system cannot open the device or file specified.” I decided the laptop must be acting up, and thought I’d work on it more later (it wasn’t top priority at the time).

  Today we received some new Dell laptops, which I began performing scripted installs on, which also failed in the same manner. After some testing (phone video camera again), I found that the error message was being displayed on these as well. I know the scripted install has worked in the past with these same models so I don’t see how this could be a driver issue. Does anybody have any experience with this error? Thanks in advance for your help

– Ben M

Answer Summary:
Drivers in the Kbox2000\Drivers\windows_7_x64 folder were apparently causing the install to fail.
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

3

Particularly with the new laptops, I would check the BIOS version and make sure they aren't running the A13 version:

http://www.itninja.com/blog/view/not-enough-memory-error-when-loading-kbe-during-scripted-install

As for the laptop you are attempting to reload, if it's failing at the beginning of the Windows install I would also suspect something driver (or hardware)-related causing the error.  The first thing I would try (just for testing) would be a manual install of Windows to make sure it starts OK and doesn't fail outright as with the scripted install.  If it proceeds normally, the next thing I'd try would be creating a new (very basic) scripted install to rule out any potential issues with the existing scripted install.  If this fails as well, I would look into replacing the Win7 source media on the K2000 (or load a "test" one) and see how that does.  If that continues to fail, I would delete any drivers cached on the K2000 and download/copy them over again. 

Beyond that, I would call support as the "script has failed" error may indicate that a core K2000 script may be corrupt.

John

Answered 07/23/2012 by: jverbosk
Red Belt

  • Thanks John,
    I checked the BIOS version already. That was the first thing that came to mind. I'll try the other tests as I get time, it's Monday. If you know what I mean :/.
  • Definitely.... >_<
  • After some testing I've decided to contact support. I'll let you all know how it pans out.
Please log in to comment

Answers

2

If the drives are the AF type make sure you have those drivers in the KBE and the image

Answered 07/23/2012 by: SMal.tmcc
Red Belt

  • I guess I'll try re-adding the drivers and re-creating the KBE. I'll let you know what happens.
  • Assuming I found the correct drivers (I think I did), this didn't seem to solve the problem. I'll talk to support and see what they think.
Please log in to comment
1

I would think this is a partitioning issue.

You can manually verify that kbe can see the disk by going to Recovery | Command Prompt, then type in diskpart and then list disk. This will show the drives that kbe sees.

If it can't see it, it is storage drivers. If it can see it, it sounds like you need some preinstall tasks to create your partition and format it, usually "create single partition" and "format c: as ntfs."

Corey
Lead L3 Enterprise Solutions Engineer, K2000
If my response was helpful, please rate it!

Answered 07/22/2012 by: cserrins
Red Belt

  • Thanks for your response Corey. I checked Diskpart and it showed the drive, and it could select the drive and list the partition that was created during the last failed scripted install. I confirmed the pre-install tasks are correct. They are as follows: Create Single Partition, Format C: as NTFS, Install Vista/2008/7 MBR.
Please log in to comment
0

Well, after a few weeks with support we finally located the problem. We removed the drivers from Kbox2000\Drivers\windows_7_x64 and the install now works great. The drivers that I believe were causing the problems were some lenovo drivers for the x130e model. Thanks for all your help.

Answered 08/07/2012 by: Ben M
Ninth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity