Results 1 to 7 of 7

Thread: Command Prompt in Windows 10?

  1. #1

    Thread Starter
    Hyperactive Member
    Join Date
    Nov 2018
    Posts
    499

    Command Prompt in Windows 10?

    Hello,

    I am trying to modify the attached midi file CANYON.MID (that shipped with past Windows OS's)
    per instructions from Charles Petzold in a 1992 PC Magazine article.
    https://books.google.ca/books?id=F1D...page&q&f=false (page 404)

    The modification is to put an additional Tempo event half way through the file.

    In the article Petzold states:

    Take TEMPO.SCR script shown below
    Code:
    e 4150 00 FF 51 03 02 B1 56
    n canyont.mid
    w
    q
    and run DEBUG like so
    Code:
    DEBUG CANYON.MID < TEMPO.SCR
    creating CANYONT.MID

    I have no knowledge of these commands.
    Something from Windows Command Prompt?
    Does it still exist?

    If anyone could help it would be appreciated.
    Attached Files Attached Files
    Last edited by mms_; Sep 17th, 2022 at 11:27 PM.

  2. #2
    PowerPoster
    Join Date
    Feb 2006
    Posts
    23,796

    Re: Command Prompt in Windows 10?

    No VB question here.

    Debug is not a standard command. He was probably using something from some version of Visual Studio or something else entirely.

    It looks like his redirected input commands just overwrite 7 bytes at offset 0x4150 then save and exit, but that's a guess.

  3. #3

    Thread Starter
    Hyperactive Member
    Join Date
    Nov 2018
    Posts
    499

    Re: Command Prompt in Windows 10?

    OK thanks

    Yes that is what I was thinking too, but I thought overwriting like that would corrupt the MIDI file and make it unplayable.

  4. #4
    PowerPoster
    Join Date
    Nov 2017
    Posts
    2,152

    Re: Command Prompt in Windows 10?

    Quote Originally Posted by dilettante View Post
    No VB question here.

    Debug is not a standard command. He was probably using something from some version of Visual Studio or something else entirely.

    It looks like his redirected input commands just overwrite 7 bytes at offset 0x4150 then save and exit, but that's a guess.
    https://en.wikipedia.org/wiki/Debug_(command)

    Nothing to do with Visual Studio, Debug was bundled with DOS since DOS 1.00. It was still available in Windows XP/2003 server.

    OP, if you are going to be referencing ~30 year old computer related documentation, I would strongly recommend setting up some virtual machines running legacy OS's via something like VirtualBox so that you have access to the operating systems from that era.

  5. #5
    Frenzied Member PlausiblyDamp's Avatar
    Join Date
    Dec 2016
    Location
    Newport, UK
    Posts
    1,925

    Re: Command Prompt in Windows 10?

    Quote Originally Posted by mms_ View Post
    OK thanks

    Yes that is what I was thinking too, but I thought overwriting like that would corrupt the MIDI file and make it unplayable.
    It really depends on what you are overwriting and what you are overwriting it with - in this case presumably they have studied the original file and figured out how to safely change it to get the desired end result.

  6. #6
    Fanatic Member
    Join Date
    Jun 2015
    Posts
    810

    Re: Command Prompt in Windows 10?

    Open the file in binary mode and write those hex bytes to that file offset or do it manually in a hex editor
    Same effect. No need for the old debug app.

    You can see the command line args here: https://montcs.bloomu.edu/Informatio...DOS-Debug.html
    Last edited by dz32; Sep 19th, 2022 at 10:15 AM.

  7. #7

    Thread Starter
    Hyperactive Member
    Join Date
    Nov 2018
    Posts
    499

    Re: Command Prompt in Windows 10?

    dz32
    Great, Thank you!

    I can do that!!
    The link you provided confirms that 4150 is the Hex byte offset.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width