Author Topic: partition drive  (Read 748 times)

daydreamer

  • Member
  • ****
  • Posts: 942
  • watch Chebyshev on the backside of the Moon
partition drive
« on: April 19, 2019, 06:45:19 PM »
anyone else partitioned drive
would be good to have the usual masm32 sdk and a customized on same drive without need to rewrite all includes in source files
Quote from Flashdance
Nick  :  When you give up your dream, you die
*wears a flameproof asbestos suit*
Gone serverside programming p:  :D

jj2007

  • Member
  • *****
  • Posts: 9794
  • Assembler is fun ;-)
    • MasmBasic

hutch--

  • Administrator
  • Member
  • ******
  • Posts: 6756
  • Mnemonic Driven API Grinder
    • The MASM32 SDK
Re: partition drive
« Reply #2 on: April 20, 2019, 02:09:25 AM »
I have been partitioning hard disks for close to 30 years, this allows me to use a dedicated partition just for development. Others for other tasks, others for similar data storage. Not only that but I set up an 8 gig ramdisk for junk, downloads and the occasional testing of very high speed stuff. Do whatever is necessary to escape from one C:\ partition so you are not nobbled by Microsoft's stuffups.
hutch at movsd dot com
http://www.masm32.com    :biggrin:  :skrewy:

Vortex

  • Member
  • *****
  • Posts: 2030
Re: partition drive
« Reply #3 on: April 20, 2019, 03:18:53 AM »
The Masm32 installation can also run on a RAM disk :

http://www.ltr-data.se/opencode.html/#ImDisk

Tedd

  • Member
  • ***
  • Posts: 377
  • Procrastinor Extraordinaire
Re: partition drive
« Reply #4 on: April 25, 2019, 01:54:37 AM »
The proper way to do it is not to have paths in your source in the first place.

  • Define a system environment variable: MASM_HOME with the full path to your masm installation
  • Edit the assemble/link/build/etc .bat files so they use this for the exe paths, e.g. "%MASM_HOME%\bin\ml"
  • Additionally, pass the include/lib locations to the right tools, e.g. "%MASM_HOME%\bin\ml /I%MASM_HOME%\include ..." and "%MASM_HOME%\bin\link /LIBPATH:%MASM_HOME%\lib ..."
  • Don't use paths in your source, e.g. "include kernel32.inc" and "includelib kernel32.lib"
  • Move things anywhere you like.
Potato2