Jump to content

UCyborg

Platinum Sponsor
 View Profile  See their activity

  • Posts

    2,631

  • Joined

  • Last visited

  • Days Won

    28

  • Donations

    100.00 USD 

  • Country

    Slovenia

 Content Type 

Posts posted by UCyborg

    Chrome 74 - Glass no longer supported in title bars!

    in Aero Glass For Windows 8+

    Posted · Edited by UCyborg

    Apparently my assumptions were incorrect, and so is this thread's title. I searched through Chromium's commit history and found out only the option in chrome://flags was removed, the functionality is still intact and can be invoked using a command line parameter, see here.

    So one must add --disable-features=Windows10CustomTitlebar parameter to Chrome's shortcut properties, at the end of the Target field on the Shortcut tab.

    61pS3UV.png

    This method doesn't have any undesired side effects like running in compatibility mode has.

    5

    Firefox Nightly 66.0a1 fixed Mini/Max/close Aeroglass

    in Aero Glass For Windows 8+

    Posted

    On 2/6/2019 at 2:04 AM, UCyborg said:

    Ideally, someone would figure out how to change it properly at CSS level.

    Figured that's impossible; I found the following code at widget/windows/nsWindow.cpp: 

    // Glass hit testing w/custom transparent margins
LRESULT dwmHitResult;
if (mCustomNonClient &&
    nsUXThemeData::CheckForCompositor() &&
    /* We don't do this for win10 glass with a custom titlebar,
     * in order to avoid the caption buttons breaking. */
    !(IsWin10OrLater() && HasGlass()) &&
    WinUtils::dwmDwmDefWindowProcPtr(mWnd, msg, wParam, lParam, &dwmHitResult)) {
  *aRetValue = dwmHitResult;
  return true;
}

    Stock caption buttons are effectively disabled on Windows 10. The behavior is hardcoded in xul.dll. If one searches for Windows version checks, there are some other parts of the code that will behave differently depending on the detected Windows version.

    0

    Audio driver for Realtek HD Audio Hardware? [Testing thread]

    in Pinned Topics regarding 9x/ME

    Posted

    On 4/14/2019 at 11:13 AM, deomsh said:

    I didn't ment to offend you. I am not an expert either, I only tried to say that using "facts" from experiences with other drivers like AC'97 doesn't say anything to me.

    You didn't answer my question if you could give the HDA controller an EXCLUSIVE IRQ. If that's possible on your system and you have still choppy audio, I would tend to agree that IRQ's are not a (possible) problem.

    I did try all possible IRQ values, it always sounds the same. Again, changing it is only possible on Windows 95, on Windows 98 I'm stuck with 11. I don't know how to tell whether IRQ is exclusive or not. I also tried HDAICOUT.HDA that comes with the driver, nothing changed.

    On 4/14/2019 at 11:13 AM, deomsh said:

    It would of interest too try MS-DOS HDA players, like I suggested Dave-H, but with respect to choppy audio.

    I tried Mpxplay, but only got silence.

    On 4/14/2019 at 11:13 AM, deomsh said:

    About volume setting for your virtual STAC9921 codec: I have red somewhere that it's not fully implemented in VirtualBox. If you have some spare time I'd like to see the codec graph.

    khmnQFB.png

    0

    The desktop of Windows 8 (9200) logs me out after installing Big Muscle's aero glass.

    in Windows 8

    Posted

    Haven't heard about that problem before. I get very obvious visual anomalies on my end, something to do with lack of certain optimizations that only later versions of Aero Glass have. The problem is more profound when ran on virtual machine due to worse graphics performance.

    Maybe there's something interesting in C:\AeroGlass\debug.log and in Event Viewer. You should be able to reboot to Safe Mode and access those things from there.

    0

    Finally fixed Aero Glass to work on Chrome (Windows 10)

    in Aero Glass For Windows 8+

    Posted

    4 hours ago, Semtex said:

    it is not so that I don't use "search" option

    That wasn't directed at you specifically, but those that keep creating new threads even though they could post in the old existing threads.

    I've no clue what the problem on your end is because the transparency part has always worked on my end. Actually, with my custom theme in Windows, I get some transparency even without using userChrome.css (no idea why that works in the first place):

    dxI2lig.png

    The frame goes solid black after turning on dark mode:

    pT2P6h3.png

    Creating the userChrome.css with the following content... 

    #main-window {
  background-color: transparent !important;
  -moz-appearance: -moz-win-glass !important;
}

.titlebar-button {
  opacity: 0 !important;
}

    ...gives this:

    WmVMx4M.png

    Built-in CSS sets display property of .titlebar-button to none on Windows 7, but that doesn't help on Windows 10 due to some hardcoded behavior; it just completely disables the ability to use those buttons.

    If you turn off critical CSS files in Style Editor such as browser.css (there are 2 files called browser.css), you can still minimize/maximize/close Firefox window with the caption buttons on Windows 7/8.x, but not on Windows 10.

    So yeah, not all behavior can be changed with CSS alone. It would require some modifications to Firefox's source code.

    1

    Finally fixed Aero Glass to work on Chrome (Windows 10)

    in Aero Glass For Windows 8+

    Posted

    21 hours ago, Semtex said:

    Yeah, it is working with latest Firefox Nightly, but there is one big problem with this patch, it is setting Firefox in light theme, not supporting dark one, any chance to get support for dark theme?

    That's because it doesn't do anything impressive, it just makes Firefox unaware of the fact that it's running on Windows 10. And since dark mode is Windows 10 thing, it won't work if it's run in the context of the older OS.

    0

    Audio driver for Realtek HD Audio Hardware? [Testing thread]

    in Pinned Topics regarding 9x/ME

    Posted · Edited by UCyborg

    On 4/11/2019 at 1:46 AM, deomsh said:

    Thanks for testing, does your IRQ-changing imply that the Controller had an exlusive IRQ? I am sorry but I can't understand your logic of facts related to a (even virtual) AC'97 controller.

    I'm not an expert when it comes to IRQs, I can only tell what I've seen.

    On 4/11/2019 at 1:46 AM, deomsh said:

    About your Choppy sound: maybe a silly question. Did you rule out Guest/Host problems? How's HDA-sound with W2K or XP? I saw some interesting HDA-correspondence on the VirtualBox-Forum about W2k/XP and even WIN10 as a Guest (mainly on older versions of VirtualBox).

    No issues on Windows 7 guest. No driver I tried worked on Windows XP though, got the error that the device cannot start (code 10) in Device Manager.

    On 4/11/2019 at 1:46 AM, deomsh said:

    Your (Virtual) HDA Codec should be STAC9221. According to the data sheet: "VolumeKnob Node (NID = 0x16)". So try VolumeWidget=$16 if you like.

    Doesn't help with anything, including volume control.

    0

    Audio driver for Realtek HD Audio Hardware? [Testing thread]

    in Pinned Topics regarding 9x/ME

    Posted

    On 4/8/2019 at 9:40 AM, deomsh said:

    Can you tell what version of VirtualBox you are using?

    6.0.4

    On 4/8/2019 at 9:40 AM, deomsh said:

    I'd like to see your HDACFG.INI too.

     

    [ALLHDA]
    $0028=$26688086

    [HDA]
    TSR=TSR Found
    PCI_VID=$8086
    PCI_DID=$2668

    [BUSMASTER]
    myPCIHI=$0012
    myPCILO=$1000
    myPCI=$00121000
    aPCIHI=$0011
    aPCILO=$1000
    aPCI=$00111000

    [HDA_26688086,76808384]
    cardmemregistersLO=$4000
    cardmemregistersHI=$F080
    Mytimer=1
    Verbinterface=$1
    wait1=$100
    wait2=$100
    pcipatchB=$0000
    PCI_BUS=$00
    PCI_DEVICE=$05
    PCI_FUNCTION=$0
    GCAP=$4401
    VMIN=$00
    VMAJ=$01
    GCTL=$0001
    CODEC BITMAP=00000001
    CODEC Index=$0
    CODEC_VID=$8384
    CODEC_DID=$7680
    CODEC_REV=$103401
    CODEC_NODEINFO=$010001
    CODEC_AFG_GPIO_CAP=$C0000004
    CODEC_AFG_SUBSYSTEM_ID=$83847680
    CODEC_AFG_PM_SUPPORT=$0F
    CODEC_AFG_PCM_DEFINITION=$20020
    CODEC_AFG_F000B=$01
    SleepingWidget=$02
    VolumeWidget=$14
    OutputWidget=$02

    On 4/8/2019 at 2:40 PM, deomsh said:

    Regarding IRQ's: maybe it was'nt clear what I ment. I am not a native speaker, sorry for my poor English. I did not ment an IRQ-conflict, but IRQ-sharing.

    Oh, well, 11 was chosen by default, so I tried 10, 9 and 5. No change, sound remained choppy. The results on Windows 98 SE were similar, except IRQ could not be changed (a message popped up saying this resource setting cannot be changed).

    Also, when ICH AC97 is chosen as the audio controller instead of Intel HD Audio, then AC97 gets the IRQ 11. I guess that fact alone is enough to rule out that the problem is related to IRQs.

    On 4/8/2019 at 2:40 PM, deomsh said:

    If in VirtualBox exists a (virtual) BIOS, maybe there are options to change IRQ's.

    Its BIOS only offers the menu to choose boot device.

     

     

    0

    Latest Version of Software Running on XP

    in Windows XP

    Posted

    21 hours ago, jaclaz said:

    Most probably UNneeded in this case, but JFYI, a few old versions of 7-zip also include a NSIS decompiler, see:

    https://sourceforge.net/projects/nsidis/

    I see, 7-Zip 15.05 does show the decompiled script in this case.

    21 hours ago, Mathwiz said:

    Whew - 230 MB? No thanks. I'll just stick with PotPlayer Mini.

    That remark about language files applies generally when dealing with anything where those languages are used. I merely wanted to point out that the way your screenshot looked isn't how it's supposed to look.

    14 hours ago, pelolindo said:

    You has tryed portableappz method? i like it because you can add the codecs to the portable too

    We were discussing beta version of PotPlayer, which drops XP support, the current stable version still supports it officially.

    0
×
×
  • Create New...