All you need to do is make sure that the website points to a location you control i.e. in IIS make sure that localhost/dotnetnuke uses the location that you've unzipped DNN 3 to on the F: drive as it's local path.

Cathal

It should adjust to whatever drive it's on.  I do all my stuff from the D: drive.  (not CDROM). 

To get it to work right though I've found I've got to unzip the source to the directory I want and the open the site in IE and let it do it's install.  The I open the DNN solution in VS 2003 and wait while it refactors everything.  Then I do a rebuild.  After the rebuild I add in all the project sources for modules I use.

The only things I've had a problem with having the wrong path after that is the solpartmenu and zlib.  Just delete the references to those two projects and then add them back in.  You'll get a warning that the path is going to change which is all right since that's what you want anyway.  :)

Cheers,

BTW there is probably a much easier less time consuming way of doing this but it works for me.