The question is whether one can do something useful with the result if it's so big that Maple has trouble displaying it. But that's up to you. :-) Here's how you can write it to a file: CodeGeneration[Matlab](y,output="C:/Temp/file1.txt"); or fprintf("C:/Temp/file2.txt","%a\n",y); For fprintf, you might need to append an fclose or fflush command to actually get the file written to disk. My remark about write was nonsense - sorry.

The shortest way should be solve(identity(eq1,x)); where eq1 is your equation above. Please see ?solve,identity for the full story.

For postprocessing the numerical solution of an ODE, the best way probably is to override the output=procedurelist option and then use eval in the following way:

sol:=dsolve({diff_eq,y(0)=0},y(x),numeric,output=listprocedure);
Y:=eval(y(x),sol);

Then you can evaluate Y(x) for plotting purposes, e.g.. (I used uppercase to distinguish it from the "original" variable y, so that you can invoke dsolve once more if needed.) For more info, please see ?dsolve,numeric and ?eval.

For postprocessing the numerical solution of an ODE, the best way probably is to override the output=procedurelist option and then use eval in the following way:

sol:=dsolve({diff_eq,y(0)=0},y(x),numeric,output=listprocedure);
Y:=eval(y(x),sol);

Then you can evaluate Y(x) for plotting purposes, e.g.. (I used uppercase to distinguish it from the "original" variable y, so that you can invoke dsolve once more if needed.) For more info, please see ?dsolve,numeric and ?eval.

That seems to happen in standard typesetting level only. Try interface(typesetting=extended); or select "Extended" in "Maple 10 > Preferences > Display > Typesetting level". Then re-execute your input. Copy&paste should work properly now.

I have not seen this problem yet. More information may be needed (also from mLau): exact version numbers for Maple, Mac OS X, Java? Is it Delete only, or is Backspace also affected?

This happens when you select the integrand and the dx but not the integral sign. Maple is unsure how to treat this incomplete expression syntactically. It's not Mac specific.

If I recall correctly, at least Maple V Release 3 on Linux evaluated the relevant environment variable (was it MORE or PAGER or something like that?). Setting that to less (or maybe /bin/less) worked as expected. I don't know whether that approach posed any problems, but from Release 4 on, Maple used its own built-in pager.

One way is to wrap the plot and textplot calls into one display call, which is then passed to the Plotter element. I'm using the long form plots[textplot](...) here. BoxColumn( BoxRow('border'='true','caption'="Triangle",halign=none,'font'=Font("Arial",14)), Plotter['PL1'](plots[display](plot([[0,0],[15,0],[24.50,9.69],[0,0]],filled=true), plots[textplot]([0,0,"Angle A"],align=BELOW), plots[textplot]([15,0,"Angle C"],align=BELOW), plots[textplot]([24.50,9.69,"Angle B"],align=ABOVE)), width=275,height=150) ) Hope you can copy&paste that properly. The formatting will probably be lost in this forum.

Such tasks will usually be delegated to C functions that can be called from Maple via External Linking (see ?define_external as an entry point). If you have some driver that treats the serial port as a network device (i.e. capable of running TCP/IP over it), you should be able to access that port with Maple's Sockets package. However, I don't have examples for either method, sorry.

Could you supply more details, please? What problem are you encountering? I just loaded a 1024x1536 image, so 480x640 pixels should pose no problem.

Could you supply more details, please? What problem are you encountering? I just loaded a 1024x1536 image, so 480x640 pixels should pose no problem.

BTW: the OP mentioned Laplace transform: dsolve({odeQ,ics},q(t),method=laplace); gives a more compact representation of the solution.

BTW: the OP mentioned Laplace transform: dsolve({odeQ,ics},q(t),method=laplace); gives a more compact representation of the solution.

A general remark: In the definition of odeQ, I would use exact values (C=1/100 in this case), because otherwise postprocessing the dsolve result (e.g. odetest(%,[odeQ,ics]);) could make trouble.