Jump to content

Marztabator

Member
  • Posts

    481
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Posts posted by Marztabator

  1. Well unfortunately I don't know an awful lot about "animated bitmaps" and how much they're supposed to differ structure wise from a regular bitmap...

     

    I thought I read somewhere though that Windows more or less creates the scroll effect "on the spot" out of any bitmap and which colours it uses depends on how the bitmap's palette is setup???

  2. Okay, back again after some absence.  I meant to ask something I should've asked back then.

     

    I did try to rip the logo data from memory using the debugger included with DOSBox Daum (the latest version).  I carefully found the routine that makes it unpack the custom-packed data embedded within IO.SYS and followed it carefully.  Although I do indeed see the familiar bitmap header and the correct/decrunched data that follows........ I can never get the whole file at once.  It always unpacks in seperate chunks and then overwrites itself afterwards, rather than just unpacking it into a single BMP file and leaving it in memory for me to rip.  I've tried everything.  I can't even get the seperate pieces to put them together.  I combed through the entire memory chunk (using a combination of the debugger and my hex editor of choice, HxD) and can't find any other bitmap-related data unpacked elsewhere.  I'm not sure if memory-ripping is how rloew does it but he must know something else about it that's flummoxing me.

     

    Is Windows just being really clever and unpacking the rest of the bitmap into some inaccessible part of the memory?

  3. Posting this so it WILL be noticed!

    @dencorso - the LOGO.SYS does not exist in the CD - only LOGOS, LOGW, and SULOGO ("First Tim") exist.

    http://www.themeworld.com/support/walls-change.html

    At the bottom of the link, is a set of VC++ programs. I downloaded the Win98 one and ran in on my VPC Win98SE installation. It appears that they could CARE LESS which OS you're running. All three of the files (LOGOS, LOGOW, LOGO) WILL get installed into the correct place.

    Happy now? ;)

    Interesting. May take me a while to setup another VM though to test this out (it obviously won't extract the contents under 7), so nobody, like, close this thread or anything!

  4. The easiest way to make the change is to copy the compressed Logo from the Windows 98 IO.SYS to the Windows 95 IO.SYS.

    Some realignment will be required as the 98 Compressed Logo is larger than the space allocated to the 95 Logo.

    I'm not sure why you would want to use the Windows 98 Logo in your Windows 95 System. It says "Windiows 98".

    Yeah, I wouldn't know how to "realign" a system file I'm afraid. That and I feel it's only fair that a publicly known way to "rescue" the logo from the "prison" that is IO.SYS is revealed. :)

    I see nothing especially fair about that. I consider it one of my Trade Secrets.

    I might just see if it's possible to rip the logo out from a memory dump with DOSBox Daum's debugger at this rate...

  5. The easiest way to make the change is to copy the compressed Logo from the Windows 98 IO.SYS to the Windows 95 IO.SYS.

    Some realignment will be required as the 98 Compressed Logo is larger than the space allocated to the 95 Logo.

    I'm not sure why you would want to use the Windows 98 Logo in your Windows 95 System. It says "Windiows 98".

    Yeah, I wouldn't know how to "realign" a system file I'm afraid. That and I feel it's only fair that a publicly known way to "rescue" the logo from the "prison" that is IO.SYS is revealed. :)

    And why not use the Windows 98 logo in Windows 95? I like the idea of mixing things up, and like I said, I always considered it prettier looking than the 95 one. :)

  6. See, this is precisely the problem I found with similar questions being responded to online. People seem to think that creating a LOGO.SYS file and placing it in C:\ is the only answer. If you want a custom loading screen yes, but the fact remains I want to use the *original* boot logo - which is currently trapped inside IO.SYS - outside of its original OS.

  7. Guys, guys............ I already know how to unpack ME's IO.SYS file and extract the bitmap out of it. This is what I already mentioned in my post!

    The IO.SYS I need help with relates to MS-DOS 7.1 (and by extension 7.0) as used in Win98 (and 95). That's generally not packed apart from the logo itself, which according to rloew is compressed in a different format. We need a tool or something for *that*.

  8. While building myself a nice little Windows 95 virtual environment, I figured I might choose to mix things up and use the boot logo from Windows 98 since I reckon it looks prettier. ;)

    Wondering why I couldn't find the startup logo (or "logo.sys") amongst the CAB archives on my 98SE CD, I googled for information and discovered that apparently the default startup animation is hidden inside the system file IO.SYS.

    Only problem is that I don't know how to get it out of there. I looked at it (as well as its renamed equivalent "winboot.sys") through a hex editor and It doesn't appear to be in bitmap format, or at least not have the proper header to make it stand out easily. What's odd is that the Windows ME version - from playing around with the file on my ME CD and unpacking it with IO8DCOMP - has an obvious bitmap file inside that can be extracted easily (but is otherwise identical to "sulogo.sys"). So why is the pre-ME equivalent more difficult to deal with?

    I googled everywhere hoping someone had the same idea as me and received or gave out the answers I was looking for - the closest I got was with this guy on this very board, who rather unfortunately was ignored and the thread forgotten about relatively quickly.

    All I'm looking for is the means to extract this default logo/animation out of the file and NOT a guide on how to use a replacement "logo.sys" like most similar questions on the net ended with. I've read the odd suggestion that a utility or two exists that should deal with this, but nobody ever mentioned any names.

    Anyone care to help? Thank you. :)

  9. Writing a carriage return into the registry is pretty easy -- at least inside a REG_SZ value. It's like 3 lines of vbscript... No need to use any fancy API to do it (regedit won't show it but it will definitely be in there). However, if it's stored inside a REG_MULTI_SZ value than that's another story (forget about vbscript then but C++ will do the job just fine using the usual RegSetValueEx function)

    Oooooh, you happen to know where I can find such a script, or if one can be reproduced on here? I believe the value I wish to change is a REG_SZ, so it shouldn't be too much of a problem.

  10. The sort of characters that a regfile can't import?

    I learnt about this quite recently when inquiring about how to adjust some tag values remotely for dBpoweramp...

    http://forum.dbpoweramp.com/showthread.php?t=21865

    Turns out it inserts an "\r" thingy between the values that RegEdit can't capture. Spoon suggests I find a program that can add that sort of character into the registry and understand it correctly, but he doesn't know of any such tools himself.

    Do any exist or will I ultimately be forced to use dMC's own config program?

  11. Some of you may be aware that by editing a certain driver file (usbport.sys) it is possible to increase the USB polling speed from the default of 125Hz to 250, 500 or 1000Hz. I know this certainly worked well in the past.

    But since moving onto XP SP3 since the past year or so, I keep finding that no matter how much editing and patching I do, the speed never goes above 250Hz. I don't know if it's a new hardcoded limit in the driver, or the mouse I'm using, or something else.

    The current latest version of the driver is 5.1.2600.5551. Downgrading the file to 5.1.2600.5512 doesn't seem to make a difference.

    So what else is it that could be the problem? All help appreciated, thanks!

  12. Since no-one responded to my post, I examined it myself. As I feared, it does install the Nero crap in HKCR, and furthermore, the uninstaller doesn't bother to remove it at all, leaving you with an unclean system unless you're smart enough to root through the registry and clean it out yourself.

    This is the same problem found in Nero 7/8 Lite and it only entices me to start searching for portable versions, or even a different burning tool altogether.

  13. Oooooh, I like! Although there's yet again something I'm puzzled about.

    I assumed where it says "Space", you could replace it with a character of your choice - but WScript generates errors in that part whether I use quotations or not. Yet the write function doesn't look that much different from one in the script I showed above. Maybe it just doesn't like having a sum function next to it?

    Maybe it would help if I explain a bit more about what I'm trying to achieve - a script that goes by bytes rather than megabytes, and which determines how many bytes the dummy should be exactly by how much space the specified folder takes up out of a total of, say, a 700Mb CD capacity, and which inputs a specified character of choice. Am I dreaming too wildly here? ;)

  14. Oooooh, ta for this. I've had to re-adapt it slightly (didn't like the the pop-up window reporting on size a gajillion times over), but I seem to have hit an annoying barrier at the moment regarding getting the file-size exact. At the moment it ends up generating a file that's slightly over the size you specify in the box because of the ">" setting, but attempting to use "=" instead seems to make the script keep working on the file endlessly, going way above the limit and showing no signs of stopping. It's strange because "=" seems to be a perfectly valid setting understood by Windows Script (after googling around for info). Is it just incompatible with "int(File.Size)"?

    To give you a good idea, here's a simple example script coded to generate a specified file with a specified size limit, and writing one character at a time on a loop:

    Option Explicit
    Dim Act :Set Act = CreateObject("Wscript.Shell")
    Dim Fso :Set Fso = CreateObject("Scripting.FileSystemObject")
    Dim File, SizeFile
    FileSize()
    Function FileSize()
    SizeFile = "100000"
    End Function
    Dim Ts
    Set Ts = Fso.CreateTextFile("z.zzz", True)
    Set File = Fso.GetFile("z.zzz")
    Do Until Int(File.Size) = Int(SizeFile)
    Ts.Write "ÿ"
    Loop
    WScript.Echo "Done!"
    Ts.Close

    Any way to make it honour the "=" properly?

  15. Well while that's a well-thought out batch file there, it's not very friendly when it comes to space and time, due to all the various temp files and the endless whirring by the HD. Thank you for teaching me a bit more about command functions anyway.

    Are you guys *sure* VBScript is incapable of doing dummy work itself? I always imagined it to be quite magic and capable of more than CMD.

  16. Simply put, I wish to come up with a script that can create a dummy file padded up to the size of my choosing (with whatever characters used). Maybe one that can work in a command line script or whatever.

    However my knowledge on VBScript isn't all that great and attempting to google for the info I need has turned out to be fruitless. There could anyone help out pretty please?

    Cheeeeers.

×
×
  • Create New...