Page 1 of 1

Find command did not read temp params anymore

Posted: 28 May 2019 11:08
by goodywp
Hi all,

I just came across this issue, sth. related to system.

Code: Select all


:: load parameters from BaseMain.cfg
find /V ";;" BaseMain.cfg | find "=" > __temp_read_params
for /F "tokens=*" %%I in (__temp_read_params) do set %%I
del /Q __temp_read_params >Nul

Basically, it shall read the params from BaseMain.cfg into a temp place somewhere in the system (using Window 10 pro). It works fine always but one day some dell encryption On /Off encrypted some of files in the system. My tech support to remove that and almost recover everything. But the above script not working,
onetime complain
find /V ";;" not exist after the tech support did sth.
onetime complain
the system can not find the file specified

any clue on this....or how to recover...?

Just got another script issue.

Does anybody have such issue before and what is the solution?

Thanks

Re: Why this remp read params not find anymore

Posted: 28 May 2019 19:47
by ShadowThief
BaseMain.cfg (whatever that is) seems to have been deleted

Re: Why this remp read params not find anymore

Posted: 29 May 2019 07:19
by goodywp
ShadowThief wrote:
28 May 2019 19:47
BaseMain.cfg (whatever that is) seems to have been deleted
Thanks for your reply! Yes I was thinking that way but checked that the file was there...

Re: Why this temp read params not find anymore

Posted: 10 Jul 2019 09:45
by goodywp
Today, I got another issue which I could think of similar to this original issue

Code: Select all

set sch_1=T501-08815-0103
find /i "%sch_1%"<all_scheme.txt>>list_sch.txt
Here is what I got
find: /i: No such file or directory
find: T501-08815-0103: No such file or directory

The above script works fine in my laptop but not working in the same desktop which I post this above original issue.
I searched up from internet, there is one people saying
When finding and deleting directories with find, you'll often encounter this error because find stores the directory to process subdirectories, then deletes it with exec, then tries to traverse the subdirectories which no longer exist.
something could be related to temporary store in that desktop system not working any more?
Does anybody have some idea on this?
Thanks