Oh, yeah - it would also help us help you if you tell us what version and SP of NetWare you're working with, as well as the version of the Portlock software.

OK- I have one disk in the server but in portlock it shows 2, one is the brand name with the disk size and the other one has XINT13.
Version of  portlock is 3.26.1.
I'm not even at the point where i have to put my image back on.

Extended Interrupt 13 is related to the "8GB Barrier" - Extended Interrupt 13 is historically used for DOS access to disk larger than 8GB.

How is your storage manager software loaded - diskette or CD?  Is it a DOS or Linux boot?
 
 

oh, I'm using a DOS boot disk (Floppy) should i use Linux?

I would think it would work either way - I was just wondering which way you were doing it.

Do you have INT 13h support turned on in your SCSI config?  How about BIOS?

I do have INT 13h support turned on and i could not find any thing in the BIOS that related to the "INT 13h"

sorry, i've just had another look and it's a win98 boot disk, should this matter?

No, I wouldn't think so.  

Are you loading a particular driver for your SCSI or RAID controller in the boot diskette?  It's possible that the version of Portlock Storage Manager you're running has access for the particular controller you have built-in, so it's confusing things...

By the way, Win98 boot disks are actually MS-DOS 7 boot disks - Microsoft just doesn't want you to know that Win98 still runs on top of DOS, so instead of naming it MS-DOS 7, they named it "Windows 98" in the internal name in the boot files.

Try this
1. Use the Portlock Boot Wizard to make a Bootable floppy for your Server(TCP/IP Boot Disk).
2. Copy the file to run from a floppy from following link:
http://www.portlock.com/download/stormgr.htm
Minimum files to run Portlock Storage Manager from a floppy: Version 3.33 (1 MB)
Unzip onto a formatted floppy diskette.
"remember copying your Portlock lic. file to the floppy"Ver 3.26 lic file should work on 3.33.
3.Run Stormgr.exe from the floppy.
4.SM should recognize the partitions correctly.I have tried it on Dell 6600 server with Hardware RAID ( PERC).

ok slow down, i've downloaded the minimum file and unzipped them, i now have 3 files : stormgr.nlm(2mb),portlock.nlm(700k) and stormgr.lic(1k)
i've got two floppy's, one with the boot files and the other with the stormgr.exe. Now where do i copy the files?
And thank you for your help.

You should have 4 files: stormgr.clm, stormgr.exe, stormgr.lic and tcpipn.nlm... and from what I can tell on the portlock site, they should go on your boot disk...

The files you downloaded are *.nlm --> "Netware" loadable module.
You need file :   "Stormgr.exe" which can run on Win98/DOS7 whatever.

Step1  Floppy 1  : Download Floppy image from the link " http://www.portlock.com/ethernet.htm"   ----> It will give you a TCP/IP boot disk. Boot from this floppy.
                          Now your server will have a A:/>         :) You don't need Portlock BOOT wizard now.This will load TCP/IP stack on top of DOS.

Step2  Floppy 2   :  Download DOS version of SM.Minimum files to run Portlock Storage Manager from a floppy: Version 3.33 (1 MB)
               Unzip onto a formatted floppy diskette.This disk will be used to run "Stormgr.exe".
                 Put this floppy now in the server floppy drive and from A:/> Stormgr.exe.

Step3                : On the StoreManager screen tell it what to do.I believe you want to restore the image.So just restore the image by  pointing SM  to the path of image file.
FYI the list of files on my StoreManager Directory is as follows:
04/08/2003  10:10 PM             4,891 BUGS.TXT
05/19/2003  09:00 AM           176,214 IMAGEMGR.EXE
05/19/2003  09:00 AM           135,282 IMAGEMGR.NLM  ----->No need to copy on Floppy 2 (NW Version)
08/14/2003  09:43 AM                 0 LICENSE.TXT
05/19/2003  09:00 AM            61,951 PINSTALL.NLM    ----->No need to copy on Floppy 2 (NW Version)
05/19/2003  09:00 AM            79,360 REMOTE.EXE
04/12/2005  01:34 PM                 0 sme.txt
05/19/2003  09:00 AM           898,699 STORMGR.CLM
05/19/2003  09:00 AM           176,214 STORMGR.EXE  ------>Run this file.
05/19/2003  09:00 AM             2,264 STORMGR.IPS
08/13/2003  01:13 PM             1,024 STORMGR.LIC     ---->Your Lic file.
05/19/2003  09:00 AM         2,022,848 STORMGR.NLM  ----->No need to copy on Floppy 2 (NW Version)
05/19/2003  09:00 AM           176,209 STORMGRV.EXE
05/19/2003  09:00 AM           704,953 SVRUPD10.NLM  ----->No need to copy on Floppy 2 (NW Version)
05/19/2003  09:00 AM            20,149 SVRUPDXX.NLM  ----->No need to copy on Floppy 2 (NW Version)
05/19/2003  09:00 AM             9,652 TCPIPN.NLM       ----->No need to copy on Floppy 2 (NW Version)
              16 File(s)      4,469,710 bytes

Best of luck.

ok, i tried the above and i still see the second "shadow disk" but when i tried a spare 18 G disk and it worked!
How weird,any ideas, and thanks again.

If you have a bootable CDROM, you could try the Linux boot disk.  I still think it's a DOS thing.

Yes i think ShineOn is right, it is a DOS thing.
BTW Download the Portlock linux ISO image, Use MagicISO ( even the trial version will work because the ISO's image size is less than 300MB) to add your License file to the ISO image, then burn the final ISO to a Blank CD.
Boot from this CD and it should work.
If possible Try to restore the image on the BRAND Name with the disk size and  for the time being do not use the one with "XINT13".See if this works.
May be you could also try to boot from a windows98 bootable CD and run " fdisk /status " to see your partition table.(is everything o.k.)

I tried the Linux boot disk and still got the same,and i've tried to install it to both drives without any luck!
Thanks for your help, I've now sent a e-mail to portlock.
if you have any other ideas that would be good.
if it helps i'm using a IMB ESeries 300 server.
Thanks

1. If possible use another disk of same capacity and try if the problem is same.Reinitialize the "one disk in the server" .
2.Take this hard disk to "another system", boot from Linux CD and see if the problem is same.

Hi Sterlingdev
I was just curious to know, what exactly was the cause of your problem and whether it was solved or not?
Thanks

Did'nt find one in the end!
Nevermind.
Thanks for your help.
SD