io operation failure

[rehanqadri]

i have recently changes my harddisk from 20 gb to 80 gb and also transferred my programs developed in fpw26 but when i run them on my new harddisk i get the error
"io operation failure". i could not figure out what is the problem.

 

[rob444]

If this is the "standard" reaction of fpw26 on the new harddisk you might have directories that are read only.
Go into dos mode and run attrib *.*.
If directories and/or files are read only change that with attrib.exe with the command:
attrib -r *.*

Rob.

 

[cricket]

Did you use a CD to transfer files? Files become read only.
Also there can be a similar problem for a Standard User or Power User when an Administrator copies files from a network to an XP/Win2000 machine.

If you, as and administrator, need to copy files for a less priviledged user, change the lower level user to Administrator priviledges while you copy the files, and change back later. This is particularly the case when using the WinXP wizard for transferring files and settings.

 

[cricket]

Did you use a CD to transfer files? Files become read only.
Also there can be a similar problem for a Standard User or Power User when an Administrator copies files from a network to an XP/Win2000 machine.

If you, as an administrator, need to copy files for a less priviledged user, change the lower level user to Administrator priviledges, and log in as the user while you copy the files, and change back later. This is particularly the case when using the WinXP wizard for transferring files and settings.

 

[ChrisMc]

One I've found - some DVD re-writers cause I/O failure messages. The workround is to leave a disk in the drive. I think they are appearing as fixed disks to FP (probably because of the capacity) and how can you have a fixed drive that returns a 'No disk in' message!

 

[Brak]

Another common problem is that if you develope on a certain drive (lets say F: for example) and you complied the code it will look for the program in F: (I have no clue way FP would do this). So if you add a new drive or paritions which causes a removable disk to be in that location (like a CD-ROM) then it will yell at you with the I/O error.

An easy way to confirm this is to put a CD in and then run your APP. If no errors come up then that was your problem.


There are two solutions. One is to recompile your program on your C drive since all computers will usually have such a drive.

What I do to solve the problem is to open up the compiled code with a hex editor and change the drive letter. Do a string search for you APP directory and just change the drive letter to C. If you encrypt your then you will have to do a little code breaking - which isn't that hard since you have can hae available a non-encrypted version.

That way you can have your projects on any drive you want and not have fears of a user having a CD-ROM located at that particular letter.

Hope that helps!


B"H
Brak