Hi everyone

I recently installed Mandrake 9.1 and the Wine that was included with the distro. When I run notepad, using wine, it works fine. However, I get these errors.

Warning: access to temporary directory '/mnt/win_c/WINDOWS/Temp' failed (Read-only file system).
fixme:reg:_nt_dump_lf unknown Win XP node id 0x686c: do we need to add support for it ?
fixme:reg:_nt_dump_lf unknown Win XP node id 0x686c: do we need to add support for it ?
fixme:reg:_nt_dump_lf unknown Win XP node id 0x686c: do we need to add support for it ?




Here is the C and D drives of my config file.

[Drive C]
"Path" = "/mnt/win_c"
"Type" = "hd"
"Label" = "Windows"
"Filesystem" = "win95"

[Drive D]
"Path" = "/mnt/win_d"
"Type" = "hd"
"Label" = "/mnt/win_d"
"Filesystem" = "win95"



and here is my winecheck file.
----------------------------------
------------------------- checking miscellaneous stuff -------------------------
001. Checking for root user... OK.

--------------------------- checking Wine base files ---------------------------
002. Checking for file "wine"... OK.
003. Checking for correct .so lib config (please wait)... OK.

----------------------------- checking config file -----------------------------
004. Checking config file access... OK.

>>> Checking drive A settings:
005. Checking Path option... OK.
006. Checking Type option... OK.
007. Checking device /dev/fd0... OK.
008. Checking Filesystem option... OK.
--> OK.

>>> Checking drive C settings:
009. Checking Path option... FAILED (/mnt/win_c is not writable for you).
- ADVICE: If your user account is supposed to be able to access
it properly, use chmod as root to fix it ("man chmod"). If that doesn't help, change mount options in case of VFAT ("umask" option).
010. Checking Type option... OK.
011. Checking Filesystem option... OK.
--> PROBLEM.

>>> Checking drive D settings:
012. Checking Path option... SUSPICIOUS (/mnt/win_d is not writable for you).
- ADVICE: If your user account is supposed to be able to access
it properly, use chmod as root to fix it ("man chmod"). If that doesn't help, change mount options in case of VFAT ("umask" option).
013. Checking Type option... OK.
014. Checking Filesystem option... OK.
--> PROBLEM.

>>> Checking drive E settings:
015. Checking Path option... OK.
016. Checking Type option... OK.
017. Checking device dev=/dev/hdc,fs=auto,ro,--,iocharset=iCRITICAL (dev=/dev/hdc,fs=auto,ro,--,iocharset=iso8859-1,codepage=850,umask=0 does not exist).
- ADVICE: use MAKEDEV script to create it.
018. Checking Filesystem option... OK.
--> PROBLEM.

>>> Checking drive F settings:
019. Checking Path option... OK.
020. Checking Type option... OK.
021. Checking device dev=/dev/scd0,fs=auto,ro,--,iocharset=CRITICAL (dev=/dev/scd0,fs=auto,ro,--,iocharset=iso8859-1,codepage=850,umask=0 does not exist).
- ADVICE: use MAKEDEV script to create it.
022. Checking Filesystem option... OK.
--> PROBLEM.

>>> Checking drive G settings:
023. Checking Path option... OK.
024. Checking Type option... OK.
025. Checking Filesystem option... OK.
--> OK.

>>> Checking drive H settings:
026. Checking Path option... SUSPICIOUS (maneesh does not exist !).
- ADVICE: create this directory or point Path to a real directory.
027. Checking Type option... OK.
028. Checking Filesystem option... OK.
--> PROBLEM.

--------------------- checking system devices used by Wine ---------------------
029. Checking sound device /dev/dsp... OK.
030. Checking audio mixer device /dev/mixer... OK.
031. Checking MIDI sequencer device /dev/sequencer... OK.

----------------------- checking registry configuration ------------------------
032. Checking availability of winedefault.reg entries... CRITICAL (entry "SHAREDMEMLOCATION" not found in system.reg registry file).
- ADVICE: file winedefault.reg, the most basic wine registry environment, doesn't seem to have been applied using regapi.
033. Checking availability of windows registry entries... NOTICE (entry "Default Taskbar" not found).
- ADVICE: A Windows registry does not seem to have been added to Wine as this typical Windows registry entry does not exist in Wine's registry. A complete original Windows registry entry set will *not* be available with a no-windows install. Usually this will present no problem in running applications although this can affect newer programs.

33 tests. 2 suspicious, 0 bad, 3 critical, 1 failed.
Wine configuration correctness score: 9.12%
-----------------------------------

I tried to chmod my win_c to 751, but I don't know if that worked or not.

If you can help me that would be great. I can not open any programs that use temp files whatsoever.

-Maneesh

you're better off editing ~/.wine/config to mount /tmp as a drive, and then marking that as the temporary directory. eg:

[Drive Z]
"Path" = "/tmp"
"Type" = "hd"
"Label" = "Tmp Drive"
"Filesystem" = "win95"


and then:

[wine]
"Temp" = "z:\\"


Alternatively you can edit /etc/fstab to mount win_c readwrite and give all users write permissions, but i wouldn't recommend it.

Hmm. I tried both ways (editing config and editing /etc/fstab) and the same thing happens. I still get the error that win_c is read only.

What else can I do?


Also, I noticed that I was unable to chmod the win_c. I get the error that it was a Read-Only Filesystem.

-Maneesh

you'd be way better off going to frankscorner website (its in my sig below) and getting the app called Winetools and create a fake windows drive...it will be easier than using a existing windows partition..

is win_c ntfs?

win_c is in fact ntfs.'

--Maneesh

Bump. Anyone else have any ideas?

have u recompiled your kernel to allow u to write to a ntfs fs?

Heh, I'm a newbie and have no idea how to recompile a kernel. Can you point me to some instructions?

Thanks

-Maneesh

there is detailed instructions already posted on this site, doing a search should get them up for u.

in the mean time, go to /usr/src/linux
type make xconfig
this will bring up a user interface with the kernel options.
follow them through, u should do some research about some of the things in there, do not make changes if u do not know what u are doing.
u need to look in filesystems, u can enable writing to ntfs partitions in there
and one thing, make sure that ur kernel can read the partition that linux is installed on or else the kernel will panic :O
save and exit;
$make dep modules modules_install bzImage

if ur machine is less than 1 Ghz, go get some lunch

$cp /usr/src/linux/arch/i386/boot/bzImage /boot/kernelx.xx.xx
$cp /usr/src/linux/SystemMap /boot/SystemMap

edit ur /etc/lilo.conf accordingly
run /sbin/lilo

these are general steps, if its ur first time recompiling the kernel, then do a search in these forums for more detailed instructions

I'm good up to here, but what should I edit lilo.conf to include?


Thanks

-Maneesh

direct it to your new kernel and tell it to boot it. u need to look examples of that up, i is different from case to case depending on your disk structure

generally just copy the section for the current boot and replace the image with the path of ur new kernel

eg
current boot
image=/boot/vmlinuz
...
...

u add to end
image=/boot/kernel2.4.22
...
...

Hmm

After changing my lilo.conf file, whenever i try to startx, i get this error.

Using vt 7
NV could not open control device /dev/nvidiact1 (No such file or directory!)

EE Nvidia(0) Failed to initialize Nvidia kernel module.
EE Screens found, but none have useable configuration

Fatal Server Error
No Screens Found.


Does anyone have any idea what I can do to fix this?

THanks

-Maneesh

mmm, no idea, maybe u took support out for ur card in character devices part of the kernel ?

backup the xf86config file and try to make a new one with generic vesa drivers