Mike Hearn mh@codeweavers.com writes:
Mike Hearn mh@codeweavers.com Add a check to process_init() to ensure at least one drive is defined, as things break if that isn't the case.
There is no need to define the Drives registry key, everything should work fine without it. If something doesn't, that's a bug.
On Mon, 2004-05-24 at 11:16 -0700, Alexandre Julliard wrote:
There is no need to define the Drives registry key, everything should work fine without it. If something doesn't, that's a bug.
Are there really many programs that will work in the absence of the (virtual) hard disk?
The thing that broke was - I think - reading win.ini in some part of Wine initialization. At the very least, the error was rather uninformative: just your standard STATUS_DLL_INIT_FAILED (or the equivalent) ...
Mike Hearn mh@codeweavers.com writes:
On Mon, 2004-05-24 at 11:16 -0700, Alexandre Julliard wrote:
There is no need to define the Drives registry key, everything should work fine without it. If something doesn't, that's a bug.
Are there really many programs that will work in the absence of the (virtual) hard disk?
That's a different problem. The Drives key is only used to override the autodetected drive types, so it shouldn't matter if it's missing. The drive symlinks themselves are obviously more important, and there's definitely room for improvement in that area. Still, I think we should try as much as possible to make things work even without the symlinks.
On Mon, 2004-05-24 at 12:19 -0700, Alexandre Julliard wrote:
That's a different problem. The Drives key is only used to override the autodetected drive types, so it shouldn't matter if it's missing. The drive symlinks themselves are obviously more important,
Ah, sorry, I hadn't kept up with the file system changes. I'd forgotten the registry keys aren't needed any more.
I suppose the problem was that the symlinks weren't being seen or something. I'll remove the keys and try again.
-
Alexandre Julliard -
Mike Hearn