Unattended W2K Server install using RIS, trying to load CPQ smartarray 5i controller drivers, fails with "file txtsetup.oem caused unexpected error (21) at line 1041 in f:
tprivate
tosootsetupoemdisk.c."
Have tried many combinations of [massstoragedrivers], [oembootfiles] and txtsetup.oem - same results. Anyone seen this before?
shovel204
06-13-2002, 11:09 PM
I haven't tried that particular driver, but did you put the drivers in the two or three folders that it calls for? It has been awhile since I did the RIS with adding mass storage drivers and chipset drivers. I did have to put the textsetup.oem file in, but if I remember correctly I also had to put the files in at least one other place I just cannot remember the exact details.
The line error kind of points to a syntax problem with that line.It might need quotation marks around the path. I had to fix a line a few times till I got it right. If it fails and points to that line as the failure point check what is listed for that line.
------------
tk at 6/13/2002 10:02:18 AM
Unattended W2K Server install using RIS, trying to load CPQ smartarray 5i controller drivers, fails with "file txtsetup.oem caused unexpected error (21) at line 1041 in f:
tprivate
tosootsetupoemdisk.c."
Have tried many combinations of [massstoragedrivers], [oembootfiles] and txtsetup.oem - same results. Anyone seen this before?
06-14-2002, 10:12 AM
Thnx for the response...I believe it's a syntax problem also. I've got the filenames in [oembootfiles] and the cpq drivers and *.oem file in $oem$ extmode...fairly straightforward.
Don't know though what this is pointing to: f:
tprivate
tosootsetupoemdisk.c??? Any idea? Also this line in txtsetup.oem is suspect...d1 = "Compaq Smart Array 5i, 532, 5312 Controllers",txtsetup.oem,. Tough to pin down correct format however. Kind of strange, since all works fine if I hit F6 and give it same files on diskette.
Have you gotten this to work using the [massstoragedrivers] option? I suspect also that this section of the *.sif could be the issue.
------------
shovel204 at 6/14/2002 12:09:34 AM
I haven't tried that particular driver, but did you put the drivers in the two or three folders that it calls for? It has been awhile since I did the RIS with adding mass storage drivers and chipset drivers. I did have to put the textsetup.oem file in, but if I remember correctly I also had to put the files in at least one other place I just cannot remember the exact details.
The line error kind of points to a syntax problem with that line.It might need quotation marks around the path. I had to fix a line a few times till I got it right. If it fails and points to that line as the failure point check what is listed for that line.
------------
tk at 6/13/2002 10:02:18 AM
Unattended W2K Server install using RIS, trying to load CPQ smartarray 5i controller drivers, fails with "file txtsetup.oem caused unexpected error (21) at line 1041 in f:
tprivate
tosootsetupoemdisk.c."
Have tried many combinations of [massstoragedrivers], [oembootfiles] and txtsetup.oem - same results. Anyone seen this before?
tk
06-14-2002, 10:13 AM
Thnx for the response...I believe it's a syntax problem also. I've got the filenames in [oembootfiles] and the cpq drivers and *.oem file in $oem$ extmode...fairly straightforward.
Don't know though what this is pointing to: f:
tprivate
tosootsetupoemdisk.c??? Any idea? Also this line in txtsetup.oem is suspect...d1 = "Compaq Smart Array 5i, 532, 5312 Controllers",txtsetup.oem,. Tough to pin down correct format however. Kind of strange, since all works fine if I hit F6 and give it same files on diskette.
Have you gotten this to work using the [massstoragedrivers] option? I suspect also that this section of the *.sif could be the issue
------------
at 6/14/2002 11:12:03 AM
Thnx for the response...I believe it's a syntax problem also. I've got the filenames in [oembootfiles] and the cpq drivers and *.oem file in $oem$ extmode...fairly straightforward.
Don't know though what this is pointing to: f:
tprivate
tosootsetupoemdisk.c??? Any idea? Also this line in txtsetup.oem is suspect...d1 = "Compaq Smart Array 5i, 532, 5312 Controllers",txtsetup.oem,. Tough to pin down correct format however. Kind of strange, since all works fine if I hit F6 and give it same files on diskette.
Have you gotten this to work using the [massstoragedrivers] option? I suspect also that this section of the *.sif could be the issue.
------------
shovel204 at 6/14/2002 12:09:34 AM
I haven't tried that particular driver, but did you put the drivers in the two or three folders that it calls for? It has been awhile since I did the RIS with adding mass storage drivers and chipset drivers. I did have to put the textsetup.oem file in, but if I remember correctly I also had to put the files in at least one other place I just cannot remember the exact details.
The line error kind of points to a syntax problem with that line.It might need quotation marks around the path. I had to fix a line a few times till I got it right. If it fails and points to that line as the failure point check what is listed for that line.
------------
tk at 6/13/2002 10:02:18 AM
Unattended W2K Server install using RIS, trying to load CPQ smartarray 5i controller drivers, fails with "file txtsetup.oem caused unexpected error (21) at line 1041 in f:
tprivate
tosootsetupoemdisk.c."
Have tried many combinations of [massstoragedrivers], [oembootfiles] and txtsetup.oem - same results. Anyone seen this before?
shovel204
06-14-2002, 12:33 PM
Does f:
tprivate
tosootsetupoemdisk.c??? exist and is it shared? I had all my mass storage drivers in the same folder as the rest of the image files.http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q288344&
------------
tk at 6/14/2002 11:13:55 AM
Thnx for the response...I believe it's a syntax problem also. I've got the filenames in [oembootfiles] and the cpq drivers and *.oem file in $oem$ extmode...fairly straightforward.
Don't know though what this is pointing to: f:
tprivate
tosootsetupoemdisk.c??? Any idea? Also this line in txtsetup.oem is suspect...d1 = "Compaq Smart Array 5i, 532, 5312 Controllers",txtsetup.oem,. Tough to pin down correct format however. Kind of strange, since all works fine if I hit F6 and give it same files on diskette.
Have you gotten this to work using the [massstoragedrivers] option? I suspect also that this section of the *.sif could be the issue
------------
at 6/14/2002 11:12:03 AM
Thnx for the response...I believe it's a syntax problem also. I've got the filenames in [oembootfiles] and the cpq drivers and *.oem file in $oem$ extmode...fairly straightforward.
Don't know though what this is pointing to: f:
tprivate
tosootsetupoemdisk.c??? Any idea? Also this line in txtsetup.oem is suspect...d1 = "Compaq Smart Array 5i, 532, 5312 Controllers",txtsetup.oem,. Tough to pin down correct format however. Kind of strange, since all works fine if I hit F6 and give it same files on diskette.
Have you gotten this to work using the [massstoragedrivers] option? I suspect also that this section of the *.sif could be the issue.
------------
shovel204 at 6/14/2002 12:09:34 AM
I haven't tried that particular driver, but did you put the drivers in the two or three folders that it calls for? It has been awhile since I did the RIS with adding mass storage drivers and chipset drivers. I did have to put the textsetup.oem file in, but if I remember correctly I also had to put the files in at least one other place I just cannot remember the exact details.
The line error kind of points to a syntax problem with that line.It might need quotation marks around the path. I had to fix a line a few times till I got it right. If it fails and points to that line as the failure point check what is listed for that line.
------------
tk at 6/13/2002 10:02:18 AM
Unattended W2K Server install using RIS, trying to load CPQ smartarray 5i controller drivers, fails with "file txtsetup.oem caused unexpected error (21) at line 1041 in f:
tprivate
tosootsetupoemdisk.c."
Have tried many combinations of [massstoragedrivers], [oembootfiles] and txtsetup.oem - same results. Anyone seen this before?
tk
06-14-2002, 02:14 PM
I've read that article many times, like I said, looks pretty straightforward! As the article states, I put the drivers in
i386$oem$ extmode. You put them directly in i386?
Also, I don't know what the f:
t...oemdisk.c is referencing... this is a RIS install using PXE boot NICs, so no idea what the reference to f: is, unfortunately...
As a test, tried an unattended install using bootable W2K Server CD, with the cpq drivers, and winnt.sif on a diskette...same error message.
You've gotten this to work?
------------
shovel204 at 6/14/2002 1:33:25 PM
Does f:
tprivate
tosootsetupoemdisk.c??? exist and is it shared? I had all my mass storage drivers in the same folder as the rest of the image files.http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q288344&
------------
tk at 6/14/2002 11:13:55 AM
Thnx for the response...I believe it's a syntax problem also. I've got the filenames in [oembootfiles] and the cpq drivers and *.oem file in $oem$ extmode...fairly straightforward.
Don't know though what this is pointing to: f:
tprivate
tosootsetupoemdisk.c??? Any idea? Also this line in txtsetup.oem is suspect...d1 = "Compaq Smart Array 5i, 532, 5312 Controllers",txtsetup.oem,. Tough to pin down correct format however. Kind of strange, since all works fine if I hit F6 and give it same files on diskette.
Have you gotten this to work using the [massstoragedrivers] option? I suspect also that this section of the *.sif could be the issue
------------
at 6/14/2002 11:12:03 AM
Thnx for the response...I believe it's a syntax problem also. I've got the filenames in [oembootfiles] and the cpq drivers and *.oem file in $oem$ extmode...fairly straightforward.
Don't know though what this is pointing to: f:
tprivate
tosootsetupoemdisk.c??? Any idea? Also this line in txtsetup.oem is suspect...d1 = "Compaq Smart Array 5i, 532, 5312 Controllers",txtsetup.oem,. Tough to pin down correct format however. Kind of strange, since all works fine if I hit F6 and give it same files on diskette.
Have you gotten this to work using the [massstoragedrivers] option? I suspect also that this section of the *.sif could be the issue.
------------
shovel204 at 6/14/2002 12:09:34 AM
I haven't tried that particular driver, but did you put the drivers in the two or three folders that it calls for? It has been awhile since I did the RIS with adding mass storage drivers and chipset drivers. I did have to put the textsetup.oem file in, but if I remember correctly I also had to put the files in at least one other place I just cannot remember the exact details.
The line error kind of points to a syntax problem with that line.It might need quotation marks around the path. I had to fix a line a few times till I got it right. If it fails and points to that line as the failure point check what is listed for that line.
------------
tk at 6/13/2002 10:02:18 AM
Unattended W2K Server install using RIS, trying to load CPQ smartarray 5i controller drivers, fails with "file txtsetup.oem caused unexpected error (21) at line 1041 in f:
tprivate
tosootsetupoemdisk.c."
Have tried many combinations of [massstoragedrivers], [oembootfiles] and txtsetup.oem - same results. Anyone seen this before?
shovel204
06-14-2002, 03:38 PM
Yes I did get it to work, unfortunately that was during my practicum (just graduated from college)I had set up the RIS for their w2k domain rollout, and I did not keep a copy of the documentation at home.I if I remember correctly had them in the textmode folder and in the $oem$\%1driversmass storage folder I had created.I am sure I had it put somewhere else as well.We had Intel NIC's so had to add drivers for those as well.I will look for any documents I kept to see if I can find them.
------------
tk at 6/14/2002 3:14:18 PM
I've read that article many times, like I said, looks pretty straightforward! As the article states, I put the drivers in
i386$oem$ extmode. You put them directly in i386?
Also, I don't know what the f:
t...oemdisk.c is referencing... this is a RIS install using PXE boot NICs, so no idea what the reference to f: is, unfortunately...
As a test, tried an unattended install using bootable W2K Server CD, with the cpq drivers, and winnt.sif on a diskette...same error message.
You've gotten this to work?
------------
shovel204 at 6/14/2002 1:33:25 PM
Does f:
tprivate
tosootsetupoemdisk.c??? exist and is it shared? I had all my mass storage drivers in the same folder as the rest of the image files.http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q288344&
------------
tk at 6/14/2002 11:13:55 AM
Thnx for the response...I believe it's a syntax problem also. I've got the filenames in [oembootfiles] and the cpq drivers and *.oem file in $oem$ extmode...fairly straightforward.
Don't know though what this is pointing to: f:
tprivate
tosootsetupoemdisk.c??? Any idea? Also this line in txtsetup.oem is suspect...d1 = "Compaq Smart Array 5i, 532, 5312 Controllers",txtsetup.oem,. Tough to pin down correct format however. Kind of strange, since all works fine if I hit F6 and give it same files on diskette.
Have you gotten this to work using the [massstoragedrivers] option? I suspect also that this section of the *.sif could be the issue
------------
at 6/14/2002 11:12:03 AM
Thnx for the response...I believe it's a syntax problem also. I've got the filenames in [oembootfiles] and the cpq drivers and *.oem file in $oem$ extmode...fairly straightforward.
Don't know though what this is pointing to: f:
tprivate
tosootsetupoemdisk.c??? Any idea? Also this line in txtsetup.oem is suspect...d1 = "Compaq Smart Array 5i, 532, 5312 Controllers",txtsetup.oem,. Tough to pin down correct format however. Kind of strange, since all works fine if I hit F6 and give it same files on diskette.
Have you gotten this to work using the [massstoragedrivers] option? I suspect also that this section of the *.sif could be the issue.
------------
shovel204 at 6/14/2002 12:09:34 AM
I haven't tried that particular driver, but did you put the drivers in the two or three folders that it calls for? It has been awhile since I did the RIS with adding mass storage drivers and chipset drivers. I did have to put the textsetup.oem file in, but if I remember correctly I also had to put the files in at least one other place I just cannot remember the exact details.
The line error kind of points to a syntax problem with that line.It might need quotation marks around the path. I had to fix a line a few times till I got it right. If it fails and points to that line as the failure point check what is listed for that line.
------------
tk at 6/13/2002 10:02:18 AM
Unattended W2K Server install using RIS, trying to load CPQ smartarray 5i controller drivers, fails with "file txtsetup.oem caused unexpected error (21) at line 1041 in f:
tprivate
tosootsetupoemdisk.c."
Have tried many combinations of [massstoragedrivers], [oembootfiles] and txtsetup.oem - same results. Anyone seen this before?
tk
06-14-2002, 04:27 PM
Thnx again. Would be interested in anything you can find...
------------
shovel204 at 6/14/2002 4:38:54 PM
Yes I did get it to work, unfortunately that was during my practicum (just graduated from college)I had set up the RIS for their w2k domain rollout, and I did not keep a copy of the documentation at home.I if I remember correctly had them in the textmode folder and in the $oem$\%1driversmass storage folder I had created.I am sure I had it put somewhere else as well.We had Intel NIC's so had to add drivers for those as well.I will look for any documents I kept to see if I can find them.
------------
tk at 6/14/2002 3:14:18 PM
I've read that article many times, like I said, looks pretty straightforward! As the article states, I put the drivers in
i386$oem$ extmode. You put them directly in i386?
Also, I don't know what the f:
t...oemdisk.c is referencing... this is a RIS install using PXE boot NICs, so no idea what the reference to f: is, unfortunately...
As a test, tried an unattended install using bootable W2K Server CD, with the cpq drivers, and winnt.sif on a diskette...same error message.
You've gotten this to work?
------------
shovel204 at 6/14/2002 1:33:25 PM
Does f:
tprivate
tosootsetupoemdisk.c??? exist and is it shared? I had all my mass storage drivers in the same folder as the rest of the image files.http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q288344&
------------
tk at 6/14/2002 11:13:55 AM
Thnx for the response...I believe it's a syntax problem also. I've got the filenames in [oembootfiles] and the cpq drivers and *.oem file in $oem$ extmode...fairly straightforward.
Don't know though what this is pointing to: f:
tprivate
tosootsetupoemdisk.c??? Any idea? Also this line in txtsetup.oem is suspect...d1 = "Compaq Smart Array 5i, 532, 5312 Controllers",txtsetup.oem,. Tough to pin down correct format however. Kind of strange, since all works fine if I hit F6 and give it same files on diskette.
Have you gotten this to work using the [massstoragedrivers] option? I suspect also that this section of the *.sif could be the issue
------------
at 6/14/2002 11:12:03 AM
Thnx for the response...I believe it's a syntax problem also. I've got the filenames in [oembootfiles] and the cpq drivers and *.oem file in $oem$ extmode...fairly straightforward.
Don't know though what this is pointing to: f:
tprivate
tosootsetupoemdisk.c??? Any idea? Also this line in txtsetup.oem is suspect...d1 = "Compaq Smart Array 5i, 532, 5312 Controllers",txtsetup.oem,. Tough to pin down correct format however. Kind of strange, since all works fine if I hit F6 and give it same files on diskette.
Have you gotten this to work using the [massstoragedrivers] option? I suspect also that this section of the *.sif could be the issue.
------------
shovel204 at 6/14/2002 12:09:34 AM
I haven't tried that particular driver, but did you put the drivers in the two or three folders that it calls for? It has been awhile since I did the RIS with adding mass storage drivers and chipset drivers. I did have to put the textsetup.oem file in, but if I remember correctly I also had to put the files in at least one other place I just cannot remember the exact details.
The line error kind of points to a syntax problem with that line.It might need quotation marks around the path. I had to fix a line a few times till I got it right. If it fails and points to that line as the failure point check what is listed for that line.
------------
tk at 6/13/2002 10:02:18 AM
Unattended W2K Server install using RIS, trying to load CPQ smartarray 5i controller drivers, fails with "file txtsetup.oem caused unexpected error (21) at line 1041 in f:
tprivate
tosootsetupoemdisk.c."
Have tried many combinations of [massstoragedrivers], [oembootfiles] and txtsetup.oem - same results. Anyone seen this before?
Matt Winer
06-21-2002, 12:47 PM
tk,
I was wondering if you had figured this out yet. I am going through the same exact thing now. I have the same error, and I can't figure it out.
Thanks
Matt
------------
tk at 6/13/2002 10:02:18 AM
Unattended W2K Server install using RIS, trying to load CPQ smartarray 5i controller drivers, fails with "file txtsetup.oem caused unexpected error (21) at line 1041 in f:
tprivate
tosootsetupoemdisk.c."
Have tried many combinations of [massstoragedrivers], [oembootfiles] and txtsetup.oem - same results. Anyone seen this before?
shovel204
06-21-2002, 02:44 PM
http://www.jsifaq.com/subh/tip3500/rh3518.htm
http://support.microsoft.com/default.aspx?scid=kb;EN-CA;q288344
------------
tk at 6/13/2002 10:02:18 AM
Unattended W2K Server install using RIS, trying to load CPQ smartarray 5i controller drivers, fails with "file txtsetup.oem caused unexpected error (21) at line 1041 in f:
tprivate
tosootsetupoemdisk.c."
Have tried many combinations of [massstoragedrivers], [oembootfiles] and txtsetup.oem - same results. Anyone seen this before?
Serverwatch.com
Copyright Internet.com Inc. All Rights Reserved.