Jump to content

oomek

Member
  • Posts

    133
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Everything posted by oomek

  1. Bro, did you just go full retard? I'm sure that one topic would have been enough to notice your app.
  2. Some of you are getting an exception saying "Access denied" when launching on screen keyboard. I wish to hear from you when that happens, so I could fix it before I'll release the 2.0 final.
  3. Not really, it's the only way to access XBStart option or to close the app. Wy won't you just hide the unnecessary icons like everyone elese? http://www.eightforums.com/attachments/tutorials/32406d1385497540-bluetooth-notification-icon-turn-off-windows-bluetooth_notification_area_icons_settings.jpg
  4. Just UNTICK "Show this window every time XBStart launches" on the help screen.
  5. Thanks for your input jaclaz. I ve sent my drive to a company claiming to fix the HDDs from £97. After the diagnosis those £97 went up to £290 initial payment and £190 after the work is done. It's sad how these companies rip people off. The new drive costs £70 so they want £410 for a head replacement. I had do pass because it's way over my budget, but at least I already know what's broken.
  6. I've managed to disassemble the xbstart.exe and toastnotification.dll and recovered the sourcecode. I'm rearranging it now to make a workable project out of it. After that you may expect a new beta release with some bugs fixed.
  7. If, by any chance, it is a 7200.11, it is possible that fixing it will be much cheaper than that.We have "saved" in the past a few hundreds (possibly more) of such disks:http://www.msfn.org/board/forum/169-hard-drive-and-removable-media-issues/with just a few bucks/Euros needed for the TTL adapter.jaclazI heard about that issue with the old Barracudas, mine is unfortunately 7200.14 ST3000DM001. It spins up, makes about 10 clicks and spins down. Not visible in the bios or Windows. I've recorded a video, so maybe with your experience you could fortell the source of the problem, whether it's PCB or mechanical failure. If it's PCB i could try to find a donor and transfuse the flash chip, as i'm skilled well enough in soldering. EDIT: Well, the PCB I got from Canada didn't work. I guess this is the end of story, as I can't afford the clean room recovery.
  8. I was trying Reflector but wasn't happy with the result. Does this netpeek extract the embedded resources as well? Thanks God that at the last moment I've decided to NOT obfuscate the exe.
  9. INPORTANT ANNOUNCMENT: XBStart 2.0 beta will be my last release. My HDD died just the day after I posted the installer and all my source code has gone. Maybe It's recoverable, maybe not, but I do not have a spare £300 at the moment to find out. Little advice, don't buy Seagate drives, EVER! EDIT: I've managed to decompile the XBStart.exe and recover my sourcecode. You may expect a new version soon.
  10. XBStart version 2.0 beta 1 released edit: added missing dll's to the installer, please re-download the file.
  11. My dwmcore.dll has version 17041 not 17031 but it's working well without symbol files. Btw what does this line mean? [2014-04-21 19:57:08][0x1794:0x1C08] Delayed hook (UxTheme.dll!GetThemeStream from udwm.dll) installed may it be the cause of the startup delay? debug.log
  12. Symbols are downloading fine, but to ProgramData folder. I've tried even to move the aero folder to \AppData\Local\ but still the same delay occurs. Luckily after that I got one error in the log file. [2014-04-15 15:22:20][0x1068:0x106C] Account error: 122 - The data area passed to a system call is too small. Edit: Finaly, i've managed to set debug logging, is there anything in that log that would explain that initialization delay? [2014-04-15 17:45:56][0x368:0x9C4] Message 0x320, wparam = 1157627904, lparam = 1 [2014-04-15 17:45:56][0x368:0x9C4] Loading settings (flags = 0x2) from HKEY 0x000000000000037C for session #2 [2014-04-15 17:45:56][0x368:0x9C4] Settings reloaded [2014-04-15 17:45:56][0x368:0x9C4] Message 0x15, wparam = 0, lparam = 0 [2014-04-15 17:45:56][0x368:0x9C4] Message 0x2B1, wparam = 6, lparam = 2 [2014-04-15 17:45:56][0x368:0x9C4] Message 0x219, wparam = 7, lparam = 0 [2014-04-15 17:45:56][0x368:0x9C4] Message 0x219, wparam = 7, lparam = 0 [2014-04-15 17:46:32][0x614:0x618] Installing DWM hook... [2014-04-15 17:46:32][0x614:0x618] User: SYSTEM [2014-04-15 17:46:32][0x614:0x618] Module: C:\ProgramData\dbg\AERO\dwmglass.dll and another just now: [2014-04-15 17:58:54][0x5E0:0x5E4] Installing DWM hook... [2014-04-15 17:58:54][0x5E0:0x5E4] User: SYSTEM [2014-04-15 17:58:54][0x5E0:0x5E4] Module: C:\ProgramData\dbg\AERO\dwmglass.dll [2014-04-15 17:58:56][0x5E0:0x5E4] CreateRemoteThread failed with error 5 - Access is denied.
  13. Hmm, That's definitely not the case in my setup, but I've doublechecked it just in case of a sudden onset of amnesia, so AppInit_DLLs is set to null, permissions of the AERO directory are set to full for SYSTEM, Administrators, Users and my account name. From 3rd party tweaks I have only Classic Start Menu 4.0.4 installed and UXTheme Multi-Patcher 9.0 for Windows 8/8.1 Edit: I've realised that i'm having a slight delay in LAN initialisation probably caused by the drivers which I'm investigating atm. Is there any dependency between the network access and the aerohost initialisation time?
  14. Can you give me some advice what may be the cause of not logging the debug information? Yes, the key is under HKLM.
  15. Help! or I'll nuts. I'm still getting a random delay in aerohost initialization (5-30 sec) after every boot. EnableLogging debug shows nothing except: [2014-04-15 13:49:08][0x84C:0x850] Installing DWM hook... [2014-04-15 13:49:09][0x84C:0x850] User: SYSTEM [2014-04-15 13:49:10][0x84C:0x850] Module: D:\APPS\TOOLS\AERO\dwmglass.dll I've checked permissions, scheduled task and symbols, and everything seems to be normal. I've tried netplwiz (logon with and without password) but still that delay in loading is getting on my nerves. What am I missing? Anyone?
  16. Webhost i'm using is case sensitive, maybe some proxy mechanism on your ISP side is causing that.
  17. I've had the same yesterday. According to my investigation, it's caused by one of the recent windows updates which rendered some of the msstyles unusable (i believe those edited with the resource editor are malfunctioning, those made with vista style builder are working fine). It happened before aeroglass 1.2 update and it also gives the black screen with aeroglass disabled. If you are able to roll back to the recent restore point do it and apply a default windows theme. After that reinstall all pending updates reverted during restore. That's what i've done. Now I'm converting my style with Vista Style Editor to make it usable again.
  18. Could anyone confirm if it's working after Windows 8.1 updates dated 12 Feb 2014 ?
×
×
  • Create New...