Jump to content











Photo
* * * * * 1 votes

UltraSCSI320 Adaptec 29320LPE + Seagate Cheetah 15k.5 + Win XP


  • Please log in to reply
85 replies to this topic

#1 gianni_trad

gianni_trad

    Member

  • Members
  • 46 posts
  • Location:Italy
  •  
    Italy

Posted 26 August 2008 - 11:39 AM

Hi at all! :whistling:

I bought an Adaptec 29320LPE kit and a Seagate Cheetah 15k.5 SCSI ULTRA 320 68Pin Hard-Disk few days ago.

Bios version of Adptec SCSI Card is the last: 4.31.4

Firmware of the Seagate Hard disk is the last: 003

Bios Of my Motherboard Intel 915PBL is the last. (#0040)

I tried to install Windows XP SP2 32Bit into the Seagate Cheetah SCSI Hard disk, but the Windows installing program after copied 100% files to the new hard-disk (text-mode installation), when reboot, after POST of SCSI BIOS, when need to acees to the hard disk, display this message error:

\WINDOWS\INF\biosinfo.inf file not present or damaged... (ecc)

but I verified that this file is present on the hard-disk and it's ok!

And the installation program terminate there!

How can i resolve this trouble?

I Can't install Windows XP Operating Sistem into this new Hard-drive!

Thanks!

#2 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 26 August 2008 - 12:04 PM

Is the SCSI card (and drive detected)? :whistling:

I mean are the XP drivers for it already in your XP CD, did you try using "F6" to add the drivers from a floppy or not?

jaclaz

#3 gianni_trad

gianni_trad

    Member

  • Members
  • 46 posts
  • Location:Italy
  •  
    Italy

Posted 26 August 2008 - 02:58 PM

Is the SCSI card (and drive detected)? :whistling:

I mean are the XP drivers for it already in your XP CD, did you try using "F6" to add the drivers from a floppy or not?

jaclaz



Hi Jac ;)

yes, at the beginning of the Windows XP (SP2) Installation, I Pressed F6 and then, later, I choose to load Adaptec SCSI Card Driver from the Floppy Drive.

Windows correctly detect SCSI Card Floppy Driver and Adaptec SCSI Card (Hardware, It call "Adaptec 29320LPE SCSI Cards") and correctly load them all.

Windows First-part (TEXT) Installation reach 100% without any problem... then it reboot the machine.

At the reboot, when the "second-part" Windows installation should begin, the error message appear:

\WINDOWS\INF\biosinfo.inf not present or damaged.

Now, i'm ansking myself: why It search in \WINDOWS\INF\ instead of C:\WINDOWS\INF\ ?

Running the recovery program mode, at the prompt, i've regulary found: C:\WINDOWS\>

All the files are present, including C:\WINDOWS\INF\biosinfo.inf


Where is the problem? ;)

#4 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 27 August 2008 - 09:25 AM

yes, at the beginning of the Windows XP (SP2) Installation, I Pressed F6 and then, later, I choose to load Adaptec SCSI Card Driver from the Floppy Drive.

Windows correctly detect SCSI Card Floppy Driver and Adaptec SCSI Card (Hardware, It call "Adaptec 29320LPE SCSI Cards") and correctly load them all.


Good. :whistling:

At the reboot, when the "second-part" Windows installation should begin, the error message appear:

\WINDOWS\INF\biosinfo.inf not present or damaged.

Now, i'm ansking myself: why It search in \WINDOWS\INF\ instead of C:\WINDOWS\INF\ ?

No, that's normal (not the error, the missing C:) in that stage of booting drives should be accessed with their arcpath, that is given as implied before the first back slash, something like this (pseudo-code):
<bootpartition>\WINDOWS\INF\biosinfo.inf
or
<multi&#40;0&#41;disk&#40;0&#41;rdisk&#40;0&#41;partition&#40;1&#41;>\WINDOWS\INF\biosinfo.inf
or whatever.

Now the questions:

What hard disk is connected to the card?
How BIG in size is/are the partitions on it?
What is the SOURCE?
I mean an Original XP SP2 CD, a selfmade XP CD slipstrreamed to SP2, a nlited CD?

I guess you have a floppy, right?

Is the PC a new one or an used one?

Was XP ever run on it (from a non-SCSI hard disk)?

Did you try a memtest+ run?
How many sticks and amount of RAM do you have?

Which manufacturer/model is the Motherboard?

Are the cables new, of good reliable brand, properly seated?

How was the hard disk partitioned?
I mean what program/utility did you use AND filesystems, sizes of partitions, all.

Have you a way (floppy bootdisk, USB stick whatever a way to access the ROOT partition of the drive?

I am interested in the list of files on the ROOT and to the contents of boot.ini.

Have you got another (IDE/SATA, whatever) hard disk on that machine (or that you can temporary attach to it)?

Could you if needed try running DOS on that machine?

Brief summary of ideas/troubleshooting path:
1) biosinfo.inf REALLY corrupted or needing an edit
2) memory bad
3) BIOS conflict between motherboard BIOS and SCSI card BIOS
4) bad cables
5) problems in BOOT.INI with multi/scsi syntax - may be worth a try the signature one
6) missing/bad/corrupted/whatever NTBOOTDD.SYS


Where is the problem? ;)

Tricky questions, I have seen all six listed points happen, I'm sorry to say that it will be a long and hard path to find the answer. ;)

;)

jaclaz

#5 gianni_trad

gianni_trad

    Member

  • Members
  • 46 posts
  • Location:Italy
  •  
    Italy

Posted 27 August 2008 - 01:21 PM

Now the questions:

What hard disk is connected to the card?


Seagate Cheetah 15k.5 147GB Ultra320 SCSI 68Pin

How BIG in size is/are the partitions on it?


I've already tried one only partition 140.004 MB and two partitions (60.000+80.000) installing in the secondo partition

What is the SOURCE?
I mean an Original XP SP2 CD, a selfmade XP CD slipstrreamed to SP2, a nlited CD?


I've an ORIGINAL Microsoft XP Home SP2 and an ORIGINAL Microsonf XP Professional SP2

I guess you have a floppy, right?

Is the PC a new one or an used one?


Yes, i've a Floppy drive and the PC is quasi-new :whistling:

It was new when i bought it 3 years ago.

Was XP ever run on it (from a non-SCSI hard disk)?


Yes, on a 80GB SATA150 Maxtor Hdd.

I Bought a SCSI controller + Hdd to upgrade my PC... to speed-up system operation.

Did you try a memtest+ run?


Yes, the Ram is new... i bought it 2 months ago

How many sticks and amount of RAM do you have?


Two bank 1 GB DDR2 533 Mhz in Dual-Channel (total 2 GB RAM) always right in the other Hard-Disk (SATA150) with XP Home Operating system

Which manufacturer/model is the Motherboard?


Intel: D915PBL

with an Intel Pentium4 3.6GHz 2MB L2 Cache

Are the cables new, of good reliable brand, properly seated?


Yes, the SCSI cable is the new Cable that was included in the Adaptec 29320LPE SCSI Controller kit

How was the hard disk partitioned?
I mean what program/utility did you use AND filesystems, sizes of partitions, all.


I've partitioned it during the Windows XP Installation... i've tried one only partition (140.000MB) and two partitions (60.000+80.000)

Have you a way (floppy bootdisk, USB stick whatever a way to access the ROOT partition of the drive?


Yes, I can do this by the Windows XP CD using the first recovery mode... it goes to the prompt C:\WINDOWS>

I am interested in the list of files on the ROOT and to the contents of boot.ini.


I'll accomplish this this evening when i'll return Home.

If I run XP by the other hard-disk (SATA150) it see the new SCSI controller and Hard-disk and display "new hardware detected" then it ask the drivers... i choose floppy drive and it load the Adaptec driver in the floppy drive... then It's ALL OK!

I can see the new SCSI Hard disk in Windows XP and PERFECTLY WORK with it!

I loaded many files in the new SCSI Hard disk.. and regulary opened them... Heavy Bitmap Image files, Heavy PDF files!

It's all ok using the new SCSI Hard disk as Secondary HDD !

the problem is only Installing XP into it! ..at the second boot, after text-installation!

Have you got another (IDE/SATA, whatever) hard disk on that machine (or that you can temporary attach to it)?


Yes

Could you if needed try running DOS on that machine?


Not actually, but i can find a DOS and I'll can do this.

Brief summary of ideas/troubleshooting path:
1) biosinfo.inf REALLY corrupted or needing an edit
2) memory bad
3) BIOS conflict between motherboard BIOS and SCSI card BIOS
4) bad cables
5) problems in BOOT.INI with multi/scsi syntax - may be worth a try the signature one
6) missing/bad/corrupted/whatever NTBOOTDD.SYS



Tricky questions, I have seen all six listed points happen, I'm sorry to say that it will be a long and hard path to find the answer. ;)

;)

jaclaz



#6 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 27 August 2008 - 01:58 PM

I've an ORIGINAL Microsoft XP Home SP2 and an ORIGINAL Microsonf XP Professional SP2

Sure, did not want to imply they were not ORIGINAL :whistling:, I just wanted to know if they came already SLIPSTREAMED to SP2 or not, and if the second was true HOW they were slipstreamed (manually, nlite, autostreamer, HFslip, etc.) - and if they are "Retail" (OK) "Generic OEM" (OK), "good brand OEM" like HP, Dell, Toshiba, etc. (sometimes heavily modified - may be unsuitable without editing them)

Yes, on a 80GB SATA150 Maxtor Hdd.


Crazy as it might seem, first thing I would try would be to physically disconnect the SATA disk and try again the setup with ONLY the SCSI disk connected.

About RAM, it is more tricky that you might think, I have seen PC's working perfectly but unable to re-install windows because setup didn't "like" the RAM, but it's much more probable that the problem is the conflict between SATA and SCSI.

jaclaz

#7 gianni_trad

gianni_trad

    Member

  • Members
  • 46 posts
  • Location:Italy
  •  
    Italy

Posted 27 August 2008 - 02:15 PM

Sure, did not want to imply they were not ORIGINAL :whistling:, I just wanted to know if they came already SLIPSTREAMED to SP2 or not, and if the second was true HOW they were slipstreamed (manually, nlite, autostreamer, HFslip, etc.) - and if they are "Retail" (OK) "Generic OEM" (OK), "good brand OEM" like HP, Dell, Toshiba, etc. (sometimes heavily modified - may be unsuitable without editing them)


both (XP Home SP2 and XP Proffessional SP2) are Generic OEM


Crazy as it might seem, first thing I would try would be to physically disconnect the SATA disk and try again the setup with ONLY the SCSI disk connected.


I've ALWAYS done this!

Before I tried to install XP in the SCSI Hard Disck, I fisically disconnected SATA Hdd AND In the Motherboard BIOS I enabled only the PATA device (Plextor DVD)

In the Boot sequence i set

1) Plextor DVD
2) 29320LPE ,Seagate 3146855LW
3) Disabled

In the Disk Drives i can see only

1) 29320LPE ,Seagate 3146855LW

About RAM, it is more tricky that you might think, I have seen PC's working perfectly but unable to re-install windows because setup didn't "like" the RAM, but it's much more probable that the problem is the conflict between SATA and SCSI.

jaclaz


About Ram, i've just re-installed XP on the SATA Hdd withount any problem, and I see the SCSI Hdd

#8 gianni_trad

gianni_trad

    Member

  • Members
  • 46 posts
  • Location:Italy
  •  
    Italy

Posted 27 August 2008 - 02:19 PM

In the Intel Motherboard BIOS i've already tried to disable PCI IDE Bus Master... but installing XP the same message appear after re-boot.

#9 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 27 August 2008 - 04:11 PM

In the Intel Motherboard BIOS i've already tried to disable PCI IDE Bus Master... but installing XP the same message appear after re-boot.


Ok, now, again, crazy as it might seem, try again WITH another hard disk attached.

See #3 in garfield report:
http://www.boot-land...?showtopic=5546

And that was/is the reason why I want to see your BOOT.INI file.

jaclaz

#10 gianni_trad

gianni_trad

    Member

  • Members
  • 46 posts
  • Location:Italy
  •  
    Italy

Posted 27 August 2008 - 06:23 PM

Ok, now, again, crazy as it might seem, try again WITH another hard disk attached.

See #3 in garfield report:
http://www.boot-land...?showtopic=5546

And that was/is the reason why I want to see your BOOT.INI file.

jaclaz



How another Hard disk attached?

I've already done all the possible combinations... windows doesn't complete install ONLY in the SCSI Hard-Disk.

In the other hard-disk (sata) i've already re-installed without trouble/problem!

and the SCSI Hard-disk is correctly viewed!

however,

this is the BOOT.INI of the SCSI Hdd partial installation:

[boot loader]
timeout=1
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /noexecute=optin /fastdetect



that's all. :whistling:

#11 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 28 August 2008 - 08:39 AM

this is the BOOT.INI of the SCSI Hdd partial installation:

[boot loader]
timeout=1
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /noexecute=optin /fastdetect


First thing try adding a few SCSI entries:
http://www.msfn.org/...ive-t25365.html
scsi&#40;0&#41;disk&#40;0&#41;rdisk&#40;0&#41;partition&#40;1&#41;\WINDOWS=&#34;XP SCSI 0001&#34;

scsi&#40;0&#41;disk&#40;1&#41;rdisk&#40;0&#41;partition&#40;1&#41;\WINDOWS=&#34;XP SCSI 0101&#34;

scsi&#40;1&#41;disk&#40;0&#41;rdisk&#40;0&#41;partition&#40;1&#41;\WINDOWS=&#34;XP SCSI 1001&#34;

scsi&#40;2&#41;disk&#40;0&#41;rdisk&#40;0&#41;partition&#40;1&#41;\WINDOWS=&#34;XP SCSI 2001&#34;

scsi&#40;0&#41;disk&#40;0&#41;rdisk&#40;1&#41;partition&#40;1&#41;\WINDOWS=&#34;XP SCSI 0011

scsi&#40;1&#41;disk&#40;0&#41;rdisk&#40;1&#41;partition&#40;1&#41;\WINDOWS=&#34;XP SCSI 1011&#34;

scsi&#40;2&#41;disk&#40;0&#41;rdisk&#40;1&#41;partition&#40;1&#41;\WINDOWS=&#34;XP SCSI 2011&#34;

scsi&#40;1&#41;disk&#40;1&#41;rdisk&#40;0&#41;partition&#40;1&#41;\WINDOWS=&#34;XP SCSI 1101&#34;

scsi&#40;2&#41;disk&#40;1&#41;rdisk&#40;0&#41;partition&#40;1&#41;\WINDOWS=&#34;XP SCSI 2101&#34;

Check that in the ROOT of the SCSI drive does exist a copy of the SCSI card driver xxxxxx.sys renamed as NTBOOTDD.SYS:

And see if any of them works.

Maybe the SCSI order is messed up by NTBOOTDD.SYS or NTDETECT.COM.

jaclaz

#12 gianni_trad

gianni_trad

    Member

  • Members
  • 46 posts
  • Location:Italy
  •  
    Italy

Posted 28 August 2008 - 08:01 PM

First thing try adding a few SCSI entries:
http://www.msfn.org/...ive-t25365.html

scsi&#40;0&#41;disk&#40;0&#41;rdisk&#40;0&#41;partition&#40;1&#41;\WINDOWS=&#34;XP SCSI 0001&#34;

scsi&#40;0&#41;disk&#40;1&#41;rdisk&#40;0&#41;partition&#40;1&#41;\WINDOWS=&#34;XP SCSI 0101&#34;

scsi&#40;1&#41;disk&#40;0&#41;rdisk&#40;0&#41;partition&#40;1&#41;\WINDOWS=&#34;XP SCSI 1001&#34;

scsi&#40;2&#41;disk&#40;0&#41;rdisk&#40;0&#41;partition&#40;1&#41;\WINDOWS=&#34;XP SCSI 2001&#34;

scsi&#40;0&#41;disk&#40;0&#41;rdisk&#40;1&#41;partition&#40;1&#41;\WINDOWS=&#34;XP SCSI 0011

scsi&#40;1&#41;disk&#40;0&#41;rdisk&#40;1&#41;partition&#40;1&#41;\WINDOWS=&#34;XP SCSI 1011&#34;

scsi&#40;2&#41;disk&#40;0&#41;rdisk&#40;1&#41;partition&#40;1&#41;\WINDOWS=&#34;XP SCSI 2011&#34;

scsi&#40;1&#41;disk&#40;1&#41;rdisk&#40;0&#41;partition&#40;1&#41;\WINDOWS=&#34;XP SCSI 1101&#34;

scsi&#40;2&#41;disk&#40;1&#41;rdisk&#40;0&#41;partition&#40;1&#41;\WINDOWS=&#34;XP SCSI 2101&#34;

Check that in the ROOT of the SCSI drive does exist a copy of the SCSI card driver xxxxxx.sys renamed as NTBOOTDD.SYS:

And see if any of them works.

Maybe the SCSI order is messed up by NTBOOTDD.SYS or NTDETECT.COM.

jaclaz



I just tried adding the scsi entries in the boot.ini file...

selecting the scsi entries appear a message (if i'm not wrong): disk not found / bad disk

Besides i've also tried to install Win XP SP2 from the Windows XP operating sistem in the SATA150 Hdd by executig this command:

f:\winnt32.exe /syspart:d

the program begin installation, then reboot

after the reboot, i set SCSI Hdd first boot diskdrive...

a menu TEXT appears with this only choice:

Installazione di Windows XP

I select it and the this error message appeared:

\$WIN_NT$.~BT\biosinfo.inf is bad or not present, error code: 43520

:whistling:

In the root of the SCSI Hdd i found NTDETECT.COM file.

By executing it, in NTFS4DOS mode and in Windows XP SATA installation, an error message appear... and show the CS IP OP adress

#13 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 29 August 2008 - 06:21 AM

ALL of the SCSI entries when selected give the same message? :whistling:

Did you check the presence of NTBOOTDD.SYS in ROOT of the SCSI drive and checked it is a copy of the actual proper .sys driver for your board?

In the root of the SCSI Hdd i found NTDETECT.COM file.

By executing it, in NTFS4DOS mode and in Windows XP SATA installation, an error message appear... and show the CS IP OP adress

NTDETECT.COM is NOT intended for direct execution, that is normal. ;)

We need to try something else.

Can you burn a CD?

Let's see if we can get Recovery console to work.

Use the batch by V.Laurie:
http://www.boot-land...?showtopic=2254

And create a Recovery Console .iso, burn it to CD.

Disconnect the SATA drive, try booting from the CD (pressing F6 at boot, feeding it the SCSI drivers and selecting NOT to setup windows, but rather to Recovery).

What happens?

jaclaz

#14 gianni_trad

gianni_trad

    Member

  • Members
  • 46 posts
  • Location:Italy
  •  
    Italy

Posted 29 August 2008 - 07:22 AM

ALL of the SCSI entries when selected give the same message? :whistling:


Yes ;)

u check the presence of NTBOOTDD.SYS in ROOT of the SCSI drive and checked it is a copy of the actual proper .sys driver for your board?


In the SCSI ROOT NTBOOTDD.SYS in NOT present, it's present only NTDETECT.COM (hidden file)



OM is NOT intended for direct execution, that is normal. ;)

We need to try something else.

Can you burn a CD?


Yes, in the new Windows XP Installation on the SATA Hdd I've installed Nero too.

Let's see if we can get Recovery console to work.

Use the batch by V.Laurie:
http://www.boot-land...?showtopic=2254

And create a Recovery Console .iso, burn it to CD.

Disconnect the SATA drive, try booting from the CD (pressing F6 at boot, feeding it the SCSI drivers and selecting NOT to setup windows, but rather to Recovery).

What happens?

jaclaz


I've already (without batch by V.Laurie) tried disconecting SATA drive, Booting from Windows XP CD, pressing F6, and then pressing R for Recovery console.

This happens: C:\WINDOWS> prompt

and the C: Hdd (SCSI) seems working right.

for example, by executing CHKDSK it's all ok.

Do I have to try with batch by V.Laurie?

#15 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 29 August 2008 - 11:34 AM

In the SCSI ROOT NTBOOTDD.SYS in NOT present, it's present only NTDETECT.COM (hidden file)

Ok, as said it is NEEDED that you copy to the ROOT of the SCSI drive the appropriate driver for the SCSI card and rename it to NTBOOTDD.SYS.

Take some time to read the MS KB referenced in the thread I referenced before:
http://www.msfn.org/...ive-t25365.html
this KB:
http://support.micro...b;en-us;q102873

You cannot boot a SCSI disk without the driver, when you give it with F6 and floppy it is "temporary", the Windows setup should copy it to both the %SystemRoot%\System32\drivers\ and the ROOT of the first active primary partition of first hard disk, renaming it to NTBOOTDD.SYS and adding the needed Registry entries.

It is possible that this has failed in your case, for reasons yet to be found. :whistling:


Yes, in the new Windows XP Installation on the SATA Hdd I've installed Nero too.

Good, though Nero is a bit of overkill to just burn a .iso...;)

I've already (without batch by V.Laurie) tried disconecting SATA drive, Booting from Windows XP CD, pressing F6, and then pressing R for Recovery console.

This happens: C:\WINDOWS> prompt

and the C: Hdd (SCSI) seems working right.

for example, by executing CHKDSK it's all ok.

Do I have to try with batch by V.Laurie?


No, it was just a way to check that you could boot through RC to the SCSI HD with F6 and with the SATA drive disconnected, if needed I will guide you through the building of a more featured CD.

But until we do not have a confirmation that you have the proper NTBOOTDD.SYS, no further steps are possible.

To recap booting process (when using SCSI hardware and scsi() syntax):
1) Motherboard BIOS loads BIOS extension in the SCSI card then chainloads the MBR of the first drive (as seen by BIOSes)
2) the MBR chainloads the partition Bootsector of the Active Primary partition it finds on first drive (again as seen by BIOS)
3) the Bootsector chainloads NTLDR
4) NTLDR loads BOOT.INI
5) the user chooses one of the entries in BOOT.INI
6) NTLDR then loads NTDETECT.COM and, in the case of a scsi() entry, loads whatever NTBOOTDD.SYS file it finds in the ROOT of the same drive and partition where NTLDR, NTDETECT.COM and BOOT.INI are and uses it to access the drive
7) Windows starts booting

From the cited KB - about multi() syntax:

Theoretically, this syntax could be used to start Windows NT on any drive in the system. However, this would require that all drives are correctly identified through the standard INT 13 interface; since support for this varies from disk controller to disk controller and most system BIOS only identify a single disk controller through INT 13, in practice it is only safe to use this syntax to start Windows NT from the first two drives connected to the primary disk controller, or the first four drives in the case of a dual-channel EIDE controller.

In a pure IDE system, the MULTI() syntax will work for up to the four drives maximum on the primary and secondary channels of a dual-channel controller.

In a pure SCSI system, the MULTI() syntax will work for the first two drives on the first SCSI controller (that is, the controller whose BIOS loads first).

In a mixed SCSI and IDE system, the MULTI() syntax will work only for the IDE drives on the first controller.


You can see how the multi() syntax is prone to fail in some cases when SCSI hardware is used, on the other hand, another exerpt from same KB about scsi() syntax:

The SCSI() syntax is used on both RISC and x86-based computers and is used in all versions of Windows NT. Using SCSI() notation indicates that Windows NT will load a boot device driver and use that driver to access the boot partition.

On an x86-based computer, the device driver used is NTBOOTDD.SYS, which can be found in the root of the system drive (generally of drive C) and is a copy of the device driver for the drive controller in use.

.....

When using SCSI() notation the value of X depends upon NTBOOTDD.SYS. Each SCSI driver under Windows NT has its own method of ordering controllers, although generally they conform to the order that the BIOS on the controllers load (that is, if the BIOS is loaded).

scsi() syntax NEEDS the driver NTBOOTDD.SYS and it is possible that the drive order is DIFFERENT from what reported by BIOS, thus different X,Y,Z,W values may be needed.

In other words, when booting from CD:
A.1) up to the "blue screen" of SETUP (where you press F6 to add the driver from floppy) the SCSI disk is accessed in "Real" mode through BIOS interrupts
A.2) after you have pressed "R" for Recovery Console, or went on with SETUP for installing, the SCSI disk is accessed through the driver loaded with F6+floppy

When (hopefully ;)) Windows is properly installed, a similar process applies,
B.1) up to BOOT.INI choices the SCSI disk is accessed in "Real" mode through BIOS interrupts
B.2) after a choice has been made, the SCSI disk is accessed through the NTBOOTDD.SYS driver
B.3) at a certain point of the windows loading, the actual SCSI .sys driver in %SystemRoot%\System32\drivers\ is loaded, "swapping" with the NTBOOTDD.SYS driver.

It seems like you miss the B.2) part, without which it is not possible to fill the gap between B.1) and B.3) above.

jaclaz

#16 gianni_trad

gianni_trad

    Member

  • Members
  • 46 posts
  • Location:Italy
  •  
    Italy

Posted 29 August 2008 - 05:42 PM

I've just tried copying adpu320.sys (driver Adaptec 29320LPE SCSI Controller) to the ROOT of the SCSI Hdd.

Then I renamed it into NTBOOTDD.SYS

but the same message appear.

Are we sure that my ntldr is loading NTBOOTDD.SYS too?

#17 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 29 August 2008 - 07:04 PM

I've just tried copying adpu320.sys (driver Adaptec 29320LPE SCSI Controller) to the ROOT of the SCSI Hdd.

Then I renamed it into NTBOOTDD.SYS

but the same message appear.


Which one?

the "\$WIN_NT$.~BT\biosinfo.inf is bad or not present, error code: 43520"

or the "\WINDOWS\INF\biosinfo.inf file not present or damaged... (ecc)"


And the same message with any of the multi() or scsi() entries?

Are we sure that my ntldr is loading NTBOOTDD.SYS too?

Sure, unless you have a "special" NTLDR, but I'm confused about at what "level" the install goes without errors and what files are actually on the drive when the install fails.


This cannot possibly work:

f:\winnt32.exe /syspart:d

the program begin installation, then reboot

after the reboot, i set SCSI Hdd first boot diskdrive...


You cannot use the /syspart WITHOUT the /tempdrive switch:
http://www.microsoft...y.mspx?mfr=true

Make another attempt, first format again the SCSI disk, just to make sure that there are no "leftovers" then run WINNT32.EXE this time with:
f:\winnt32.exe /syspart:d /tempdrive:d /noreboot
and after setup finishes, check what has been copied to the SCSI drive ROOT, before changing the BIOS order and try booting without the SATA drive connected.
(assumimg that "d" is the right drive letter for the Active partition on the SCSI disk)

If the above does not work we must change approach.

I need some more info.

Is the SATA drive "expendable"? (in the sense that can it be formatted and Windows re-installed to it?) don't worry, it won't be ruined in the process.

Can I assume that the SCSI drive (once hopefully we will find the way to install Windows on it) will be the "main" drive of the system ? (in other words is it the one on which at least the boot partition - the one that usually gets drive letter C: - will be?)

Are you OK with a partitioning scheme similar to the one I normally use, i.e. smallish FAT 16 partition at the beginning of the drive Active with Windows boot files and all the rest in a Logical Volume inside Extended?
See here:
http://www.boot-land...opic=4900&st=90

jaclaz

#18 gianni_trad

gianni_trad

    Member

  • Members
  • 46 posts
  • Location:Italy
  •  
    Italy

Posted 30 August 2008 - 01:12 AM

Which one?

the "\$WIN_NT$.~BT\biosinfo.inf is bad or not present, error code: 43520"

or the "\WINDOWS\INF\biosinfo.inf file not present or damaged... (ecc)"


And the same message with any of the multi() or scsi() entries?


The error message is: \WINDOWS\INF\biosinfo.inf not present or damaged.

This happens with the "multi" entries

between the choice "multi" and the message error, for about ten seconds, the SCSI Hdd activity LED lamps for 0,5 second evry two seconds... then the error message appear.

Instead, selecting the scsi entries, immediatly appears the other message: bad disk drive/problem with hard disk (without any lamps of the activity LED)

Sure, unless you have a "special" NTLDR, but I'm confused about at what "level" the install goes without errors and what files are actually on the drive when the install fails.


This cannot possibly work:


You cannot use the /syspart WITHOUT the /tempdrive switch:
http://www.microsoft...y.mspx?mfr=true

Make another attempt, first format again the SCSI disk, just to make sure that there are no "leftovers" then run WINNT32.EXE this time with:
f:\winnt32.exe /syspart:d /tempdrive:d /noreboot
and after setup finishes, check what has been copied to the SCSI drive ROOT, before changing the BIOS order and try booting without the SATA drive connected.
(assumimg that "d" is the right drive letter for the Active partition on the SCSI disk)

If the above does not work we must change approach.

I need some more info.


Ok, tomorrow i'll try this.

Is the SATA drive "expendable"? (in the sense that can it be formatted and Windows re-installed to it?) don't worry, it won't be ruined in the process.


Yes, the SATA Hdd is divided in two NTFS partitions:

in the first one there is Windows XP installation and can be formatted

in the second one there are the "source program file" ...this partition can't be formatted

Can I assume that the SCSI drive (once hopefully we will find the way to install Windows on it) will be the "main" drive of the system ? (in other words is it the one on which at least the boot partition - the one that usually gets drive letter C: - will be?)


Yes! :whistling:

Are you OK with a partitioning scheme similar to the one I normally use, i.e. smallish FAT 16 partition at the beginning of the drive Active with Windows boot files and all the rest in a Logical Volume inside Extended?
See here:
http://www.boot-land...opic=4900&st=90

jaclaz


If it's Ok for you, it's Ok for me too! ;)

You are great, I blindly trust in you ;)

#19 gianni_trad

gianni_trad

    Member

  • Members
  • 46 posts
  • Location:Italy
  •  
    Italy

Posted 31 August 2008 - 09:42 AM

Hi all :whistling:

Jac, I've tried installing from SATA Hdd XP installation, by using execute f:\i386\winnt32.exe /syspart:d /tempdrive:d /noreboot


those are the results:

SCSI Hdd ROOT contains: (between [] means it's a directory)

[System Volume Information]

bootfont.bin

ntdetect.com

ntldr

boot.ini

[$WIN_NT$.~BT]

txtsetup.sif


So, i've added to the ROOT adpu320.sys and renamed to NTBOOT.SYS, then I reboot the machine.

I've changed the Boot sequence in the Motherboard BIOS, selecting the SCSCI Hdd as first Drive to boot.

At the Boot, a message appear:

"Verifica configurazione Hardware in corso.... "

this message remains for 2 seconds, then it disappears.

then, after about 6-7 seconds of Black screen, an ERROR message appear:

Impossibile caricare il file \$WIN_NT$.~BT\biosinfo.inf
codice errore: 43520


impossibile continuare l'installazione, premere un tasto per riavviare.

;)

#20 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 31 August 2008 - 11:44 AM

Ok. (well, actually NOT ok, but we must keep a positive attitude :whistling: )

Were you asked at some point to "Press F6" or however to give the drivers on floppy?

Can you post the current contents of BOOT.INI?

Can you check that in the $WIN_NT$.~BT folder the driver files adpu320.sys, adpu320.inf. etc. are present?

Are you familiar with nlite?
(next try I would make would be to integrate the SCSI drivers in the source, nlite is a good, easy application to do that, but if you use other ones it's OK)

jaclaz

#21 gianni_trad

gianni_trad

    Member

  • Members
  • 46 posts
  • Location:Italy
  •  
    Italy

Posted 31 August 2008 - 12:41 PM

Ok. (well, actually NOT ok, but we must keep a positive attitude :whistling: )

Were you asked at some point to "Press F6" or however to give the drivers on floppy?


No, I wasn't asked to press F6 even to give the drivers from floppy disk.


Can you post the current contents of BOOT.INI?


Yes ;)

here is BOOT.INI of the SCSI Hdd:

[Boot Loader]
Timeout=5
Default=C:\$WIN_NT$.~BT\BOOTSECT.DAT
[Operating Systems]
C:\$WIN_NT$.~BT\BOOTSECT.DAT="Installazione di Windows"

Can you check that in the $WIN_NT$.~BT folder the driver files adpu320.sys, adpu320.inf. etc. are present?


I've just checked that folder:

adpu320.sys either adpu320.inf are NOT present in that folder.

the only file similar that is present is: adpu160m.sy_

But it's dated 02-03-2006 and I think this is a standard driver included in Windows XP SP2 CD installation

Are you familiar with nlite?
(next try I would make would be to integrate the SCSI drivers in the source, nlite is a good, easy application to do that, but if you use other ones it's OK)

jaclaz


I'm not actually familar with nlite, but I can quickly learn if it's needed ;)

#22 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 31 August 2008 - 01:29 PM

Ok, first thing, let's see if we can have the XP install on SATA hard disk boot normally from the SCSI drive, leaving it as first boot drive, add to the BOOT.INI on the SCSI drive these lines:
multi&#40;0&#41;disk&#40;0&#41;rdisk&#40;1&#41;partition&#40;1&#41;\WINDOWS=&#34;XP SATA 0011&#34; /noexecute=optin /fastdetect

multi&#40;0&#41;disk&#40;0&#41;rdisk&#40;2&#41;partition&#40;1&#41;\WINDOWS=&#34;XP SATA 0021&#34; /noexecute=optin /fastdetect
(first one should work)

I'm not actually familar with nlite, but I can quickly learn if it's needed

Hmmm, no doubt about that, but maybe it would be an overkill for our present scope, that is only that of integrating a driver.

Get nlite:
http://www.nliteos.com/
and check this italian guide:
http://www.hwupgrade...d.php?t=1383206

Most of it will NOT be used at this moment, just point 8), which links to this thread:
http://www.hwupgrade...threadid=795886
links to grenmachine site are obsolete, so get them through the wayback machine:

http://web.archive.o...ING/addraid.htm

Unfortunately there is not a pre-made text to add TXTSETUP.SIF among the ones in XPCREATE.CAB:
http://web.archive.o...IN/XPCREATE.CAB

This should do for you:
&#91;SourceDisksFiles&#93; 

adpu320.sys = 1,,,,,,3_,4,1 



&#91;HardwareIdsDatabase&#93;

PCI\VEN_9005&DEV_801D = &#34;adpu320&#34;

PCI\VEN_9005&DEV_801E = &#34;adpu320&#34;

PCI\VEN_9005&DEV_801F = &#34;adpu320&#34;

PCI\VEN_9005&DEV_800F = &#34;adpu320&#34;

PCI\VEN_9005&DEV_800F&SUBSYS_005F9005 = &#34;adpu320&#34;

PCI\VEN_9005&DEV_8000&SUBSYS_00609005 = &#34;adpu320&#34;

PCI\VEN_9005&DEV_8010&SUBSYS_00409005 = &#34;adpu320&#34;

PCI\VEN_9005&DEV_8011&SUBSYS_00419005 = &#34;adpu320&#34;

PCI\VEN_9005&DEV_8012&SUBSYS_00429005 = &#34;adpu320&#34;

PCI\VEN_9005&DEV_8014&SUBSYS_00449005 = &#34;adpu320&#34;

PCI\VEN_9005&DEV_8015&SUBSYS_00409005 = &#34;adpu320&#34;

PCI\VEN_9005&DEV_8016&SUBSYS_00409005 = &#34;adpu320&#34;

PCI\VEN_9005&DEV_8017&SUBSYS_00449005 = &#34;adpu320&#34;

PCI\VEN_9005&DEV_8017&SUBSYS_00459005 = &#34;adpu320&#34; 



&#91;SCSI.load&#93; 

adpu320 = adpu320.sys,4 



&#91;SCSI&#93; 

adpu320 = &#34;Adaptec SCSI Card 29320LPE - Ultra320 SCSI&#34;

Post if anything is not clear.

jaclaz

#23 gianni_trad

gianni_trad

    Member

  • Members
  • 46 posts
  • Location:Italy
  •  
    Italy

Posted 31 August 2008 - 02:03 PM

Ok, first thing, let's see if we can have the XP install on SATA hard disk boot normally from the SCSI drive, leaving it as first boot drive, add to the BOOT.INI on the SCSI drive these lines:

multi&#40;0&#41;disk&#40;0&#41;rdisk&#40;1&#41;partition&#40;1&#41;\WINDOWS=&#34;XP SATA 0011&#34; /noexecute=optin /fastdetect

multi&#40;0&#41;disk&#40;0&#41;rdisk&#40;2&#41;partition&#40;1&#41;\WINDOWS=&#34;XP SATA 0021&#34; /noexecute=optin /fastdetect
(first one should work)



i've just added that lines in the Boot.ini of the SCSI Hdd and reboot froms SCSI Hdd...

this is my actually SCSI Hdd BOOT.INI:

[Boot Loader]
Timeout=10
Default=C:\$WIN_NT$.~BT\BOOTSECT.DAT
[Operating Systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="XP SATA 0011" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="XP SATA 0021" /noexecute=optin /fastdetect
C:\$WIN_NT$.~BT\BOOTSECT.DAT="Installazione di Windows"


But at the reboot the system doesn't ask me anything, it run directly to "Verifica configurazione Hardware in corso...." anf then to the error message:
Impossibile caricare il file \$WIN_NT$.~BT\biosinfo.inf
codice errore: 43520

:whistling:

#24 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 31 August 2008 - 02:48 PM

You mean that you cannot see the choices in BOOT.INI? :whistling:

Check the size of the NTLDR file that you have in ROOT of the SCSI disk against the size of the NTLDR file you have on your SATA disk (and against the size of the files NTLDR and SETUPLDR.BIN that you have on your CD).

Try copying the NTLDR file from CD (or from SATA, they should be exactly the same) to the SCSI disk.


jaclaz

#25 gianni_trad

gianni_trad

    Member

  • Members
  • 46 posts
  • Location:Italy
  •  
    Italy

Posted 31 August 2008 - 03:45 PM

Yes, i can't see the choice of Boot.ini! it run without ask anything!

However here are file sizes:

NTLDR (SCSI ROOT) 256KB

NTLDR (SATA ROOT) 246KB

NTLDR (\i386\ installation CD) 246KB

:whistling:




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users