nothing happens!
even there was no explorer.exe process created in task manager
MS explorer.exe don't work on Reactos
Moderator: Moderator Team
-
manatails007
- Posts: 96
- Joined: Sat Jan 19, 2008 1:52 pm
- Location: Crystal river
MS explorer.exe don't work on Reactos
I terminated explorer.exe process in task manager and I executed MS's explorer.exe(XP Professional SP2) and....
nothing happens!
even there was no explorer.exe process created in task manager
nothing happens!
even there was no explorer.exe process created in task manager
Last edited by manatails007 on Sat Feb 09, 2008 1:10 pm, edited 2 times in total.
MS 2003 windows explorer does not use any. Safe one I know to play with.
If there is another version that is safe speak up.
I had a list on the syscalls older windows explorer in early NT used it was for functions that were not exported. I know it changed with the functions 2003 exports. Might have changed in XP too.
Missing api function or missing syscalls missing caused some of the older windows explorer to go nuts on wine and created 1000's of trash files. Yes normal creation functions with randomly generated filenames. That feature is also missing from MS 2003 windows explorer. So its a safe one to play with on something incomplete because its not going to do other stupid things.
Basically if you know safe version list. We really don't need the same insane mess I seen in wine in reactos. If the version that was played with was insane we should be thankful that it did not work.
If there is another version that is safe speak up.
I had a list on the syscalls older windows explorer in early NT used it was for functions that were not exported. I know it changed with the functions 2003 exports. Might have changed in XP too.
Missing api function or missing syscalls missing caused some of the older windows explorer to go nuts on wine and created 1000's of trash files. Yes normal creation functions with randomly generated filenames. That feature is also missing from MS 2003 windows explorer. So its a safe one to play with on something incomplete because its not going to do other stupid things.
Basically if you know safe version list. We really don't need the same insane mess I seen in wine in reactos. If the version that was played with was insane we should be thankful that it did not work.
Oiaohm I think you're getting confused between exported API's and syscalls.
Syscalls are talking to the kernel, and require switching context and interrupt handlers etc.
exported functions in exported API's are just programs talking to each, so not neccesarily syscalls.
Although what you say about wierd behaviour of explorer in wine is true. Creating thousands of garbage files, (and in wine's case reports of it trying to draw the desktop, but that wouldn't be an issue under ROS...)
Syscalls are talking to the kernel, and require switching context and interrupt handlers etc.
exported functions in exported API's are just programs talking to each, so not neccesarily syscalls.
Although what you say about wierd behaviour of explorer in wine is true. Creating thousands of garbage files, (and in wine's case reports of it trying to draw the desktop, but that wouldn't be an issue under ROS...)
Wine running MS Windows Explorer and having the run away file creation.
Windows XP no patches or service packs known to do it. Windows 2003 no patches known not to do it instead just dies cleanly. So now SP1 or SP2 XP never tested to see what it does. I would suspect SP2/SP3 fixed the same way as 2003 or at least hope so. What it does in wine seams to be a alternate line that was never meant to happen. If a function it needs is missing and stubed we might find another cause of it.
Sorry ged I mixed my information together. Its the stuff that done as pre 3.5 NT done as syscalls first then converted into ntdll.dll entries. If does not work seams to be the trigger for some applications of windows into going off rails. Very much if this fails to return correct value system will be dead so no need to worry were the code will go next. It also appears from reading ros might be 100 percent safe from it. Since ros most likely will fail not do a wine try to go forward and expect good internal application bug checking. As normal lot of applications don't handle the unexpected api answers very well.
Sorry everyone I over reacted. Long term memory left out the links.
Windows XP no patches or service packs known to do it. Windows 2003 no patches known not to do it instead just dies cleanly. So now SP1 or SP2 XP never tested to see what it does. I would suspect SP2/SP3 fixed the same way as 2003 or at least hope so. What it does in wine seams to be a alternate line that was never meant to happen. If a function it needs is missing and stubed we might find another cause of it.
Sorry ged I mixed my information together. Its the stuff that done as pre 3.5 NT done as syscalls first then converted into ntdll.dll entries. If does not work seams to be the trigger for some applications of windows into going off rails. Very much if this fails to return correct value system will be dead so no need to worry were the code will go next. It also appears from reading ros might be 100 percent safe from it. Since ros most likely will fail not do a wine try to go forward and expect good internal application bug checking. As normal lot of applications don't handle the unexpected api answers very well.
Sorry everyone I over reacted. Long term memory left out the links.
Who is online
Users browsing this forum: Semrush [Bot] and 1 guest