@Preben Alsholm 

It does not work for me. I am running windows 10 professional. Latest updates.

I uninstalled maple 2018. Rebooted the PC. Installed Maple 2018 again, then did update. So now I am running latest and greatest Maple.

Each time I do an package update from the cloud or by direct command, Maple MSERVER.EXE crashes

Faulting application name: mserver.exe, version: 0.0.0.0, time stamp: 0x5bee9873
Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f83ff
Exception code: 0xc0000005
Fault offset: 0x000000000005f3e7
Faulting process id: 0x19b0
Faulting application start time: 0x01d499c1e72d8dac
Faulting application path: C:\Program Files\Maple 2018\bin.X86_64_WINDOWS\mserver.exe
Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR120.dll
Report Id: a4b63628-36d2-4a4a-9ef6-6f553703bd8f
Faulting package full name: 
Faulting package-relative application ID: 

when I try packagetools:-install.... same thing, MSERVER.EXE crashes. The examples posted above do not work for me for this reason

I have no idea what else to try.

My windows event log is full of MSERVER crashes.

Error	12/22/2018 12:45:48 AM	Application Error	1000	(100)
Error	12/21/2018 11:29:52 PM	Application Error	1000	(100)
Error	12/21/2018 10:50:40 PM	Application Error	1000	(100)
Error	12/21/2018 10:44:40 PM	Application Error	1000	(100)
Error	12/21/2018 10:28:07 PM	Application Error	1000	(100)
Error	12/20/2018 9:16:46 PM	Application Error	1000	(100)
Error	12/20/2018 8:37:09 PM	Application Error	1000	(100)
Error	12/20/2018 8:28:05 PM	Application Error	1000	(100)
Error	12/20/2018 8:23:45 PM	Application Error	1000	(100)

Those are all from Maple MSERVER.EXE. same exact crash. It happens each time I try to install package.

windows 10 professional. 64 GB. This problem started either after I did windows 10 latest updates it seems, or something in Maple 2018.2.1 that caused it, since I was able to do this before many times on same PC with no problem when I was running Maple 2018.2 not long ago. 

I have no firewall. This is a home PC.

I made no changes myself in the PC that will affect Maple itself.

@ecterrab 

Thank you again for the instructions. I followed them exactly.

cmaple crashes immediatly after the command  PackageTools:-Install("the full path of the file Physics+Updates.maple").  (btw, you had typo, you wrote .mla there.

The full path I used was correct. the cmaple windows went away right away. I looked at the event log and saw the crash with time stamp at the instance cmaple crashed.

Faulting application name: mserver.exe, version: 0.0.0.0, time stamp: 0x5bee9873
Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f83ff
Exception code: 0xc0000005
Fault offset: 0x000000000005f3e7
Faulting process id: 0x1d38
Faulting application start time: 0x01d498d498640810
Faulting application path: C:\Program Files\Maple 2018\bin.X86_64_WINDOWS\mserver.exe
Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR120.dll
Report Id: 69c0deb5-e619-48ad-b67e-f317d2e617c8
Faulting package full name: 
Faulting package-relative application ID: 

There is something wrong somewhere. I will try to contact customer support may be they can help. May be windows 10 latest update changed something.

Thank you

@ecterrab 

Thank you for the updates. But V 264 also hanged during installation, so had to terminate it. Waited 10 minutes.

The strange thing is that when I do PackageTools:-Uninstall("Physics Updates"); followed by Physics:-Version() it says I have version 264?  Is not PackageTools:-Uninstall("Physics Updates"); supposed to actually remove the physics package?

Then when I type your code above, I get no solution. Because I assume Physics package is not there?

Then I tried to install another package from the cloud. Tried the ClusterAnalysis package. And this also hanged at the "installing...." stage. restarted Maple and tried yet another package. TextTools, and that also hanged !

Then looked in the windows 10 event viewer and see number of  critical errors from Maple:

Faulting application name: mserver.exe, version: 0.0.0.0, time stamp: 0x5bee9873
Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f83ff
Exception code: 0xc0000005
Fault offset: 0x000000000005f3e7
Faulting process id: 0x934
Faulting application start time: 0x01d498c574117d48
Faulting application path: C:\Program Files\Maple 2018\bin.X86_64_WINDOWS\mserver.exe
Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR120.dll

The I closed Maple, started the command line Maple and typed

    |\^/|     Maple 2018 (X86 64 WINDOWS)
._|\|   |/|_. Copyright (c) Maplesoft, a division of Waterloo Maple Inc. 2018
 \  MAPLE  /  All rights reserved. Maple is a trademark of
 <____ ____>  Waterloo Maple Inc.
      |       Type ? for help.
> PackageTools:-Uninstall("Physics Updates");
Uninstall Physics Updates from directory C:\Users\me\maple\toolbox/2018/Physics Updates? (Y/N)
Y
                                                         true

> Physics:-Version();
"C:\Program Files\Maple 2018\lib\update.mla",

    2018, November 16, 2:40 hours, version in the MapleCloud: 264, version installed in this computer: 264


> PackageTools:-Install("5137472255164416", version = 264, overwrite);

Error, (in PackageTools:-Install) permission denied when trying to copy to C:\Users\me\maple\toolbox/2018/Physics Updates/lib/UpdatesPhysics2018.help

#notice the mixes "\" and "/" in the above directory name

#Ok, let me try again
> PackageTools:-Install("5137472255164416", version = 264, overwrite);

#Now it hangs. Nothing happens.

The download works OK, as I see the file here

But the problem comes from the installing phase.

It seems that installing from the cloud does not work. I have no idea why all packages hangs in "installing....". May be windows 10 latest updates broke something. I do not know.

If there is another manual way to try to install the Physics package from the file above? I will try it. 

@ecterrab 

Thanks., I followed the instructions, but it still hangs.

Rebooted the PC, started Maple and followed same instructions again and still hangs.

I am running windows 10, with latest updates. 

I did not make any other changes to my windows. 

If there is a log file kept during installation, I could look at it and see where/why it hanged but I do not know if there is such a file.

I'll wait and try the next version of physics updates, may be will have better luck with that. This is the first time it hanged during install for me.

version()
 User Interface: 1362973
         Kernel: 1362973
        Library: 1362973
                            1362973

kernelopts(version)
  Maple 2018.2, X86 64 WINDOWS, Nov 16 2018, Build ID 1362973

interface(version)

    Standard Worksheet Interface, Maple 2018.2, Windows 10, 

       November 16 2018 Build ID 1362973

Hello;

I've just updated my version 2018.2 using the "check for updates" option from the Tools-> menu to 2018.2.1 according to the post.

Now when I start Maple again, how does one verify they are running 2018.2.1?  It is still saying 2018.2 (without the .1 at the end)

I am assuming this minor version number should be given in the version number as well, else how would one know they are running 2018.2 vs. 2018.2.1 or 2018.2.2 etc...?

@Mariusz Iwaniuk 

Thank you for the workaround. Will use your workaround meanwhile, but I think it should not give exception if user do not provide the hint. Btw, to get simpler solution withtout the transforms, the following assumption helps.

sol:=pdsolve({pde,ic},w(x,t),HINT = `*`) assuming t>0;

Your PDE  has x,y as independent variables but your boundary conditions uses time?

PDE := (diff(u(x,y), x,x))-1/x*(diff(u(x, y), x)) -x^2*(diff(u(x,y), y,y))= 2;
BCs:=u(0,t) = 0, u(1,t) = 0;

@tomleslie 

you can give an answer without being such a rude person.

@Mariusz Iwaniuk 

Thanks. But assumptions are not needed in the product rule for logs. The rule is defined as is. Unless Wikipedia and all the books that list this rule are wrong ofcourse, which is a possibility.

@acer 

What is the reason for putting a NULL at last line of the proc?

I made small modification to your code, as I wanted the latex to be string.

restart:	
aliasedlatex:=proc(e)
local lookup;
lookup:=op(eval(alias:-ContentToGlobal));
return (:-latex(subs(lookup,e),output=string));
end proc:

This seems to work so far. But not sure why the NULL was there.

alias(C[1]=_C1):
aliasedlatex(1);
aliasedlatex(dsolve( diff(y(x),x)=1,y(x)) );

                              "1"
                "y \left( x \right) =x+C_{{1}}"

I found an answer, thanks to acer  which seems to do what I want. But I need to try it more to make sure.

https://www.mapleprimes.com/questions/204714-Alias-Surpress-Or-Declare-With-Latex-Outputs

restart;
aliasedlatex:=proc(e)
  local lookup;
  lookup:=op(eval(alias:-ContentToGlobal)):
  :-latex(eval(e,lookup));
  NULL;
end proc:

alias(C[1]=_C1):
sol:=dsolve(diff(y(x),x)=1,y(x));
aliasedlatex(sol);

               y \left( x \right) =x+C_{{1}}

which is what I want. This should be part of Maple itself. I do not understand why it is not. Or at least an option to latex() command.

@Joe Riel 

"Alas, the current design of odetest expects that integration constants are named with prefix _C"

Then why I can rename the constant to anything else in some other ode solution and it works just fine for odetest?

ode:=diff(y(x),x)=1+2*x;
my_sol:=y(x)=x^2+x+ C;
odetest(my_sol,ode);

            0

I can use "B" or "C[1]" or any other letter, and Maple is happy with it in the above example. odetest gives 0.  Maple own solution does use _C

dsolve(ode,y(x));
       y(x) = x^2+_C1+x

Are you saying it is hardcoded in some places and not in other places? 

This is all so confusing for a user who is trying to learn Maple.

@vv 

I am not able to follow what you are saying. 

I want 

RootOf(signum(0, _Z, 1));

to become

RootOf(signum(0, n, 1));

I read the help, but do not see why one can't do the above. (Maple help is really hard to follow. No example there for the 3 argument version for example. Maplesoft should invest some resources to improve help.)

It can be done using subs

expr:=RootOf(signum(0, _Z, 1));
subs(_Z=n,expr);

           RootOf(signum(0, n, 1))

Can't use subs, since do not know what the _symbol is before hand. This is just for formating purposes. I like to see "n" there instead of "_Z" when I print it.

@vv 

<"Blow-up" is not defined.>

Well, I guess Wikipedia and all the engineering Professors at my school who used this term have no clue what they are saying.

From https://en.wikipedia.org/wiki/Singularity_(mathematics)

The term blow up is a just a "loose" way to describe this and very common. At least in engineering.  As I said, there are other cases where a function is said to be singular at a point and the above article talks about those cases aslo. But the above is the most common one and what I was interested in when using singular for my needs. 

@vv 

I am using the basic definition of singularity: The points where the function  blows up. Sometimes called a pole also. I know there are different types of singularities and this can get complicated.

But I simply wanted to know the points where the function "blows" up. Excluding +- infinity.

So using this, the function sqrt(x) does not blow up (excluding +- infinity). singular does give these points correctly, but not discont(). At least not for every function I tried. So can't use discont() to find where the function "blows" up.

I like singular(), it works OK. Only question I had is about the real domain part. But it is not a big problem, as I could always filter out the complex poles it finds by post-processing the result.