Unable To Create Virtual Memory Page File on Win XP Pro SP1

[gaviota 0]

When installing Windows XP Pro SP1 on a PC with a SCSI disk, I've always had disconnect the ATA disks because for some reason Windows always decides to install the boot files on the ATA disk, even when I specify that I want Windows installed in the SCSI disk.

 

Anyway, by simply disconnecting the ATA disks I've always been able to install Windows and the virtual memory page file on the SCSI disk, until now. Yesterday I added a 120 GB ATA disk to my PC and I later noticed that Windows had decided by itself to move the virtual memory page file to this disk. But when I checked on the virtual memory window, the strange thing was that it said it was located on the SCSI disk, but it was really in the ATA disk.

 

So I erased this paging file by setting the virtual memory file to size 0, rebooted, then I erased the file, removed the E: label from the ATA disk and mounted it on a directory of the SCSI disk. Then I opened the virtual memory window and set a new page file on the SCSI disk and rebooted, but for some reason it doesn't create the virtual memory file. When I log in after rebooting it says that there was an error creating the virtual memory file.

 

The boot order in the BIOS is as follows:

1) SCSI-0 (Seagate Cheetah 15K.3)

2) Maxtor D740X (master on IDE # 1)

3) Maxtor D740X (master on IDE # 2)

4) Western Digital Special Edition (slave on IDE # 1)

 

I've tried changing the boot order of all the IDE disks, always leaving the SCSI as the first device, but I still can't create the virtual memory page file on the SCSI disk. I've even tried disconnecting all IDE disks again, leaving only the SCSI disk, and I still can't create the page file.

 

The Cheetah and the WD disk are basic file systems, while the two Maxtors are dynamic disks spanned on RAID 0. SCSI controller is an LSI Logic U160, motherboard is an Asus PC-DL Deluxe with BIOS 1003 and OS is Windows XP Pro with SP1 and all the latest updates.

 

Any advice will be appreciated.

[ofelas 0]

I had a similar problem on an IDE drive with NAV 2004 installed...switching back to NAV 2003 solved the problem.