Latest CVS config upgrade of drive letters problem

[J. Grant]

Hello,

I just built and installed CVS WINE using the work around for asla 
suggested by Ivan.

However, the config file does not seem to have been converted correctly. 
  I fixed the symbolic link manually.  Read on if you are interested to 
know the details of this bug.

Kind regards

JG

$ wcmd
Created symlink /home/now3d/.wine/dosdevices/com1 -> /dev/ttyS0
Created symlink /home/now3d/.wine/dosdevices/com2 -> /dev/ttyS1
Created symlink /home/now3d/.wine/dosdevices/com3 -> /dev/ttyS2
Created symlink /home/now3d/.wine/dosdevices/com4 -> /dev/modem
Created symlink /home/now3d/.wine/dosdevices/lpt1 -> /dev/lp0
Created symlink /home/now3d/.wine/dosdevices/c: -> /home/now3d/c
Created symlink /home/now3d/.wine/dosdevices/d: -> ../${HOME}
Created symlink /home/now3d/.wine/dosdevices/e: -> /tmp
Created symlink /home/now3d/.wine/dosdevices/f: -> /mnt/cdrom2
Created symlink /home/now3d/.wine/dosdevices/g: -> /mnt/cdrom
Created symlink /home/now3d/.wine/dosdevices/f:: -> /dev/scd0
Created symlink /home/now3d/.wine/dosdevices/g:: -> /dev/scd1

You can now remove the [SerialPorts], [ParallelPorts], and [Drive] sections
in your configuration file, they are replaced by the above symlinks.

Converted drive type to new entry HKLM\Software\Wine\Drives "C:" = L"hd"
Converted drive type to new entry HKLM\Software\Wine\Drives "D:" = 
L"network"
Converted drive type to new entry HKLM\Software\Wine\Drives "E:" = L"hd"
Converted drive type to new entry HKLM\Software\Wine\Drives "F:" = L"cdrom"
Converted drive type to new entry HKLM\Software\Wine\Drives "G:" = L"cdrom"

Converted temp dir to new entry HKCU\Environment "TEMP" = L"e:\"
Converted path dir to new entry HKCU\Environment "PATH" = 
L"d:\vs\vc98\bin;d:\vs\common\msdev98\bin;c:\windows;c:\windows\system"
Converted profile dir to new entry HKCU\Environment "USERPROFILE" = 
L"c:\windows\Profiles\Administrator"
Converted windows dir to new entry HKCU\Environment "windir" = 
L"c:\windows"
Converted system dir to new entry HKCU\Environment "winsysdir" = 
L"c:\windows\system"
Warning: could not find DOS drive for current working directory 
'/home/now3d', starting in the Windows directory.
Please use the registry key HKEY_CURRENT_CONFIG\Software\Fonts\LogPixels
to set the screen resolution and remove the "Resolution" entry in the 
config file
fixme:font:WineEngCreateFontInstance just using first face for now
WCMD Version 0.17

C:\windows>ls
File not found

C:\windows>cd ..

C:>ver
WCMD Version 0.17

C:>d:
Path not found

C:>d:\
Path not found

C:>cd d:
Path not found

This worked before I ugpraded.

10 Sep 20 00:13 d: -> ../${HOME}

Thats a duff sym link,  so I assume it was not evaluated correctly in 
that script..?

Are these double links meant to be present?

lrwxrwxrwx    1 now3d    now3d          11 Sep 20 00:13 f: -> /mnt/cdrom2/
lrwxrwxrwx    1 now3d    now3d           9 Sep 20 00:13 f:: -> /dev/scd0
lrwxrwxrwx    1 now3d    now3d          10 Sep 20 00:13 g: -> /mnt/cdrom/
lrwxrwxrwx    1 now3d    now3d           9 Sep 20 00:13 g:: -> /dev/scd1

lrwxrwxrwx    1 now3d    now3d          10 Sep 20 00:13 com2 -> /dev/ttyS1
lrwxrwxrwx    1 now3d    now3d          10 Sep 20 00:13 com3 -> /dev/ttyS2

these are also duff links, but maybe it will not effect anything.

[Vincent Béron]

Le dim 19/09/2004 à 19:24, J. Grant a écrit :
> Hello,
>
> I just built and installed CVS WINE using the work around for asla 
> suggested by Ivan.
>
> However, the config file does not seem to have been converted correctly. 
>   I fixed the symbolic link manually.  Read on if you are interested to 
> know the details of this bug.
>
> Kind regards
>
> JG
>
> $ wcmd
> Created symlink /home/now3d/.wine/dosdevices/com1 -> /dev/ttyS0
> Created symlink /home/now3d/.wine/dosdevices/com2 -> /dev/ttyS1
> Created symlink /home/now3d/.wine/dosdevices/com3 -> /dev/ttyS2
> Created symlink /home/now3d/.wine/dosdevices/com4 -> /dev/modem
> Created symlink /home/now3d/.wine/dosdevices/lpt1 -> /dev/lp0
> Created symlink /home/now3d/.wine/dosdevices/c: -> /home/now3d/c
> Created symlink /home/now3d/.wine/dosdevices/d: -> ../${HOME}

Wine didn't expand ${HOME} when creating this symlink. Delete it (d:)
and recreate it with ln -s ~ ~/.wine/dosdevices/d:

Upgrading from a quite old version I may add... ($VAR-style variables in
config are long gone, maybe a year now).

[snip]
> fixme:font:WineEngCreateFontInstance just using first face for now
> WCMD Version 0.17
>
> C:\windows>ls
> File not found

ls is Unix, you don't have access to it in wcmd. Use dir.

[snip]
> 10 Sep 20 00:13 d: -> ../${HOME}
>
> Thats a duff sym link,  so I assume it was not evaluated correctly in 
> that script..?

See above. Combination of two changes in Wine code.
> Are these double links meant to be present?
>
> lrwxrwxrwx    1 now3d    now3d          11 Sep 20 00:13 f: -> /mnt/cdrom2/
> lrwxrwxrwx    1 now3d    now3d           9 Sep 20 00:13 f:: -> /dev/scd0
> lrwxrwxrwx    1 now3d    now3d          10 Sep 20 00:13 g: -> /mnt/cdrom/
> lrwxrwxrwx    1 now3d    now3d           9 Sep 20 00:13 g:: -> /dev/scd1

The f:: (double-colon) links point to the (Unix) device behind the
Windows dir. They were created from your config.
> lrwxrwxrwx    1 now3d    now3d          10 Sep 20 00:13 com2 -> /dev/ttyS1
> lrwxrwxrwx    1 now3d    now3d          10 Sep 20 00:13 com3 -> /dev/ttyS2
>
> these are also duff links, but maybe it will not effect anything.

Wine just created the symlinks from your config. You had com2 and com3
in it, so it created the link.

Vincent

[J. Grant]

Hi Vincent,

Thanks for your reply.
> Upgrading from a quite old version I may add... ($VAR-style variables in
> config are long gone, maybe a year now).

Yep, this WINE build was last used when I wrote an article on WINE
2003-02-18.  I do not see why WINE should not be compatible with a
config file which is only 17 months old though.  Compatibility should be
for the life of a product in use IMO.  If that development time is too
not available for WINE, I can accept that, but non-compatibility with
recent config files like this should be avoided if possible in my view.
> > C:\windows>ls
> > File not found
>
> ls is Unix, you don't have access to it in wcmd. Use dir.

I had hoped for an alias, in the same way that "dir" works in nearly all
GNU/Linux distros.
> The f:: (double-colon) links point to the (Unix) device behind the
> Windows dir. They were created from your config.

Ok.
> Wine just created the symlinks from your config. You had com2 and com3
> in it, so it created the link.

Then I guess com2 and com3 were default in the mdk9.0 wine package
"config" file, as I did not add those lines myself.

Please include my email address in replies.

Kind regards

JG

[Vincent Béron]

Le lun 20/09/2004 à 19:10, J. Grant a écrit :
> Hi Vincent,
>
> Thanks for your reply.
> > Upgrading from a quite old version I may add... ($VAR-style variables in
> > config are long gone, maybe a year now).
>
> Yep, this WINE build was last used when I wrote an article on WINE
> 2003-02-18.  I do not see why WINE should not be compatible with a
> config file which is only 17 months old though.  Compatibility should be
> for the life of a product in use IMO.  If that development time is too
> not available for WINE, I can accept that, but non-compatibility with
> recent config files like this should be avoided if possible in my view.

Talk to Alexandre on that :)
Although 17 months begins to be old for Wine.
> > > C:\windows>ls
> > > File not found
> >
> > ls is Unix, you don't have access to it in wcmd. Use dir.
>
> I had hoped for an alias, in the same way that "dir" works in nearly all
> GNU/Linux distros.

Does Windows support aliases? Does it provides ls? If the answer is yes
to any of those two questions, then Wine is at fault, else no.
> > The f:: (double-colon) links point to the (Unix) device behind the
> > Windows dir. They were created from your config.
>
> Ok.
> > Wine just created the symlinks from your config. You had com2 and com3
> > in it, so it created the link.
>
> Then I guess com2 and com3 were default in the mdk9.0 wine package
> "config" file, as I did not add those lines myself.

Probably. Nowadays most users don't have a config file.

Vincent