Jump to content

Win2K issues [SOLVED]


fordp01

Recommended Posts

Hi,

I am trying to setup Win2k with WinSetupFromUSB. But I am encountering two problems:

I get an error when using v2.3:

AutoIt Error

Line -1

Error: Subscript used with non-Array variable

This happens when trying to prepare the ~LS Folder.

Log:

2009/08/22 10:38:01- WinSetupFromUSB 0.2.3 started

2009/08/22 10:38:01- OS: WIN_XP Architecture type: X86 ServicePack: Service Pack 3 OS Language: 0407

2009/08/22 10:38:01- Getting USB drives information

2009/08/22 10:38:01- Found USB Physical Disk: JetFlash Transcend 8GB USB Device -- \\.\PHYSICALDRIVE6

2009/08/22 10:38:01- Found USB Disk Partition: Disk #6, Partition #0

2009/08/22 10:38:01- Found USB Logical Disk: I: File system: NTFS Bootable: -1

2009/08/22 10:38:01- Found USB Disk Partition: Disk #6, Partition #1

2009/08/22 10:38:01- Target drive selected- I:

2009/08/22 10:38:01- Drive letter of the active partition in selected disk- I:

2009/08/22 10:38:01- Total target size avialable- 7258 MB

2009/08/22 10:38:01- Checking sizes...

2009/08/22 10:38:01- Total source size- 0 MB

2009/08/22 10:38:01- Target space available- 7258 MB

2009/08/22 10:38:09- Checking sizes...

2009/08/22 10:38:09- Total source size- 347.9 MB

2009/08/22 10:38:09- Target space available- 7258 MB

2009/08/22 10:38:09- Windows source selected- D:\Software\Unattended\Win2k SP4 Asus A8V

2009/08/22 10:38:09- Source version- Microsoft Windows 2000 Professional

2009/08/22 10:38:09- Service Pack- Service Pack 4-

2009/08/22 10:38:09- AMD64 flag- 0

2009/08/22 10:38:18- Removing TEMP folder

2009/08/22 10:38:18- Checking if grub4dos is installed properly

2009/08/22 10:38:18- Checking for grldr string in BootSector of disk #6 partition #0

2009/08/22 10:38:20- Saved BootSector of disk #6 partition #0

2009/08/22 10:38:21- Grub4dos bootsector found

2009/08/22 10:38:21- Checking for grldr string in MBR of disk #6

2009/08/22 10:38:23- Saved MBR of disk #6

2009/08/22 10:38:24- Grub4dos MBR not found

2009/08/22 10:38:24- grub4dos BS/MBR and files are installed properly

2009/08/22 10:39:05- DOSNET.INF parsed, 106 files for ~BT folder

...

2009/08/22 10:39:05- Preparing ~BT folder completed

2009/08/22 10:39:05- Launching MkMigrateInf3.cmd

2009/08/22 10:39:08- Adding lines for binifix5.cmd and start64.exe

2009/08/22 10:39:08- Preparing ~BT folder and boot files

2009/08/22 10:39:08- Preparing ~LS folder

Version 1.1 does not show this error.

When booting from USB prepared with 1.1 I can select text setup and everything is fine until message

"Starting win2k".

Then I get a BlueScreen with errror 7b (inaccessible boot device)

Some additional information:

I am trying to install on an IDE HDD and I formatted the USB stick with HP tool to NTFS with 1.1.

Using the search function I learned about the modified NTDETECT.COM and used it. But this still lead to the BlueScreen.

It does not make any difference if I select the USB stick via boot menu or set it up as first boot device in BIOS.

Any help would be appreciated.

Link to comment
Share on other sites


Sorry, I didn't find that post.

Yes. With the dummy file I am able to prepare the USB stick with version 0.2.3.

But I still get the BlueScreen.

Could my current partitioning be a problem?

I have a primary partition © with NTFS of 8 GB and a logical of 43 GB with NTFS on my IDE disk.

Additionally two SATA drives are connected to an onboard RAID controller. But I haven't set up a RAID array.

Theses are just single disks. And deconnecting the SATA drives did't change anything.

Link to comment
Share on other sites

On another PC I get no BlueScreen and I get to the screen where I can select the partition to install Win2K on.

So the USB stick seems to be OK.

The PC with the Bluescreen has an Asus A8V Deluxe Mainboard with AMD Opteron.

Link to comment
Share on other sites

Running out of ideas...

Try updating BIOS if possible.

Check any setting in BIOS regarding USB and play a bit with them- USB legacy support etc.

Disconnect any other USB devices if present.

If none of the above works and somebody else doesn't come up with another idea- check out this method, it should not lead to 0x7B when RAM based LiveXP is used:

http://www.msfn.org/board/2-t121446.html

Link to comment
Share on other sites

Since I had no other USB devices connected and my BIOS is the latest version I started changing BIOS settings.

I ended up clearing CMOS and this finally helped.

No more Bluescreen but the partition selection screen of the Win2K text setup.

Beside the USB stick my existing partitions C and D were displayed.

I selected C for install and the following setup was OK until after the third boot when booting from HDD for the first time.

There I get the message "Reboot and select proper boot device ...".

Did I miss something again?

Link to comment
Share on other sites

Good, some progress.

2000 likes the USB stick as boot device (XP upwards ignores removable devices for that purpose, but 2k doesn't treat them differently) and places boot files on it. Presetup.cmd should copy those files (boot.ini, ntdetect.com and ntldr) to C:, assuming that's the active partition on the hard disk, but you need to make sure it's primary and set as active.

You may do that from any partition manager, PartedMagic which includes GParted for example. Check if boot files are there too.

Fixmbr and fixboot from recovery console may also help if partitioning was done not from Windows or Windows

Warning:

Use device name for fixmbr, get it from output of command "map".

http://www.microsoft.com/resources/documen...r.mspx?mfr=true

For fixboot use drive letter for the active partition on the hard disk.

http://www.microsoft.com/resources/documen...t.mspx?mfr=true

Improper use of the above 2 may overwrite MBR/bootsector on the USB stick, removing grub4dos boot code.

Link to comment
Share on other sites

Good, some progress.

2000 likes the USB stick as boot device (XP upwards ignores removable devices for that purpose, but 2k doesn't treat them differently) and places boot files on it. Presetup.cmd should copy those files (boot.ini, ntdetect.com and ntldr) to C:, assuming that's the active partition on the hard disk, but you need to make sure it's primary and set as active.

You may do that from any partition manager, PartedMagic which includes GParted for example. Check if boot files are there too.

Fixmbr and fixboot from recovery console may also help if partitioning was done not from Windows or Windows

Warning:

Use device name for fixmbr, get it from output of command "map".

http://www.microsoft.com/resources/documen...r.mspx?mfr=true

For fixboot use drive letter for the active partition on the hard disk.

http://www.microsoft.com/resources/documen...t.mspx?mfr=true

Improper use of the above 2 may overwrite MBR/bootsector on the USB stick, removing grub4dos boot code.

thanks for the info

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...