Page 1 of 2

Strange thing while ARWINSS installation

Posted: Mon Mar 29, 2010 5:03 pm
by wildschwein
I use virtualbox and tested ARWINSS 45997

I need to install it three times, because it hangs three times. THIS IS REPRODUCEABLE !

First: Black screen after booting from CD

Reseting machine

Second: Hang while formating virtual harddisc

Reseting machine

Third: Hangs at the begining of the file copy process

Reseting machine

goes through and installs and runs fine !

THIS IS REPRODUCEABLE !

Another strange thing: With same virtual machine configuration, bootcd-46566 (latest automatically build)
hangs after pressing NEXT from Ros Installing Wizard.

Anybody an idea ?

Re: Strange thing while ARWINSS installation

Posted: Tue Mar 30, 2010 1:56 pm
by wojo664
Give us a debug log. For me it looks like our infamous Uniata bug..

Try these drivers and write the reasults here
http://www.reactos.org/forum/viewtopic.php?f=2&t=8058

Re: Strange thing while ARWINSS installation

Posted: Tue Mar 30, 2010 2:46 pm
by wildschwein
Ok. I managed it, to get debug logs ! hehehehe....

here it is:

I hope you can see, were the breaks between the trys are.
A part of the log is the last successfully start of ARWINSS...
USB was deactivated in virtualbox during install, because ARWINSS won't run with activated USB.

(ntoskrnl\kd\kdio.c:297) -------------------4) \reactos\
WARNING: HalStopProfileInterrupt atpace
(ntoskrnl\mm\mminit.c:328ed but not yet taken advantage of
(ntoskrnl\ke\i386\patpge.c:62) PAT support detected but not yet taken advantage of
(ntoskrnl\ke\i386\mtrr.c:24) MTRR support detected but not yet taken advantage of
PC Compatible Eisa/Isa HAL has been initialized
l\io\iomgr\iorsrce.c:700 is UNIMPLEMENTED!
(ntoskrnl\io\iomgr\driver.c:1391) '\Driver\BUSLOGIC' initializale 0
(ntoskrnl\fstub\disksup.c:1487) FSTUB: (IoReadPartitionTable) No 0xaa55 found in partition table 0
(ntoskrnl\io\iomgr\file.c:420) Using found4
(drivers\filesystems\cdfs\common.c:107) ST: 0x0000006f
(0x80000016,0x00000000,0x00000000,0x00000000)

Entered debugger on embedded INT3 at 0x0008:0x808dba94.
kdb:> (ntoskrnl\kd\kdio.c:297) --------------------) \reactos\
WARNING: HalStopProfileInterrupt at hal\halx86\generic\profi.c:328) yet taken advantage of
(ntoskrnl\ke\i386\patpge.c:62) PAT support detected but not yet taken advantage of
(ntoskrnl\ke\i386\mtrr.c:24) MTRR support detected but not yet taken advantage of
PC Compatible Eisa/Isa HAL has been ge at ntoskrnl\io\iomgr\iorsrce.c:700 is UNIMPLEMENTED!
(ntoskrnl\io\iomgr\driver.c:1391) '\Driver\BUSLOGIC' initializble 0
(ntoskrnl\fstub\disksup.c:1487) FSTUB: (IoReadPartitionTable) No 0xaa55 found in partition tablercName\multi(0)disk(0)rdisk(1), status=c0000034
(drivers\filesystems\cdfs\common.c:196) STA01) IoVerifyVolume() returned (Status 0)
(drivers\filesystems\cdfs\create.c:148) Status 80000016
(lib\cmlib\hib\cmlib\hivewrt.c:26) FIXME: HvpWriteLog doesn't do anything atm
(ntoskrnl\kd\kdio.c:297) ----------)cdrom(224) \reactos\
WARNINGce
(ntoskrntected but not yet taken advantage of
(ntoskrnl\ke\i386\mtrr.c:24) MTRR support detected but not yet taken00 is UNIMPLEMENTED!
WARNING: IoReportReation
(ntoskrnl\fstub\disksup.c:1487) FSTl\fstub\disksup.c:253) ZwOpenSymbolicLinkObject failed for \ArcName\multi(0)disk(0)rdisk(1), status=c0000034
(ntoskrnl\io\iomgr\file.c:420) Using IopParin partition table 0
(ntoskrnl\io\iomgr\file.c:420) Using IopParseDevice() hack. Requested invalid attributes: 1017f
(ntoskrnl\io\iomgr\file.c:420) Using Ialid attribu.c:420ested invalid attributes: 116
(base\setup\usetup\bootsup.c:2060) No or unknown boot loader found
(ntoskrnl\kd\kdio.c:297) -----------------224) \reactos\
WARNINGce
(ntoskrntected but not yet taken advantage of
(ntoskrnl\ke\i386\mtrr.c:24) MTRR support detected but not yet taken advantage oEMENTED!
WARNING: IoReportResourceUsage at ntous (0xc00000c0)
(ntoskrnl\io\iomgr\file.c:420) multi(0)disk(0)rdisk(1), status=c0000034
(ntoskrnl\io\iomgr\file.c:420) Using IopParseDevice() hack. Requested invalid attributes: 1
(ntoskrnl\io\iomgr\file.c:420) Using IopParseDevributes: 9
(ntoskrnl\io\iomgr\file.c:420) Using IopParseDevice() hack. Requested invalid attributes: 116
(base\setup\usetup\bootsup.c:2060) No or unknown boot loader found
(ntoskrnl\io\iomgr\file.c:420) Usininvalid attributes: 9
(ntoskrnl\io\iomgr\file.c:420) Using IopParseDevice() hack. Requested invalid attributes: 116
(lib\cmlib\hivewrt.c:26) FIXME: HvpWriteLog pWriteLog doIXME: HvpWriteLog doesn't do anything atm
(ntoskrnl\kd\kdio.c:297) -----------------n(1) \ multi(0)disk(0)rdisk(0)pn Paged Pool Expansion PTE Space
(ntoskrntected but not yet taken advantage of
(ntoskrnl\ke\i386\mtrr.c:24) MTRR support detected but not yet taken advanUNIMPLEMENTED!
WARNING: IoReportResourceUsage at ntous (0xc00000c0)
wood_uhci: Entering DriverEntry(), driver' initialization failed, status (0xc0000001)
(ntoskrnl\io\iomgr\file.c:420) Uadvantage of
(subsystems\win32\win32k\main\init.c:277) Win32k initialization: DO FB61AC70, RegPath <NULL>
(subsystems\win32\win32k\eng\engsurf.c:337) flHooks: 0x0
fixme:(dll\win32\user32\legacy.c:37) PrivateCsrssManualGuiCheck is UNIMPLEMENTED!
(subsystems\win32\win32k\main\csr.c:48) Win32k registered with CSRSS
(subsystems\win32\win32k\wine\winstation.c:370) close_timeout for this process is not done yet!
fixme:(dll\winot done yet!
(subsystems\win32\win32k\wine\winstation.c:370) close_tiinfo at subsystems\win32\win32k\wine\stubs.c:608 is UNIMPLEMENTED!
fixme:(dll\win32\user32\win.c:3320) (hwnd 00000008) stub!
(subsystems\win32\win32k\wine\winstation.c:370) close_timeout for this process is not done yet!
(subsystems\win32\win32k\wine\winstation.c:370) close_timeout for this process is not done yet!
(dll\ntdll\ldr\utils.c:2355) Relocbsystems\win32\win32k\wine\stubs.c:608 is UNIMPLEMENTED!
(subsystems\win32\win32k\wine\winstation.c:370) close_timeout for this process is not done yet!
err:(dll\win32\shell32\shellpath.c:1468) path for default container 2
(dll\ntdll\ldr\utils.c:2355) Relocating (77400000 -> 00A74000) C:\ReactOS\system32\msacm32.dll
err:(dll\win32\setupapi\queue.c:1659) copy error 2 L"C:\\\win32k\wine\stubs.c:608 is UNIMPLEMENTED!
(subsystems\win32\win32k\wine\winstation.c:370) close_timeout for this process is not done yet!
err:(dll\win32\shell32\shellpath.c:1468\Local Settdefault container 2
(dll\ntdll\ldr\utils.c:2355) Relocating (77400000 -> 00A74000) C:\ReactOS\system32\msacm32.dll
err:(dll\win32\setupapi\queue.c:1659) copy error 2 L"C:\\ReactOS\wine\stubs.c:608 is UNIMPLEMENTED!
(subsystems\win32\win32k\wine\winstation.c:370) close_timeout for this process is not done yet!
err:(dll\win32\shell32\shellpath.c:1468) Failed to ch.c:1468) Faile 2
(dll\ntdll\ldr\utils.c:2355) Relocating (77400000 -> 00A74000) C:\ReactOS\system32\msacm32.dll
WARNING: req_set_clipboard_info at subsystems\win32\win32k\wine\stubs.c:608 is UNIMPLEMENTED!
fixme:(dll\win32\winent.drv\userdr
fixme:(dll\win32tyle isMPLEMENTED!
WARNING: GreSetCursor at subsystems\win32\win32k\gre\cursoricon.c:142 is UNIMPLEMENTED!
WARNING: GreSetCursor at subsystems\win32\win32k\gre\cursoricon.c:142 is UNIMPLEMENTED!
fixme:(dll\win32\winent.drv\userdrv.c:8
fixme:(dll\win32\winent.drv\userdrv.c:825) RosDrv_SetWindowStyle is UNIMPLEMENTED!
fixme:(dll\win32\winent.drv\userdrv.c:82osDrv_SetWindowStyle is UNIMPLEMENTED!
WARNING: GreSetCursor at subsystems\win32\win32k\gre\cursoricon.c:142 is UNIMPLEMENTED!
WARNING: GreSetCursor at subsystems\win32\win32k\gre\cursoricon.c:142 is UNIMPLEMENTED!
WARNING: GreSetCursor at subsystems\win32\win32k\gre\cursoricon.c:142 is UNIMPLEMENTED!
WARNING: GreSetCursor at subsystems\win32\win32k\gre\cursoricon.c:142 is UNIMPLEMENTED!
WARNING: GreSetCursor at subsystems\win32\win32k\gre\cursoricon.c:142 is UNIMPLEMENTED!
WARNING: GreSetCursor at subsystems\win32\win32k\gre\cursoricon.c:142 is UNIMPLEMENTED!
fixme:(dll\win32\winent.drv\userdrv.c:825) Ro_SetWindowStyle is UNIMPLEMENTED!
WARNING: GreSetCursor at subsystems\win32\win32k\gre\cursoricon.c:142 is UNIMPLEMENTED!
WARNING: GreSetCursor at subsystems\win32\win32k\gre\cursoricon.c:142 is UNIMPLEMENTED!
WARNING: GreSetCursor at subsystems\win32\win32k\gre\cursoricon.c:142 is UNIMPLEMENTED!
WARNING: GreSetCursor at subsystems\win32\win32k\gre\cursoricon.c:142 is UNIMPLEMENTED!
WARNING: GreSetCursor at subsystems\win32\win32k\gre\cursoricon.c:142 is UNIMPLEMENTED!
WARNING: GreSetCursor at subsystems\win32\win32k\gre\cursoricon.c:142 is UNIMPLEMENTED!
WARNING: GreSetCursor at subsystems\win32\win32k\gre\cursoricon.c:142 is UNIMPLEMENTED!
WARNING: GreSetCursor at subsystems\win32\win32k\gre\cursoricon.c:142 is UNIMPLEMENTED!
WARNING: GreSetCursor at subsystems\win32\win32k\gre\cursoricon.c:142 is UNIMPLEMENTED!
WARNING: GreSetCursor at subsystems\win32\win32k\gre\cursoricon.c:142 is UNIMPLEMENTED!

Re: Strange thing while ARWINSS installation

Posted: Tue Mar 30, 2010 3:33 pm
by hefner
u know how to use Bugzilla ? It has a upload - function.

To post a Debug - Log in the forum ist a little bit "messy" ;)

Re: Strange thing while ARWINSS installation

Posted: Tue Mar 30, 2010 4:48 pm
by gabrielilardi
hefner wrote:u know how to use Bugzilla ? It has a upload - function.

To post a Debug - Log in the forum ist a little bit "messy" ;)
The debug log is messed itself in origin, this is a known issue anyway, please don't add another bug report for it.

Re: Strange thing while ARWINSS installation

Posted: Tue Mar 30, 2010 11:17 pm
by Haos
drivers\filesystems\cdfs\common.c:196) STA01) IoVerifyVolume() returned (Status 0)
90% its uniata timing bug. Please use vt-x in vbox if your processor is capable of supporting it. Else, use custom uniata.sys from wojo's thread.

Re: Strange thing while ARWINSS installation

Posted: Thu Apr 01, 2010 8:58 am
by wildschwein
sorry for posting log here. I managed to put it in bugzilla.

Slowly, very slowly, i understand how things and people work together here...

Re: Strange thing while ARWINSS installation

Posted: Thu Apr 01, 2010 1:12 pm
by gabrielilardi
wildschwein wrote:sorry for posting log here. I managed to put it in bugzilla.

Slowly, very slowly, i understand how things and people work together here...
What about:
...this is a known issue anyway, please don't add another bug report for it.

Re: Strange thing while ARWINSS installation

Posted: Sat Apr 24, 2010 7:28 am
by RaptorEmperor
wildschwein wrote:sorry for posting log here. I managed to put it in bugzilla.

Slowly, very slowly, i understand how things and people work together here...
Don't worry, it takes a little getting used to. I just learned how to do a bug report less than a year ago, and I've been dabbling with ReactOS since 2006 or so.

I haven't done much lately, though. Too caught up with classes. :P

Re: Strange thing while ARWINSS installation

Posted: Wed Dec 15, 2010 10:51 pm
by andy-123
Hello,

i had the same problem with non-arwinss build. I figured out that changing the Windows-Version (in Virtualbox) to "Windows NT 4" solves the problem.
Maybe you can try and report if it works for you too.

Thanks

Andy

Re: Strange thing while ARWINSS installation

Posted: Mon Dec 20, 2010 5:10 am
by livestrong23
If anyone else need help debugging in VB here is a link below
http://www.haikuware.com/wikis/doku.php ... aiku-guest

I have to say though that ARWINSS is nothing more than a waste of time and a distraction.

Re: Strange thing while ARWINSS installation

Posted: Mon Dec 20, 2010 3:43 pm
by Black_Fox
As can be said about ROS, but still we love it and improve it as it's ours.

Re: Strange thing while ARWINSS installation

Posted: Mon Dec 20, 2010 4:17 pm
by Aeneas
Thing is, I doubt many people care too much about the internals. - Windows is not attractive to most people (i.e., non-IT-people) because of its internal design - but because people are just able to run on it with little hassle anything from software for selling lawn mowers to programs aiding evaluation of satellite imagery. It is the sheer unending sea of software products, both free as well as perfectly closer-source and commercial, which attracts people. - I just wanted to mention this in order to keep this idea Arwinss vs. "pure" system into perspective.

(And I personally like the idea of Arwinss more; I believe a "clean product" which is being put out in another decade or so is actually less advantageous than a "quick and dirty" one which, however, works "well enough" TODAY. For the "clean" variant targets better long-term compatibility, yet I doubt that one can rely too much on this anyway in case Microsoft decides to somehow introduce incompatibility to ROS on purpose.)

Re: Strange thing while ARWINSS installation

Posted: Mon Dec 20, 2010 6:17 pm
by livestrong23
Well Microsoft does do their best to break wine compatibility with MS apps from time to time. I'm sure the same MS dll checks will reflect on ARWINISS "as well as the RoS Trunk" as we use the majority of Wine's DLLs.

Re: Strange thing while ARWINSS installation

Posted: Mon Dec 20, 2010 9:25 pm
by vicmarcal
It is moving to offtopic, but i think that "MS wine checks".( in order to detect wine code and avoid linu+wine or arwinss working) is totally illegal and sueable.
A Win32 app is designed to run in any win32-compatible OS as ReactOs,Windows,LUK are. Forcing a win32 app to work just in one specific win32OS( windows) is an obvious way to avoid competency.