This is how I always build my boxes, Day 0, set_letterbug, Commit. -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Johnson, Alex (Foxboro) Sent: Tuesday, March 08, 2005 5:37 PM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] WP51D Stand-alone Isn't there a tool - setletterbug - that makes this possible? You run it = and it sets the litterbug such that the DNBT is not necessary. Sorry I can't remember exactly. Regards, =20 Alex Johnson Invensys Process Systems Invensys Systems, Inc. 10707 Haddington Houston, TX 77043 713.722.2859 (voice) 713.722.2700 (switchboard) 713.932.0222 (fax) ajohnson@xxxxxxxxxxx -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] = On Behalf Of Burnham, Rob C. Sent: Tuesday, March 08, 2005 7:55 PM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] WP51D Stand-alone That's what I was thinking, but I could swear I did this before. Maybe I had it connected to the DNBT? But I now I wasn't on the operation floor when I built it and it's identical to this one? Thanks Jeremy! -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Jeremy Milum Sent: Tuesday, March 08, 2005 1:47 PM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] WP51D Stand-alone On Tue, 8 Mar 2005 14:41:59 -0500, Burnham, Rob C. <rburnham@xxxxxxxxxxxxxx> wrote: > After I run the COMMIT and reboot, I get: > "Configuring Network Interfaces: Program Terminated" >=3D20 > My failing memory has a recall of setting up a WP51D > off-line and then taking it to its final resting place, plugging > it in and away we go. Was this just a dream? I believe that a nodebus WP must be connected to a DNBT in order to boot, the AW's will boot fine stand-alone, but not the WP's --=3D20 Patron saints in general are broadband connections to the Almighty - Michelle Delio, Wired News =3D20 =3D20 _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html =3D20 foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djo= in to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dlea= ve =3D20 =20 =20 _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html =20 foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave =20 =20 =20 _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html =20 foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave =20 _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave