Thanks very much for the quick response. It's a 2.01i card type server. 1 disk. We have a backup that we could restore to a working Call Pilot but so far we cannot get the Win NT installed.
We have followed the Nortel doc and everything goes fine until the step four install begins. It is supposed to be an 'automated process' involving more than one reboot and ending up with the Nortel logo, but it fails after the first reboot and all you can do is start over and end up with the same result. Thanks again for the quick response.
1: Have you got a ghost image? Makes life a lot easier.
2: I am assuming that you have access to the hard disk at some point after the format etc. Have you done a chkdsk at that point?
3: How are you doing the load? It almost sounds like at the point that the reboot in step 4 occurs that the CP is seeing another device so fails. Bit like the boot devices are in the wrong order.
Apologies as it has been a long time since I have done a rebuild from the recovery disk.
As a bit of an aside, if you have 2,02,26 installed, you can up that to 2.02.27 with the same keycodes.
1. Don't have a ghost image; it's a single drive, where would the ghost image be? (I understand mirrored disks where you have a multi disk or a RAID arrangement but don't know how with one disk.
2. I'll do the checkdisk tomorrow; otherwise it's a new 40 gig disk.
3. Boot device choices are 1)Hard Disk, 2)CD ROM, 3)CLAN: what order should they be in? You might be onto something here! I have varied the boot order in an effort get it to return to the CD Drive when it indicated "No Valid OS"
New systems come with the OS already installed. The only install CD we have is for the Call Pilot app itself (I'll double check that this morning. thanks again, going there now to resume.
I'm note sure but does 2.02 run on a 201i? If I remember correct you need 2.5/3 for the 201i. It's been a while since I've seen a CallPilot older then release 3.
You can find the needed platform type on the keycode sheet. You can't change platform because it's hardcoded in the keycode.
Marc D.
If Bill Gates had a nickel for every time Windows crashed... Oh wait, he does...
I have reset the ROM BIOS setup to default in the hope that it would establish the correct boot sequence. The boot order is currently:
"Removable Devices
+Hard Drive
ATAPI CD-ROM Drive
Network Boot"
Then I went thru steps 1-4 again with the same result: on boot-up it continues to give the message
"Cannot find valid operating system" "Boot ROM DOS Y/N:"
Card slot 9 is Call Pilot, Card = NTRH30AA,
CD s/w = CallPilot Server 2.02, 02.01.27.05, Mar 3, 2003;
CD P/N = NTUB40AE/A0510777
The OS Recovery CD = "CallPilot 2.02 OS Recovery", 02.01.27.05 K.
We also have two "My CallPilot S/W nd Updates" CD's: one is 02.01.27.09, the other is 2.50.06.08.
There are two pc-mcia type cards in the lowerslot: MPC 2 & 3, which have always been there. I unerstand they are for multimedia purposes. This site only uses voice mail, menus, and maybe some announcements: no multi media apps, no integrated messaging, etc.
thanks for the help though, but we don't otherwise have any CF cards; only the OS Recovery CD and the CP Server S/W CD.
I actually tried using a regular Windows NT from Microsoft but got nowhere with that.
The 200 i needed the pcmcia card to restore from hard disk failure on the 201i it was pre loaded so you could boot up and use the cd rom drive their was and image disk available from nortel for 2.2 it was one disk I have tryed to use the recovery disk that comes with the software with out much luck the image seems to work better.
Thanks to all who pitched in with this problem. Ultimately it was resolved by obtaining a "Ghost Image", downloaded from another site. This restored the OS and the Call Pilot App to the drive and we were then able to 'recreate' the 'customer data'.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.