creating a link to a file
 

I want to move a file from one partition to the second partition but have my software still be able to find it on the first partition. So create a link on the first drive that doesn't take up space. I tried just creating a shortcut but it didn't work. My first partition is full and the computer will not turn on. To fix this issue b4 I moved the page file to the second partition but that only freed up 25mb which has since been used up with new files added to it.

Now If I cant figure this out I will half to remove some of the files and everyday import and export what ever I am working on. Which is a real pain. Takes awhile to do the import and export. But if I can move the database which is around 50mb then every time I add something to the machine it will just add to the second drive which has 2gb free.

Or spend 10k on the software that runs off winxp. Which right now is not a option.

OS: Windows NT 4.0 workstation.

how big are your partitions?

Its a 2gb partition.

If I remember correctly you've got this growing database, but there's also something else that is growing as well. Is the "new" files added to it from the database growth?

What else is adding to the drive?

---------- Post added at 08:15 AM ---------- Previous post was at 07:50 AM ----------

I think the best solution for you is to buy a new IDE drive. Ghost an image of your NTFS partition and lay that back down onto the new drive. Use something like Gpart (not partition magic) and expand the partition size.

The only thing added to the machine are dcw files everyday which go into a database. I freed up 24mb by moving the page file. And since then the database has grown 16mb leaving us with only 8mb freed up which is no enough room. Because when you open up the software it does this thing called compacting the database and that uses up hard drive space and error's out.

I think you can try the ghost to IDE method. Using shortcuts and recursive naming locations won't really be very effective in any manner.

You're topping out the software and the hardware. If this is part of your critical mission apps, you should be able to know how to restore it into a fresh environment. If you can't do it via installation disks, your best bet would be to try the ghost method I mentioned.

Think about if this app failed hard, not soft like it is. You're going to have to recover to something new. Work that angle.

http://en.wikipedia.org/wiki/NTFS#Volume_mount_points
Looks like they added that feature in Windows 2000, sorry.