What do I do
Started by
jkmira
, Mar 30 2006 03:39 PM
#106
Posted 06 April 2006 - 05:23 PM
#107
Posted 07 April 2006 - 03:10 AM
ok 3 questions
when I type in c:\>dir window\desktop\secrec~1 I get,
Volume in drive C has no label
Volume Serial Number is 3D2A-1907
Directory of C:\WINDOW\DESKTOP
Secrec~1 LNK 432 03-30-06 (time)
1 file(s) 432 Bytes
0 dir(s) 584.43 MB free
1. If I type in del window\desktop\secrec~1 or something like that will that delete the program?
2. Is there a way to uninstall the program?
3. Will either deleting or uninstalling the program undo the programs effect and give control of the c:\ drive back to me and allow me to use windows again?
when I type in c:\>dir window\desktop\secrec~1 I get,
Volume in drive C has no label
Volume Serial Number is 3D2A-1907
Directory of C:\WINDOW\DESKTOP
Secrec~1 LNK 432 03-30-06 (time)
1 file(s) 432 Bytes
0 dir(s) 584.43 MB free
1. If I type in del window\desktop\secrec~1 or something like that will that delete the program?
2. Is there a way to uninstall the program?
3. Will either deleting or uninstalling the program undo the programs effect and give control of the c:\ drive back to me and allow me to use windows again?
#108
Posted 07 April 2006 - 06:35 AM
first rename the window folder to WINDOWS
type ren window WINDOWS
i have a feeling that might let you boot up...MIGHT
deleting the program WILL have no effect..it will just leave the lock behind...(i tried it...) this program is not an ACTIVE LOCKER...(one that actually continually does something to lock the folders...which is the type that you can uninstall to remove the lock)...this one just renames something and changes the attributes then forgets about it...if you uninstall the program....it won't help at all
type ren window WINDOWS
i have a feeling that might let you boot up...MIGHT
deleting the program WILL have no effect..it will just leave the lock behind...(i tried it...) this program is not an ACTIVE LOCKER...(one that actually continually does something to lock the folders...which is the type that you can uninstall to remove the lock)...this one just renames something and changes the attributes then forgets about it...if you uninstall the program....it won't help at all
#109
Posted 07 April 2006 - 08:05 AM
I'm afraid I suggested an incorrect command back in post #95...an easy mistake to make, but it sure wouldn't have gained us the information I was looking for... Let's try it again with the correct folder name...
At C:\, type windows\sysbckup\dir /p
We're looking for files named something like rb001.cab, etc...
At C:\, type windows\sysbckup\dir /p
We're looking for files named something like rb001.cab, etc...
#110
Posted 07 April 2006 - 12:06 PM
wannabe1- nothing happened either with window or windows and the first word
dsenette - it wiuldn't let me change the name to windows apparently there is a file windows already originally window was the file "window~1 {21" that I renamed earlier. by the was I have a new screen to ask about. I realised that well duh the c:\ is a hidden directory so I reconfigured the Advanced CMOS Setup Boot Sequence to cd-rom, A:, C: after the realization that having it boot up C: first would trigger an error ( the registry/configuration error that was disallowing any cd-rom to run) and this screen came up (leaving out a few words here and there)
Caldera Dr Dos
Cache Size: 7670 kb (XMS)
Minimum cach size: 1024 km
Write-through drives: A B
Current Options:
/MLX
/BL=16
/LEND=ON
/DELAY=OFF
(there are some explinations after the /xxx above)
[DR-DOS]A:\>
Now I don't know if it means the bootable disk I made actually worked and by changing the startup sequence I was able to get it to boot or what but I figured I'd let you know. Any Ideas?
dsenette - it wiuldn't let me change the name to windows apparently there is a file windows already originally window was the file "window~1 {21" that I renamed earlier. by the was I have a new screen to ask about. I realised that well duh the c:\ is a hidden directory so I reconfigured the Advanced CMOS Setup Boot Sequence to cd-rom, A:, C: after the realization that having it boot up C: first would trigger an error ( the registry/configuration error that was disallowing any cd-rom to run) and this screen came up (leaving out a few words here and there)
Caldera Dr Dos
Cache Size: 7670 kb (XMS)
Minimum cach size: 1024 km
Write-through drives: A B
Current Options:
/MLX
/BL=16
/LEND=ON
/DELAY=OFF
(there are some explinations after the /xxx above)
[DR-DOS]A:\>
Now I don't know if it means the bootable disk I made actually worked and by changing the startup sequence I was able to get it to boot or what but I figured I'd let you know. Any Ideas?
#111
Posted 07 April 2006 - 01:46 PM
jkmira....from the c: prompt (not booting to the floppy drive..just boot normally to the c: prompt that y ou've been stuck at) type
dir /a /p
then write down EVERYTHING you see and post that with your next reply
dir /a /p
then write down EVERYTHING you see and post that with your next reply
#112
Posted 07 April 2006 - 04:28 PM
when I type dir /a /p I get this
screen 1
suhdlog dat
bootlog prv
frunlog txt
detlog txt
dos <dir>
diskette <dir>
dev <dir>
bin <dir>
bootlog txt
msdos sys
recycled <dir>
command com
config sys
screen 2
autoexec bat
em bat
em sys
config old
autoexec old
config dos
autoexec dos
dblspace bin
scandisk log
msdos ---
setuplog txt
netlog txt
progra~1 <dir>
temp <dir>
drvspace bin
mydocu~1 <dir>
system 1st
io sys
wpwin60 <dir>
wpc20 <dir>
npdsplay dll
iph ph
ffastun0 ffx
asd log
ffastun ffo
msoffice <dir>
ffastun ffl
ffastun ffa
screen 3
mymusi~1 <dir>
mplaye~1 <dir>
lxkz51 <dir>
window~1 bmk
expert <dir>
window~1 <dir>
szsite ini
windows <dir>
detlog old
unzipped <dir>
restart ini
os249510 bin
simsph~1 <dir>
setupxlg txt
pc100ez <dir>
~r_login nid
conexant <dir>
winform <dir>
config 001
npds zip
npwmsdrm dll
npdrmv2 dll
screen 4
npdrmv2 zip
instal~1 <dir>
install log
ram35 exe
config pss
instal~3 <dir>
instal~4 <dir>
autoexec pss
extrac~1 <dir>
design~1 <dir>
musicr~1 <dir>
r35help txt
tempel~1 <dir>
pl~2 qan
window <dir>
window above formally
window~1 {21
48 file(s) 8,153,171 bytes
screen 1
suhdlog dat
bootlog prv
frunlog txt
detlog txt
dos <dir>
diskette <dir>
dev <dir>
bin <dir>
bootlog txt
msdos sys
recycled <dir>
command com
config sys
screen 2
autoexec bat
em bat
em sys
config old
autoexec old
config dos
autoexec dos
dblspace bin
scandisk log
msdos ---
setuplog txt
netlog txt
progra~1 <dir>
temp <dir>
drvspace bin
mydocu~1 <dir>
system 1st
io sys
wpwin60 <dir>
wpc20 <dir>
npdsplay dll
iph ph
ffastun0 ffx
asd log
ffastun ffo
msoffice <dir>
ffastun ffl
ffastun ffa
screen 3
mymusi~1 <dir>
mplaye~1 <dir>
lxkz51 <dir>
window~1 bmk
expert <dir>
window~1 <dir>
szsite ini
windows <dir>
detlog old
unzipped <dir>
restart ini
os249510 bin
simsph~1 <dir>
setupxlg txt
pc100ez <dir>
~r_login nid
conexant <dir>
winform <dir>
config 001
npds zip
npwmsdrm dll
npdrmv2 dll
screen 4
npdrmv2 zip
instal~1 <dir>
install log
ram35 exe
config pss
instal~3 <dir>
instal~4 <dir>
autoexec pss
extrac~1 <dir>
design~1 <dir>
musicr~1 <dir>
r35help txt
tempel~1 <dir>
pl~2 qan
window <dir>
window above formally
window~1 {21
48 file(s) 8,153,171 bytes
Attached Files
#113
Posted 07 April 2006 - 04:52 PM
type cd windows then do dir /a /p and do the same but only list anything showing up with the .{21
#114
Posted 08 April 2006 - 12:12 AM
the only thing that came up was this
. <dir>
.. <dir>
desktop <dir>
alluse~1 <dir>
shelli~1
recent <dir>
temp <dir>
sysbckup <dir>
I saw nothing with {21
. <dir>
.. <dir>
desktop <dir>
alluse~1 <dir>
shelli~1
recent <dir>
temp <dir>
sysbckup <dir>
I saw nothing with {21
#115
Posted 08 April 2006 - 07:14 AM
ok....from the windows directory type cd .. (include the periods as that will jump you back up a directoryr) now you should be at the c: prompt
type
cd window
dir /a /p
tell me what you see there
(trying to figure out which of those two folders is the real windows folder as in highlander....there can be only one.)
type
cd window
dir /a /p
tell me what you see there
(trying to figure out which of those two folders is the real windows folder as in highlander....there can be only one.)
#116
Posted 08 April 2006 - 12:55 PM
I typed in cd window and there was 21 screens of filenames I didn't see any {21 files (except window which was window~1 {21 originally before it was renamed)
#117
Posted 10 April 2006 - 07:40 AM
ok at the c: prompt type
ren windows windold
then
ren window WINDOWS
now try to boot the pc
ren windows windold
then
ren window WINDOWS
now try to boot the pc
#118
Posted 10 April 2006 - 05:04 PM
I wanted to say thanks for all the help. I did some reading and research and was able to build a windows file buy copying the necessary files I needed to boot windows in a safe mode and than I accessed the program that was effecting the c:\ drive. and unlocked everything there by fixing the problem. The only thing that was really hard was finding all the files I needed in different directories and copying them so suficite to say I won't be needing anymore assistance on this problem thanks again
#119
Posted 10 April 2006 - 05:07 PM
Well Done!!! Hand this man a
wannabe1
wannabe1
#120
Posted 10 April 2006 - 05:45 PM
Well Done
Edited by peterm, 10 April 2006 - 05:51 PM.
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users